A Good Test Case Means..?
Answers were Sorted based on User's Feedback
Answer / sailaja
a good test case is one that discovers as many as not yet
discovered errors or bugs.
a successful test case is one that is successful to find
the desired bug
| Is This Answer Correct ? | 2 Yes | 0 No |
Answer / malli
it should be smple understandable & powerfull mean should
not have diffects
| Is This Answer Correct ? | 2 Yes | 0 No |
Answer / samuel david dhas, banyan soft
Designing good test cases is a complex art. The complexity
comes from three sources. Test cases help us discover
information. Different types of tests are more effective
for different classes of information. Test cases can
be "good" in a variety of ways. No test case will be good
in all of them. People tend to create test cases according
to certain testing styles, such as domain testing or risk-
based testing.
| Is This Answer Correct ? | 1 Yes | 0 No |
Answer / pavan kumar
A test case is written to check the positive flow of the
application
If we find more number of errors for a single test case
written then that test case can be called as aGOOD TEST
CASE because we are covering the maximun flow with that
written test case
| Is This Answer Correct ? | 1 Yes | 0 No |
Answer / rajeshwar rao
A good testcase means which has high probability of finding
on error in the developed system.
| Is This Answer Correct ? | 1 Yes | 1 No |
Answer / vsnraju19
which has highest probability of finding the defect.
| Is This Answer Correct ? | 0 Yes | 2 No |
Answer / santosh
A Good test mean how many defect are covering with that
test cases.
| Is This Answer Correct ? | 0 Yes | 2 No |
What is defect masking?
Relative to other technical groups in the company? Relative to your staff?
What is the responsibility of programmer’s vs QA?
can anyone give me a good example for creating Bug report with all its mandatory field
when developer will found bug they will store that bug in Dts 1- yes 2 - sometimes 3 - No 4 - none of these
What is meant by entry criteria and exit criteria in software testing?
Can you explain how one defect leads to other defects?
How many testcases have you written till, now as an average per project?
can anybody tell me what is thread testing with a practical example,coz the defn is liitle complex it seems.
Give me some sertification courses in testing?
What test cases should be written in performance testing manually?
Tell me the test cases for a search and replace functionality in a microsoft document (.doc)?