How to Know when to Stop Testing?

by Nataliia Vasylyna | October 24, 2016 6:46 am

Usually, at the beginning stage of software testing, a tester is full of determination and starts executing all necessary preparatory actions, such as defining the test strategy and purposes of testing, writing a test plan and test cases, and many others.

To know when to start web app testing or mobile testing[1], one should specify the entry and exit criteria for the project success.

The exit criteria presuppose that all necessary documentation is available, programs are installed, the duties are assigned, all required manual and automation tools are established, accurate test data and test environment are ready.

If the above-mentioned factors are maintained, then it is high time to start testing. The biggest problem of the test process execution is that after a certain number of test running, whether it was functional testing[2], user interface testing or performance testing, the operated and cycled work seems eventless and boring. This may lead to some bugs remained in software after the product release. But how to know that all defects are discovered and fixed? Let us work this out.

When to Stop Testing[3]: What Are Exit Criteria for Testing?

• All scenarios are performed several times.
• Regression testing[4] is obligatory fulfilled.
• The specified number of bugs is achieved.
• All errors with the highest priority are debugged.
• The “blocker” and “critical” mistakes are removed.
• At least 90% of test coverage is reached.
• The testing budget is used up.
• The deadline for the project is kept.

Thus, the set tasks and purposes at the entry criteria should be achieved in order to have the exit criteria productive and adequate.

Related Posts:

• How do You Know When to Stop Testing?[5]

Source URL: https://blog.qatestlab.com/2016/10/24/when-stop-testing/

---