How do you know that the testing is complete?

Question

As a test lead, how do you know that the testing is complete and the release is good?

Answer 1

I believe testing exit criteria is as below:

1- calculate test coverage like created 10 test cases for 3 features out of 4. your test coverage is 3/4.

2- how many test cases are failed, passed or not executed.

3- define priority and severity of each test case

4- depending upon above three factors, you can measure how much further testing is needed.

Moral: if further testing needed ratio is 5%-10%, then I think no further testing needed. If you now do further testing, it will be exhaustive testing. So it is better to leave here and complete your testing docs.

Those testing docs are meant for stakeholders for their decision making and for support team for agile maintenance phase.

Hope that answers

Comments

Good answer. Thank you.

Answer 2

This really depends on what type of cycle / spring you have, if you complete verifying all the stories as well as regression level specified for that particular build/ sprint with all types of testing required including backend, integration, etc.

Answer 3

There are some points which indicate that testing is complete:

1-The exit criteria that was mentioned in the test plan document is achieved.

2-when we achieved no. of successful test case execution at a specified level.

3-when the rate of bug finding decreases from a specified level.

4-when the manager said that ok stop.

5-when we don’t have enough time to perform more tests and have achieved a specified level of quality.

6-when the cost of fixing a bug is more than the impact of the bug in the system.

There are a plethora of tools available online, but some are unable to deliver the desired results. I recently came across a tool called QAppAssure which allows you to test on-cloud and on-field devices, across 100+ device, make and models, Integrate with Jira, CI/CD tools, and also use Appium, Calabash, Espresso, UI Automator, XCUITest.