we can stop testing when test coverage is 100%. when there 
are no defects found in the build. and also by traecability 
matrix.(prepared by test lead)

HI


1.When Requirement is met.

2. User is Satisfied.

sun_ramprasad@yahoo.com
9940314706.

1.  When there is no time and budget
2. When maximum number of test cases are executed
3. All the Requirements are mapped that is RTM is filled 
completely
4. When Test coverage is > 80%
5. when bug rate falls below certain level

The decision that when to stop testing or we have tested 
enough depends on the Budget and available time for the 
project.

It depends upon..

1) The TestCases prepared from the UseCase which cover's 
all the features/functionality of SUT.

2) When the error rate is very low.

(And ofcourse Time and Budget as All Say). Actually it 
depends, how they prepare the plan's for their project..

As you all say, it depends on time, but not budget and also 
mainfactor is that it depends on base criteria. When 
acceptance criteria is met we can feel like we had enough 
testing.  When it reaches acceptance criteria means when 
all the test cases that are developed basedon customer 
requirements are passed we can say that we have tested 
enough.

1.when it meet all the user requirements.

2. When there is no defects in the build.

3.When all the test cases which are made on user 
requirements are passed then we can decide tested is enough.

There are various points which we can consider to decide 
that we have tested enough. 
1.	When the system is highly stable and no errors are 
found .
2.	When certain amount of test cases are run then 
there is no error found that time we can say that we have 
tasted enough
3.	Probability of finding errors is lace then 
4.	When all the test cases are run  

But we can not consider the deadline and budget depleted 
part over here because this question defines that when we 
think that we have tested enough not when to stop testing.

Testing is potentially endless. We can not test till all 
the defects are unearthed and removed -- it is simply 
impossible. At some point, we have to stop testing and ship 
the software. The question is when. 

Realistically, testing is a trade-off between budget, time 
and quality. It is driven by profit models. The 
pessimistic, and unfortunately most often used approach is 
to stop testing whenever some, or any of the allocated 
resources -- time, budget, or test cases -- are exhausted. 
The optimistic stopping rule is to stop testing when either 
reliability meets the requirement, or the benefit from 
continuing testing cannot justify the testing cost.  This 
will usually require the use of reliability models to 
evaluate and predict reliability of the software under 
test. Each evaluation requires repeated running of the 
following cycle: failure data gathering -- modeling -- 
prediction. This method does not fit well for ultra-
dependable systems, however, because the real field failure 
data will take too long to accumulate