how much testing is enough.and why documentation is needed

Question Posted / chhabra chhagan

2 Answers
4490 Views
I also Faced
E-Mail Answers

Answers were Sorted based on User's Feedback

how much testing is enough.and why documentation is needed..

It totally depends on the exit criteria.
There are 7 exit criteria' s to stop testing
1. As soon as the release time is achieved
2. As soon as the budget is exhausted
3. When all of the planned testing is achieved with no major
pending issues
4. When the residual risk is minimal with no major pending
issues
5. When certain percentage of coverage is achieved in terms
of requirements/code/risks with no major pending issues.
It is also called thoroughness messure.
6. When predicted no. of defects are found with no more
major pending issues.
7. Based on testing, sufficient info is generated &share
with stake holders in letting them decide abt release.

DOCUMENTATION is necessary because
1. Maintaining documentation we can check the process.
2. find the defects easily.
3. requirements can be mapped.and can check whether each and
every req has been covered or not.
4. If defects are documented we can test whether the defect
functionality has been fixed properly.
5. In future if we get any project related to the same
domain we can use the metrics, also we will know which
module has to be concentrated the most

Is This Answer Correct ?

3 Yes

0 No

how much testing is enough.and why documentation is needed..

Answer / kalesha

if most of your test cases executed successfully based on
test matrix.. one can stop testing the release the application.

Is This Answer Correct ?

0 Yes

0 No

Post New Answer