Answer:- It is suggested to perform a regression testing and run tests for all the other modules as well. Finally, the QA should also carry out a system testing.

Answer:- If the standard documents like System Requirement Specification or Feature Description Document are not available, then QAs may have to rely on the following references, if available. • Screenshots • A previous version of the application • Wireframes Another reliable way is to have discussions with the developer and the business analyst. It helps in solving the doubts, and it opens a channel for bringing clarity on the requirements. Also, the emails exchanged could be useful as a testing reference. Smoke testing is yet another option that would help verify the main functionality of the application. It would reveal some very basic bugs in the application. If none of these work, then we can just test the application from our previous experiences.

Answer:- Possible differences between retesting and regression testing are as follows: • We perform retesting to verify the defect fixes. But, the regression testing assures that the bug fix does not break other parts of the application. • Regression test cases verify the functionality of some or all modules. • Regression testing ensures the re-execution of passed test cases. Whereas, retesting involves the execution of test cases that are in a failed state. • Retesting has a higher priority over regression. But in some cases, both get executed in parallel.

Answer:- Following are some of the key challenges of software testing: The lack of availability of standard documents to understand the application Lack of skilled testers Understanding the requirements: Testers require good listening and understanding capabilities to be able to communicate with the customers the application requirements. The decision-making ability to analyze when to stop testing Ability to work under time constraints Ability to decide which tests to execute first Testing the entire application using an optimized number of test cases

Answer:- Functional testing covers the following types of validation techniques: • Unit testing • Smoke testing • UAT • Sanity testing • Interface testing • Integration testing • System testing • Regression testing

Answer:- • Functional testing: It is testing the ‘functionality’ of a software or an application under test. It tests the behavior of the software under test. Based on the requirement of the client, a document called a software specification or requirement specification is used as a guide to testing the application. • Non-functional testing: In software terms, when an application works as per the user’s expectation, smoothly and efficiently under any condition, then it is stated as a reliable application. Based on quality, it is very critical to test these parameters. This type of testing is called non-functional testing.

Answer:- Software testing life cycle (STLC) proposes the test execution in a planned and systematic manner. In the STLC model, many activities occur to improve the quality of the product. The STLC model lays down the following steps: 1. Requirement Analysis 2. Test Planning 3. Test Case Development 4. Environment Setup 5. Test Execution 6. Test Cycle Closure

Answer:- Fault is a condition that makes the software fail to execute while performing the considered function.

Answer:- A slip in coding is indicated as an error. The error spotted by a manual tester becomes a defect. The defect which the development team admits is known as a bug. If a built code misses on the requirements, then it is a functional failure.

Answer:- • Severity: It represents the gravity/depth of a bug. It describes the application point of view. • Priority: It specifies which bug should get fixed first. It defines the user’s point of view.

Answer:- The criticality of a bug can be low, medium, or high depending on the context. User interface defects – Low Boundary-related defects – Medium Error handling defects – Medium Calculation defects – High Misinterpreted data – High Hardware failures – High Compatibility issues – High Control flow defects – High Load conditions – High

Answer:- Defect detection percentage (DDP) is a type of testing metric. It indicates the effectiveness of a testing process by measuring the ratio of defects discovered before the release and reported after the release by customers. For example, let’s say, the QA has detected 70 defects during the testing cycle and the customer reported 20 more after the release. Then, DDP would be: 70/(70 + 20) = 72.1%

Answer:- Defect removal efficiency (DRE) is one of the testing metrics. It is an indicator of the efficiency of the development team to fix issues before the release. It gets measured as the ratio of defects fixed to total the number of issues discovered. For example, let’s say, there were 75 defects discovered during the test cycle while 62 of them got fixed by the development team at the time of measurement. The DRE would be 62/75 = 82.6%

Answer:- Defect age is the time elapsed between the day the tester discovered a defect and the day the developer got it fixed. While estimating the age of a defect, consider the following points: • The day of birth of a defect is the day it got assigned and accepted by the development team. • The issues which got dropped are out of the scope. • Age can be both in hours or days. • The end time is the day the defect got verified and closed, not just the day it got fixed by the development team.