This test case format is suitable for manual system test cases.
The test cases should be written in enough detail that they could be given to a new team member who would be able to quickly start to carry out the tests and find defects.Purpose: | Short sentence or two about the aspect of the system is being tested. If this gets too long, break the test case up or put more information into the feature descriptions. |
---|---|
Prereq: | Assumptions that must be met before the test case can be run. E.g., "logged in", "guest login allowed", "user testuser exists". |
Test Data: |
List of variables and their possible values used in the test case.
You can list specific values or describe value ranges. The test
case should be performed once for each combination of
values. These values are written in set notation, one per
line. E.g.:
loginID = {Valid loginID, invalid loginID, valid email, invalid email, empty}
password = {valid, invalid, empty}
|
Steps: |
Steps to carry out the test. See step formating rules below.
|
Notes and Questions: |
|
Each step can be written very tersely using the following keywords:
Every test case must include a verify step at the end so that the expected output is very clear. A test case can have multiple verify steps in the middle or at the end. Having multiple verify steps can be useful if you want a smaller number of long tests rather than a large number of short tests.
For more information on advice, see: