When we know that testing is complete?

Questions by prakash_534

Showing Answers 1 - 12 of 12 Answers

Abhay Kumar Tripathi

  • Feb 9th, 2006

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 acheived no. of successful test case execution at a specified level.

2-when rate of bug finding decrease from a specified level.

3-when manager said that ok stop.

4-when we dont have enough time to perform more test and have acheived a specified level of quality.

5-when the cost of fixing a bug ismore then the impact of the bug in the system.


  • Sep 22nd, 2006

That is complicated question. As far as build remains testing remains.

when ever customer requests for new featuere at that time complete and pure regression testing takes place.

thank u



  Was this answer useful?  Yes


  • Dec 10th, 2006

we know that testing is complete when all bug status in the life cycle are closed.


My Email:kollasudhakar2005@yahoo.co.in

  Was this answer useful?  Yes


  • Jul 12th, 2008

God will decend and gently stroke your cheek, telling you that you did well my son.  Seriously, how could it ever be complete?  The question is one of balancing compeating priorities.  Sometimes marketing pressures require a product to be released early DOS 6.0 is a classic example, it just "wasn't ready" in the words of one team member I talked to.    The way that you know it is ready is that the bug counts are low, especially the critical bugs.

  Was this answer useful?  Yes

Vedika Ahluwalia

  • Jun 16th, 2014

Following will be the different criteria when we should stop testing:

1. When the bug rate has fallen down a certain level.
2. When all the test cases have been executed and when the exit criteria has been met.
3. When the testing budget has depleted.
4. When the timeline has reached.

  Was this answer useful?  Yes

Korey Hinton

  • Oct 19th, 2014

For me I don't feel that testing is done until Ive checked off every test scenario listed in my testing checklist. The items on the checklist come from past bugs that were missed from testing in the past. The chances are that the same developers will make the same mistakes and assumptions in the future. Here is a simple iOS Testing Checklist I use myself: http://www.koreyhinton.com/blog/ios/am-i-really-done-testing.html

  Was this answer useful?  Yes

Shraddha Joshi

  • Sep 22nd, 2015

When all the prepared test cases are tested and confirmed. And all the checklist of Exit criteria is covered.

  Was this answer useful?  Yes


  • Nov 24th, 2016

when the number of bugs are less than the threshold value and when management says to stop the testing and when the product is completley stable that time i stop testing..

  Was this answer useful?  Yes


  • Aug 3rd, 2017

Testing will stop when it has already reached testing deadlines and completion of test case execution.

  Was this answer useful?  Yes


  • Jun 1st, 2018

When I remove all the P1 and P2 bug from my applications. Then I say testing is complete.

  Was this answer useful?  Yes

Ankur Maharaj

  • Nov 13th, 2018

Following points indicate for stop testing
1.Based on BRD & FRD document cover all possible functionality
2 Create scenarios with help of BRD & FRD then make maximum test cases which is possible
3.Execute all test cases and log defect.
4.When status of defect is closed then we can stop testing

  Was this answer useful?  Yes

Give your answer:

If you think the above answer is not correct, Please select a reason and add your answer below.


Related Answered Questions


Related Open Questions