Answer:- Static testing is a white-box testing technique that directs developers to verify their code with the help of a checklist to find errors in it. Developers can start the static testing without actually finalizing the application or program. Static testing is more cost-effective than dynamic testing as it more areas than dynamic testing in a shorter time.

Answer:- It is a standard software testing approach that requires testers to assess the functionality of the software as per the business requirements. The software is treated as a black box and validated as per the end user’s point of view.

Answer:- A test plan stores all possible testing activities to ensure a quality product. It gathers data from the product description, requirement, and use case documents. The test plan document includes the following: • Testing objectives • Test scope • Testing the frame • Environment • Reason for testing • Criteria for entrance and exit • Deliverables • Risk factors

Answer:- Test coverage is a quality metric to represent the amount (in percentage) of testing completed for a product. It is relevant for both functional and non-functional testing activities. This metric is used to add missing test cases.

Answer:- It’s considered not possible to perform 100% testing of any product. But you can follow the below steps to come closer. • Set a hard limit on the following factors: o Percentage of test cases passed o Number of bugs found • Set a red flag if: o Test budget is depleted o Deadlines are breached • Set a green flag if: o The entire functionality gets covered in test cases o All critical and major bugs must have a ‘CLOSED’ status

Answer:- Unit testing has many names such as module testing or component testing. Many times, it is the developers who test individual units or modules to check if they are working correctly. Whereas, integration testing validates how well two or more units of software interact with each other. There are three ways to validate integration: • Big Bang approach • Top-down approach • Bottom-up approach

Answer:- No. System testing should start only if all modules are in place and they work correctly. However, it should be performed before UAT (user acceptance testing).

Answer:- Various types of Software Testing used by manual testers are as follows: • Unit testing • Integration testing • Regression testing • Shakeout testing • Smoke testing • Functional testing • Performance testing • o Load testing o Stress testing o Endurance testing • White-box and Black-box testing • Alpha and Beta testing • System testing

Answer:- The test driver is a section of code that calls a software component under test. It is useful in testing that follows the bottom-up approach. The test stub is a dummy program that integrates with an application to complete its functionality. It is relevant for testing that uses the top-down approach. For example: Let’s assume a scenario where we have to test the interface between Modules A and B. We have developed only Module A. Here, we can test Module A if we have the real Module B or a dummy module for it. In this case, we call Module B as the test stub. Now, Module B can’t send or receive data directly from Module A. In such a scenario, we’ve to move data from one module to another using some external features called test driver.

Answer:- Agile testing is a software testing process that evaluates software from the customers’ point of view. It is favorable as it does not require the development team to complete coding for starting QA. Instead, both coding and testing go hand in hand. However, it may require continuous customer interaction.

Answer:- It is one of the white-box testing techniques. Data flow testing emphasizes for designing test cases that cover control flow paths around variable definitions and their uses in the modules. It expects test cases to have the following attributes: 1. The input to the module 2. The control flow path for testing 3. A pair of an appropriate variable definition and its use 4. The expected outcome of the test case

Answer:- End-to-end testing is a testing strategy to execute tests that cover every possible flow of an application from its start to finish. The objective of performing end-to-end tests is to discover software dependencies and to assert that the correct input is getting passed between various software modules and sub-systems.

Answer:- Reliability testing

Answer:- When a bug occurs, we can follow the below steps. • We can run more tests to make sure that the problem has a clear description. • We can also run a few more tests to ensure that the same problem doesn’t exist with different inputs. • Once we are certain of the full scope of the bug, we can add details and report it.