In many condition we hav to stop Testing:

1) If Specification is not proper
2) If so many so many show stoper bugs are their
3) Functionality is not meating to the Specification
4) Environment is not proper to test (System Environment)
  .....

1.When the allocated time exceeds, allocated cost exceeds
2.When deadlines are met
3.showstoper kind of issue is found
4.bug rates fall below certain level 
5. when test cases are complete

Hai,

According to my knowledge we can't say when we r going to 
stop the testing.But.........
1.As soon as the code meet the previous  agreed up on the 
defects per KLOC
Ex: take the project, that project can be released when 
there is an average errorpercentage of .2 defects per KLOC
2.when the cost invested on testing exceeds the revenue 
that can de incurred by the testing

Hi,

    - If the bug rate falls certain level.
    - if the build is not stable.( if the main    
unctionalities are not working )
    - if there are lot of change requests(CR's).
    - And all the functional requirements are covered.

Let me know if there any mistakes.



Regards,
Satya.k

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

all the above answer is right but the question is open 
ended it is tricky one - boz we can keep on do the testing 
if you are going to upgrade the requirement - always every 
concern want to upgade with latest tech. - until it full 
fill the custmer requirement and needs the quality within 
the time frame and cost then we can stop testing

Typically testing is an endless process.

- When the project meets its dead line.
- After client finishes his UAT testing.
- When we execute all the test cases.
- After all the functionality works.
- When test budget is reached 

V.Allwin
helloallwin@gmail.com

when to stop testing will varies from company to compan
.some companies  follow ZERO DEFECT POLICY.

that means whatever the defects raised by testengineer
should be closed

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
  .