In my case if we are no more able to find severity 1 and 2 bugs and all the previously logged bugs are fixed and tracked to closure, we stop testing further.
Also before we stop testing we make sure that all the features mentioned in the scope of testing are tested.
English is neither my first language [img]/images/graemlins/smile.gif[/img] , but I believe that stopping testing means abnormal termination.
I would expect answers that are given above to question like "when testing is completed?" , but to question "when testing is stopped" I would answer "if there are defect(s) preventing as from doing the test as planned e.g. can't log in or can't start the application. Or sometimes when developers say that they have to do major rework of an application"
[ QUOTE ]
It depends........there can be many reasons...
You have covered all the test cases in traceability matrix.
Your Budget of testing
The bugs/issues falls below a certain limit.
[/ QUOTE ]
I agree with the first reason only.
Because manager should be aware both of budget and of time given for testing. If test cases are already been created, manager has to set priority.
Therefore I'd add to your "You have covered all the test cases in traceability matrix" accordingly to priorities.
[ QUOTE ]
I would expect answers that are given above to question like "when testing is completed?" ,
[/ QUOTE ]
The completion of Testing is usually stated in the test plan. It may be any criteria, but the most common one is the number of P2 and P3 bugs remaining in the system. For P2 bugs there should be known workaround.
But for some critical application the test completion criteria may be more hard like all the bugs had been tracked to closure and a regression test had been successfully run on the system.
"When Testing will be stopped?"
The answer should have to parts
1. Testing is stopped temporarily when
The reasons will be Work stopper Bug, New major release
Anticipation of Major requirement changes etc.
2. Testing stopped or testing "completed" when
Time ,Money ,Resources Budgeted for testing is over OR
When All Planned Testing activities completed with low probability of high priority Defects remaining in software.
Testing is essentially a Risk mitigation activity so It can be stopped when risk is reduced to acceptable level.( Risk
can not be zero or reducing risk becomes very expensive)
Testing is done to make sure that we get a reasonable, dependable product, with in a acceptable schedule at a reasonable cost.So you can stop testing whenever this is assured OR you continue testing till you get this assurance.
Most of the answers I have read here are good text book answers. But there are lots more reasons to stop testing. As Ainars says, there is a difference between "complete" testing and "abnormal termination" (stopping) of testing.
Here are some answers from the real world:
1. The version you are testing is superceded by a new build.
2. Emergent bugs prevent further testing.
3. Application flow is different than the testing flow (i.e. the test is out of date).
4. Testing environment goes down.
5. Ran out of time
6. Ran out of money
7. No testing resources available.
1. All identified tests activities have been completed.
2. Ran out of time (complete by fiat via project management)
3. Ran out of money (complete by fiat via project management)