When do you stop testing?
Answers were Sorted based on User's Feedback
Answer / dillip palai
Some of the common factors and constraints that should be
considered when decided on when to stop testing are:
1. Testing budget of the project. Or when the cost of
continued testing does not justify the project cost.
2. Resources available and their skills.
3. Project deadline and test completion deadline.
4. Critical or Key Test cases successfully completed.
Certain test cases even if they fail may not be show stoppers.
5. Functional coverage, code coverage, meeting the client
requirements to certain point.
6. Defect rates fall below certain specified level & High
priority bugs are resolved.
7. Project progresses from Alpha, to beta and so on.
| Is This Answer Correct ? | 10 Yes | 1 No |
Answer / dheeraj shandilya
Testing is the process of assessment of quality.We also
know exhaustive testing is impractical to achieve.
So we should stop testing at some point.These some point
are defned by exit criteria.
Like
1.) Availability of staff, Material, tools required for
testing.
2.)Undesirable outcome that could result from shipping too
early (Risk)
3.)The status of the important quality characteristics
4.)the portions of the test basis, the software code covered
5.)Number of test run , Passed , Failed, Bocked
6.)The number of defect known to be present, its arrival
rate
7.) Money i.e. the cost of finding the next defect in
current level than finding that in next level of testing
| Is This Answer Correct ? | 2 Yes | 1 No |
Answer / castor_troy
Testing is stopped under 2 conditions :
1) when all the conditions mentioned in exit criteria is met.
2) If there is a request from the client to stop testing.
| Is This Answer Correct ? | 0 Yes | 0 No |
In simple steps how will you do unit testing using VSTS?
How many flows of Events are there?
Can we use automation tools during static testing? If yes when and how?
How many testcases can you write an avg for a day?
. Batch testing in how many ways u perform in QTP ?
What is the concept of introducing a small change to the program and having the effects of that change show up in some test?
How do u write integration test cases?do u have any special format?
Can you explain capability levels in continuous representation?
Explain the V-Model
What is Bugzilla? Can I used it manually, If yes then how can i used it? Can I used it in .NET Environment?
Should every business test its software the same way?
How do your characteristics compare to the profile of the ideal manager that you just described?