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.

Answer:- Here are the two principal reasons that make it impossible to test a program entirely. • Software specifications can be subjective and can lead to different interpretations. • A software program may require too many inputs, outputs, and path combinations.

Answer:- If the required specifications are not available for a product, then a test plan can be created based on the assumptions made about the product. But we should get all assumptions well-documented in the test plan.

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.