When do I STOP testing?(Exit Criteria in Software Testing)

All testers have asked themselves this question at some point in their career. When do I stop testing a product and consider the job done?

You Can’t determine when to stop testing. Now a days software applications are so complex and should run in a interdependent environment that complete 100 % testing can never be done. Few things are there to stop…. There are some markers that help us in determining the closure of the testing phase of software development life cycle.

  • completed with certain percentage passed – Depending on the system, testing can be stopped when an agreed upon test case pass percentage is reached.
  • After successful test case execution – Testing phase can be stopped when one complete cycle of test cases is executed after the last known bug fix.
  • Project Duration Complete – Testing can be stopped after deadlines get met with no high priority issues left in system.
  • Mean Time Between failure (MTBF)– MTBF is the time interval between to inherent failures. Based on stakeholders decisions, if the MTBF is quite large one can stop the testing phase.
  • Based on Code coverage value – Testing phase can be stopped when the automated code coverage reaches a certain acceptable value.
  • All the high priority bugs are fixed – Testing phase can be stopped when we found that all high and medium priority labeled bug are solved.

 

Advertisements

One thought on “When do I STOP testing?(Exit Criteria in Software Testing)

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s