Answer Posted / chandni
There are various points which we can consider to decide
that we have tested enough.
1. When the system is highly stable and no errors are
found .
2. When certain amount of test cases are run then
there is no error found that time we can say that we have
tasted enough
3. Probability of finding errors is lace then
4. When all the test cases are run
But we can not consider the deadline and budget depleted
part over here because this question defines that when we
think that we have tested enough not when to stop testing.
| Is This Answer Correct ? | 6 Yes | 0 No |
Post New Answer View All Answers
Please anyone give answers for all below questions and help ? realtimers please and please share your knowledge.lot of questions left unanswered.
6 what do you like least about testing?
Describe some staff conflicts you have handled.
plz send the test scenarios and test cases for "user name should contain 4 to 8 chars and they should have only vowels"
How can you use technology to solve problem?
What is common interface?
any one please send me any test case examples with tabular columns in manual testing
Explain some techniques for developing software components with respect to testability.
What is integration level testing?
When do we perform smoke testing?
What is a top-down and bottom-up approach in testing?
How does a coverage tool work?
Can you please provide me the standard testcase review templete and Test plan templete.In my company we are not following any Standards templete so.Please guve me some Excell attachments.
1.what promted you to become involved in QA/Testing?
iwant know IEEE formate ,how it is used and exactly where it is used? i have details it follows test plan, testcases...etc. i want real time explanation. pls any one give?
