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.
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
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
What is Test Data?. When we prepare test data?, is it
included in Test Cases or should it be seperately prepared.
What and when will be the actual use of Test Data and who
prepares it.
question about bug is valid or invalid ?
suppose i don't have srs i want suggest close button in one
form but the developer says client no need that one
in this situation the bug is valid or invalid?
1.The effectiveness of a test suite in detecting errors can
be determined by counting the total number of test cases
present in the test suite.
2.Black-box testing attempts to find errors in which of the
following categories
Option 1 Incorrect or missing functions
Option 2 Interface errors
Option 3 Performance errors
Option 4 All of the above