A user story is defined as done when the items listed below are met.
- All tasks within the User Story have been completed and the Acceptance Criteria have been met.
- The User Story has been tested in accordance with the Quality Strategy.
- Errors are caught and handled appropriately
- Code is unit tested and passed to appropriate levels for the story
- Pull requests are raised, reviewed, and accepted.
- Code is committed to the version control system.
- The User Story has been tested by the testing team on the QA environment.
- Code is deployed to the xxx environment (this is usually the QA environment but can be a different environment if appropriate).
- The User Story is updated in Azure DevOps Board/JIRA and sits on the QA column.
Optional
- Deployment notes are added (where applicable).
- Any CMS elements are identified and guidance notes are added to the ticket as to where they can be updated.
- All stories meet AA accessibility standards https://achecker.ca/checker/index.php
- For any stories that relate to user data ensure “Privacy by Design” standards are upheld in line with GDPR requirements
- Site events that need to be track-able using Google Analytics should have an appropriate ID.
Supported Browsers/Operating Systems
| Operating System | Browser | Version |
|---|
| iOS | Safari | Latest Release (Auto-update)
(and 1 previous version) |
| MacOS | Safari | Latest (Auto-update)
(and 1 previous version) |
| Android | Chrome | Latest (Auto-update)
(and 1 previous version) |
| Windows | Chrome | Latest (Auto-update)
(and 1 previous version) |
| Windows | Firefox | Latest (Auto-update)
(and 1 previous version) |
| Windows | Edge | Latest (Auto-update)
(and 1 previous version) |
Definition of Done-Done
- Full regression testing carried out and passed, with all low-severity bugs recorded (on stage)
- Penetration tests completed and results accepted
- Load tests completed and results accepted
- Response times are uniformly [xxx’s across the platform]
