Print Page | Close Window

When Should Testing stop?

Printed From: One Stop Testing
Category: Types Of Software Testing @ OneStopTesting
Forum Name: Manual Testing @ OneStopTesting
Forum Discription: Discuss All that is need to be known about Manual Software Testing and its Tools.
URL: http://forum.onestoptesting.com/forum_posts.asp?TID=6844
Printed Date: 13Mar2025 at 6:27pm


Topic: When Should Testing stop?
Posted By: Mithi25
Subject: When Should Testing stop?
Date Posted: 10Aug2009 at 11:14pm
HTML clipboard

When Should Testing stop?

 
"When to stop testing" is one of the most difficult questions to a test engineer.
The following are few of the common Test Stop criteria:

1. All the high priority bugs are fixed.
2. The rate at which bugs are found is too small.
3. The testing budget is exhausted.
4. The project duration is completed.
5. The risk in the project is under acceptable limit.

Practically, we feel that the decision of stopping testing is based on the level of the risk acceptable to the management. As testing is a never ending process we can never assume that 100 % testing has been done, we can only minimize the risk of shipping the product to client with X testing done. The risk can be measured by Risk analysis but for small duration / low budget / low resources project, risk can be deduced by simply: -

• Measuring Test Coverage.
• Number of test cycles.
• Number of high priority bugs.


-------------
http://www.quick2sms.com - Send Unlimited FREE SMS to Any Mobile Anywhere in INDIA,
Click Here



Replies:
Posted By: skumar75.qa
Date Posted: 18Sep2009 at 3:18am

Stop Testing:-

1) All the major and Seviority defects needs to be close
2) All the Test cases needs to be complete 100% Pass rate
3) All the Failed test cases needs to complte re-test
4) The project duration  and budget is completed
5) All the UAT's needs to be get sign off from customer
 



Print Page | Close Window