Structure of a Manual Test Script
A well-structured test script includes several components to ensure completeness and clarity:
- Test Script ID: A unique identifier for tracking and referencing the script.
- Title: A brief description of what the test script covers.
- Objective: The goal or purpose of the script (e.g., “Verify user login functionality with valid credentials”).
- Preconditions: Conditions or setup steps that need to be in place before executing the test (e.g., “User must be registered in the system”).
- Test Steps: Detailed, step-by-step instructions that the tester should follow to execute the test.
- Test Data: Any specific data values or variables used in the test, such as login credentials or form inputs.
- Expected Results: The outcome expected after each step or at the end of the test to determine if the application behaves correctly.
- Actual Results: Document the actual behavior observed during testing; this is recorded to compare against the expected result.
- Pass/Fail Status: The status based on whether the actual results match the expected results.
- Remarks: Any additional notes, such as bug ID if a defect was found.