Test Case - TwoGears/hakomo-guides GitHub Wiki
Test Case
- ID
Unique ID for each test case - Title
Test case title. E.g. verify login page with valid username and password. - Priority
/Low/Medium/High/ This is useful while test execution. Test priority for business rules and functional test cases can be medium or higher whereas minor user interface cases can be low priority. Test priority should be set by reviewer. - Module Name
- Test Designed By
- Test Designed Date
- Description
- Preconditions
(optional) SETUP and ADDITIONAL INFO. Any prerequisite that must be fulfilled before execution of this test case. List all pre-conditions in order to successfully execute this test case. - Dependencies
(optional) Mention any dependencies on other test cases or test requirement.
- Design State
Create test case
| Number | Step | Input Data | Expected Result |
|---|---|---|---|
| Number of the Step | List all test execution steps in detail. Write test steps in the order in which these should be executed. Make sure to provide as much details as you can. | Use of test data as an input for this test case. You can provide different data sets with exact values to be used as an input. | What should be the system output after test execution? Describe the expected result in detail including message/error that should be displayed on screen. |
- Postconditions
(optional) What should be the state of the system after executing this test case?
- Execution State
Execute test steps and write down result of each step
| Number | Step | Input Data | Expected Result | Actual Result | Status(Pass/Fail) | Notes |
|---|---|---|---|---|---|---|
| Number of the Step | List all test execution steps in detail. Write test steps in the order in which these should be executed. Make sure to provide as much details as you can. | Use of test data as an input for this test case. You can provide different data sets with exact values to be used as an input. | What should be the system output after test execution? Describe the expected result in detail including message/error that should be displayed on screen. | Actual test result should be filled after test execution. Describe system behavior after test execution. | If actual result is not as per the expected result mark this test as failed. Otherwise update as passed. | To support above fields if there are some special conditions which can’t be described in any of the above fields or there are questions related to expected or actual results mention those here. |
-
Bug ID
If test status is fail, then include the link to defect log or mention the defect number. -
Test Executed By
-
Test Execution Date