To stop a testing depends on many factors.
1- When the defect finding density is reduced pre KLOC
(Kilo Lines Of Code).
2- When the time and budget sanctioned for the testing
depletes.
3- Release date is nearby.
The testing can be stopped when
1. when we running out of time
2. If budget crosses the limit
3. It depends on the project and release
If Im wrono pls correct me
Muralidharan
dharanmu@yahoo.com
1.When all the core functionality is working
2.System satisfied the exit criteria as agreed in the test
plan
3.Nearing the release date
Please note: Release can go with know bugs and thus we
should be confident enough thhat the core functionality is
working as it suppose to.
It is very difficult to determine when to stop testing
Because it depends upon the some of the testing to be
follow
1. When Alfa and beta testing gets over.
2. Defect rate follows down below the criteria
3. When the test manger is confident when the application
will perform as expected in the production environment
4. Bug rate falls down below the criteria.
5. Test budget
6. Deadlines to be relised the project
It is not very difficult to know "When to Stop Testing?"
In the Test Plan there is somthing called Exit Criteria,
Where the Product release status has been defined
clearly.I.e. when to stop testing.
- If defect dencity level is predictable low.
- Test Schedule has been reached.
- If Build meets the requirment.
How testing is necessary and when it should be stopped
depends upon a variety of facts which are as follows;
1: When the core functionality according to the SRS
(Software requirement specification) is tested.
2: When all the requirements mapped to the given
functionality are tested.
3: When all the designed test cases are executed for the
functionality.
4: After Regression testing is done: IF the functionality to
be tested can affect other related functionalities.
5: Depending upon the exit criteria mentioned in the Test plan.
6: in case of re testting when all the required priority
test cases has been tested (As agreed upon by stake holders
of the product).
7: In case off shortage of resources (Billing, delivery
date, etc) when all the critical and blocking scenarios have
been tested.
As this is my first post on any website please let me know
if there are any suggestions or improvements.
Thanks,
Pankaj
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.
[Yang95] 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.
Testing can be stopped when
1. Application meets the Exit criteria specified in the
Test Plan.
2. Or when the application meets the client requirements
also we can stop the testing.
Hi frnds im Priyan.in interviews they are one question 4r
me. " AS A TESTER, WHAT IS UR GOAL OR AIM OR AMBITION..? "..
can any one gve answer perfect answer ? tank u .. reply me plss
What is SDLC Model used in ypur company ? What is best
Model from Testing point Of View ? Which comes first
Verification or Validation ? Which is most important
Verification or Validation? What u'll chose to do if
suppose to work ANY 1 . & Why ?
To Refer this Site to Your Friends 
Site Map
