A QA review checks that a pattern, component, or template works as expected before release. By reviewing both design and code implementations, you catch issues early, reduce bugs, and build trust in the system. Use this before releasing new work or after making major updates.
QA Review
How to
-
Set criteria
Agree what "done" means for both design and engineering, using your Minimum Viable Checklist as an aid. Include visual consistency, performance, interaction states, and outcomes from an Accessibility Review.
-
Check design output
Verify that the design matches your system's tokens, naming standards, and specs. Flag inconsistencies or missing states.
-
Check code implementation
Review the coded version for fidelity, accessibility, and performance. Confirm it works across browsers and devices.
-
Review platform differences
Use Platform Overrides to document and agree on differences for iOS, Android, and web.
-
Document findings
Capture issues, prioritise fixes, and update guidance so teams have visibility.
-
Sign off and release
Once issues are resolved, approve the work for rollout and follow your Release process to communicate and scale changes.
Generate test cases: Use AI for comprehensive test cases including happy path, edge cases, and accessibility checks. Run visual regression testing. Human QA still validates real-world usage.