Interested to Buy Any Domain ? << Click Here >> for more details...
how much testing is enough.and why documentation is needed
- 2 Answers
- 5383 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 |
diff b/w alpha & beta testing? who will do this with examples? can u pls help in this topics
I want to do Advanced Level of Certification Course.Please let me know which lelel will be better for me.please let know after completion og Foundation Level,which level will be better for me?
what is the difference between developer testing and tester testing?
What is deferred status in defect life cycle?
How to test the Online Games?? Suggest tricks. I have experience in server-client application testing.
After recieved the defect from Tester,developer is not getting any error while executing that bug then he will reject that defect due to the above reason.As a Tester what we can do in that situation?
1. what are the different types of test cases techniques ?
the typical Application Test Lifecycle?
what is meant by deffered status
Suppose there is a User window (having fields First name, Last name, phone & address) What is the test case for Edit User ?
hey showed me a Web page containing 3 text boxes labeled as Name, D.O.B & Blood Group.It also have 3 Buttons as OK, CANCEL,Reset. They told me that 1) when you click on OK it'll route you to the next page and save the data in the database. 2) When you click on CANCEL it'll route you to the previous page. 3) When you click on Reset it'll clears all the entries made by you. Now they asked me to write Test cases to test the functionality of that web page & asked me to write 1 critical test case after which they will give final go ahead to test the rest of the application... I wasn't able to write the critical test case. Plz answer.
As soon as we get the build what type test we will do?and how?
Automation Testing 
