Interested to Buy Any Domain ? << Click Here >> for more details...
When should testing be stopped?
- 24 Answers
- 47028 Views
- GE, I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
Answer / rajeshwar rao
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
| Is This Answer Correct ? | 19 Yes | 1 No |
Answer / subhan.qa
when all the testcases are executed
bug arrival rate is down
dead line comes
| Is This Answer Correct ? | 15 Yes | 4 No |
Answer / sethupathy
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.
| Is This Answer Correct ? | 12 Yes | 1 No |
Answer / raghavender
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.
| Is This Answer Correct ? | 9 Yes | 0 No |
Answer / ch.s.m.prasad
All the customer requirements are tested.
All major defects are resolved.
time exceeded.
| Is This Answer Correct ? | 7 Yes | 2 No |
Answer / psrisusee
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.
| Is This Answer Correct ? | 4 Yes | 0 No |
Answer / pankaj ghate
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
| Is This Answer Correct ? | 4 Yes | 0 No |
Answer / ramprasad.s
Hi
When the Application Meets the Requirement.
sun_ramprasad@yahoo.com
| Is This Answer Correct ? | 5 Yes | 3 No |
Answer / shashank saxena
1. Deadlines
2. Test Budget Depleted
3. Bug rate falls below a certain level
| Is This Answer Correct ? | 4 Yes | 3 No |
Answer / parul
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.
| Is This Answer Correct ? | 1 Yes | 0 No |
if my documents (SRS &FRS) having erros(does not meets) the requirements in that situation,which document i should take to write the testcases?(othere wise which steps i should take? Thanks In Advance
how to do manual test?
i have 500 testcases , how to perform the regression testing
What is CMM and CMMI?
Who will repare SRS? What is the basis for SRS preparation?
How would you do the ollowing Security Testing for web application? 1) Authentication. 2) Authorization. 3) cookies. 4) penetration testing. 5) session testing. 6) encryption and decryption testing pls give examples give example i can't understand so pl
which type of testing we r doing at the begining of the project,and what r the next next testing at the application
How do ensure that we prepared Test cases for all the requiremets.. or how do we ensure that we didn't missed out any requirments...do we prepare any Tracebility matrix.. can anybody answer this question...
why it is know as alpha and beta testing(alpha & beta)?
what is the difference between primary key and foreign key
Is anybody have the telecom systems test cases from start to end?
Define load, performance and stress testing
Automation Testing 
