![]() ![]() In the above example there are unnecessary outcomes of several test steps. When you write a test case, you don’t need to specify the expected result for each test step if the result is obvious. When testers report defects based on the test case, they should indicate which test step failed, in order to make troubleshooting easier. ![]() If you only have a few test steps, you should probably consider making a checklist instead – it’s not worth your while to keep track of a lot of small test cases when a checklist will do the job just as well. You should have 3-8 test steps in a test case. The test case has multiple test steps, some of which have expected result and some which do not. This is a fairly common structure that contains a number of important points. Your test could also include any pre-conditions or assumptions that are necessary for the test to be successful, such as the user must already be registered with the software. Verify response when a valid email address and password is used Here is a simple test case template with an example: Test Case No. The test case should include its number, a description, the test data, expected result, actual result and status (whether the test passed or failed). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |