# General Test Automation Standards · AT

These standards apply to all automated tests, including performance tests. Standards for writing functional tests are in the [Playwright standards](/standards/engineering/coding-standards/playwright).

## Standard Metadata

- Area: Automated Testing
- Owner: Technical Leadership group
- Last reviewed: 2026-09-09
- Next review due from: 2026-12-01
- Enforcement: Code review
- Status: Active
 

## Regression tests must be automated · AT-01 · **MUST** · **TEST**

Automate all regression tests to ensure repeatability and reduce manual effort.

## Tests must be run automatically when new functionality is released · AT-02 · **MUST** · **TEST**

Configure automated tests to run as part of the release process for new functionality.  

## Tests must be actively maintained · AT-03 · **MUST** · **TEST**

Actively maintain all tests as the system evolves.  
This includes:
- Checking pipelines after each run.
- Addressing failing tests as soon as possible, following the process in the project's test strategy.
- Reprioritising tests as project priorities change.
- Deleting tests that are no longer relevant or valuable.

## There must be a link between automated test pull requests and work item(s) they test · AT-04 · **MUST** · **TEST**

Reference the relevant work item(s) in pull requests containing automated tests to ensure traceability between code changes and requirements.