Interested to Buy Any Domain ? << Click Here >> for more details...
how much testing is enough.and why documentation is needed
- 2 Answers
- 5367 Views
- I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
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 |
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 |
write test case for 1<=a<10;10<=b<=20 using boundry value analysis
Describe to me what you see as a process. Not a particular process, just the basics of having a process.
What is the test case?
what is software testing
what is the diff between verification and validation.is verifiction and validation will takes place in each and every phase..pls send a clarified answer
When the Developer fixes and releases a defect.. then the tester tests it and fails the defect. Suppose the developer again fixes it and the tester again fails it and this process continues for the same defect for more times then what is that u do for getting the defect closed?
how do u define quality of software?
I need a brief decsrpition on How to test borwser compatabilty and O.S compatibity? Wat are the techniques to test? TIA
How you will do the functional testing ?
what do u like in QA?
CAN ANY ONE PREPARE TEST CASES FOR SUPPLY ACHAIN MANAGEMENT AND IF YES I WILL GIVE THE REQUIREMENT WHICH CONTAINS NEARLY 27 PAGAES
Process and procedures followed while writing Integration testcases and system test cases
Automation Testing 
