Print Page | Close Window

When to stop testing?

Printed From: One Stop Testing
Category: Software Testing @ OneStopTesting
Forum Name: Test Plans @ OneStopTesting
Forum Discription: Discuss, Learn and Prepare better and better Test Plans for yourself.
URL: http://forum.onestoptesting.com/forum_posts.asp?TID=693
Printed Date: 31Dec2024 at 12:04am


Topic: When to stop testing?
Posted By: Anamica
Subject: When to stop testing?
Date Posted: 05Apr2007 at 3:30am
Hi,
    How can it be known when to stop testing?


Replies:
Posted By: Badri
Date Posted: 01May2007 at 10:31pm

afeter conducting the user acceptance testing.

when the code is error free,and u have to check whether the build is satisfying the all the requirements.if it satisfies all the  equirements we can stop testing.



-------------
BADRI

Posted By: somanianand
Date Posted: 07May2007 at 11:00pm

1·       Thumbs Up    This can be difficult to determine. Many modern software applications are so complex, and run in such as interdependent environment, that complete testing can never be done. "When to stop testing" is one of the most difficult questions to a test engineer. Common factors in deciding when to stop are:

1.  Deadlines ( release deadlines,testing deadlines.)
    2.   Test cases completed with certain percentages passed

·                    3.  Test http://www.onestoptesting.com/introduction/test-stop.asp - ·                          4. Coverage of code/functionality/requirements reaches a specified point

·                                5. The rate at which Bugs can be found is too small

·                                       6. Beta or Alpha Testing period ends

·                                              7. The risk in the project is under acceptable limit.


Posted By: Aman Kumar
Date Posted: 02Jul2007 at 4:43am
1.) Test budget is depleted.
2.) When bug rate is fall from given thershold.

Posted By: erkamalbansal
Date Posted: 08Dec2007 at 1:51am
1  Deadlines ( release deadlines,testing deadlines.)
2.  Test cases completed with certain percentages passed

·     3.  Test budget depleted

·     4. Coverage of code/functionality/requirements reaches a specified point

·     5. The rate at which Bugs can be found is too small

·     6. Beta or Alpha Testing period ends



-------------
Kamal Bansal
QA Engineer

Posted By: rajinimohan
Date Posted: 28Jan2008 at 5:08am

·        Deadlines, e.g., release deadlines, testing deadlines;

·        Test cases completed with certain percentage passes;

·        Test budget has been depleted;

·  Coverage of code, functionality, or requirements reaches a specified point

·        Bug rate falls below a certain level; or

·        Beta or alpha testing period ends.



-------------
Rajini Mohan


Print Page | Close Window