Test scripts
- Ian Dillon
- Astrid Decrop
Purpose of test scripts
Test scripts are detailed, step-by-step instructions that outline how to test a particular functionality or feature of a product.
Test scripts are designed to verify that the application behaves as expected and meets the acceptance criteria defined in the user stories. By executing test scripts, we ensure that the product is of high quality, free of defects, and provides a seamless experience for the user.
Guidelines for writing test scripts
Align with acceptance criteria and user stories
Each test script should directly relate to a specific user story and its associated acceptance criteria.
This is to ensure that all user requirements are thoroughly tested and validated.
Cover all user flows, including happy and unhappy paths
Test scripts should encompass all possible scenarios, including both happy paths and unhappy paths (error conditions and exceptions). This comprehensive approach helps identify potential issues that could affect user experience.
Include detailed steps and expected results
We suggest that each test script should contain:
Test case ID: A unique identifier for tracking purposes
Test description: A brief summary of what is being tested
Preconditions: Any prerequisites that must be met before executing the test
Test steps: Step-by-step instructions to perform the test
Expected results: The anticipated outcome for each step or at the end of the test
Prioritise test scripts
Prioritise test scripts based on the prioritisation used for the user stories they cover and the impact on KPIs and strategic goals. Critical functionalities should be tested first to mitigate significant risks early.
Include necessary metadata
Provide essential metadata for each test script to aid in tracking and reporting, such as related user story ID, priority level, tester assigned, ate of execution, and test environment.
Automate where possible
Automate repetitive and critical test scripts, especially for regression testing.
Document defects thoroughly
When a test fails, document the defect with detailed steps, screenshots, and logs. This information aids developers to be able to diagnose and fix issues.