When Should We Stop Testing ?
Often we see software testers very enthusiastic at the beginning of the project. We create testing documents such as Test Strategy, Test Plan or Test Cases willingly and enthusiastically.
Then we get to testing software with a BANG! This is only amplified by the interesting defects we find at the beginning of the project. Getting them resolved will only add to our achievement.
In today’s article, I would like to share my thoughts on how to conclude testing activities when we reach a point in our testing cycle where we can say this testing is enough.
The progress of Testing:
Testing measurements can help the analyzers to take better and exact choices; like when to quit testing or when the application is prepared for discharge, how to track testing progress and how to quantify the nature of an item at one point in the testing cycle.
We can calculate our testing results using different formulas:
1. Completeness percentage:
Executed Test Cases/ Total Test Cases
2. Passed Test cases percentage:
Passed Test Cases/Executed Test Cases
3. Failed Test cases percentage:
Failed Test Cases/Executed Test Cases
Most Common Statements about when to stop testing:
1) When the due dates come then testing should be stopped.
2) When no bugs are found after running multiple cycles of testing then testing should be stopped
Finally, how to decide when to stop Testing, if certain conditions occur:
I think there is not a specific condition to decide that when to stop testing and many testers believe that there is not a certain point where testing should be stopped.
There are a number of factors to consider before we conclude that when should we stop testing.
This can be difficult to decide. Most software applications and systems are so complex and run in such a dependent environment, that complete testing can never be done.
List of factors to decide when to stop testing are:
- Test cases completed with acceptance percentage
- Test budget short
- Coverage of code/functionality/requirements reach a specified point
- Bug rate falls below a certain level
- There are no known critical bugs
- Beta or alpha testing period ends
Software testing is potentially an endless activity which could be carried on and on to the point of absurdity. It is difficult to define when to stop testing, as testing is a never ending method and no one can say that any software/application is 100% tested.
As logical as we struggled to influence it to sound, the choice to quit testing is still generally guided by a feeling of instinct increased over years of experience.