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.
The objective of any Testing activity is to find the defects at the earliest stage. To test a product we must know
1. "What all the features to be tested?" (Objective of testing)
2. "How to test the features?" (Steps to test the objective)
3. "What will be the result if I execute the steps given to test the features?" (Expected behavior of the output for the objective) So, a good test case should be more precise. And it should be more focus towards testing one particular functionality rather than covering all functionality.
A test case is a document that describes an input, action, or event and an expected response, to determine if a feature of an application is working correctly. A test case should contain particulars such as test case identifier, test case name, objective, test conditions/setup, input data requirements, steps, and expected results.
A Test case is a sequence of steps to be executed to test the expected results for a part of am application. A test case could be defined for any of the following:
Data entry or data displayed
Functionality flow
Calculation
Desired output
Drop down list values
Data ranges and data values
Basically anything the tester need to define to make sure the application does not functional incorrectly at any certain scenario.
Posts
No comments:
Post a Comment