QA checklist
Tick it off on this page, download it as Markdown or plain text, and take the picture with you.
The checklist, ready to tick
Thirty checks in six groups, in the order a release goes through them. Nothing you tick leaves this page.
Esto funciona en tu navegador. Nada de lo que pegues o abras se nos envía.
The same checklist as text
Copy the blank one into your own document, or read the filled-in one to see what a finished pass looks like.
# QA checklist
## Before you start
- [ ] Build and version under test recorded
- [ ] Test environment matches production
- [ ] Test data seeded and reachable
- [ ] Feature flags set as released
- [ ] Known open bugs reviewed
## Core journeys
- [ ] Sign up and sign in work end to end
- [ ] The main task completes in one pass
- [ ] Payment or submission confirms
- [ ] Emails and notifications arrive
- [ ] Navigation reaches every main screen
## Forms and input
- [ ] Required fields are enforced
- [ ] Errors name the field and the fix
- [ ] Long, empty and pasted values handled
- [ ] Submitting twice creates one record
- [ ] Values survive a validation failure
## Browsers and devices
- [ ] Chrome, Firefox and Safari pass
- [ ] One Windows and one macOS pass
- [ ] Mobile width down to 320px holds
- [ ] Portrait and landscape both usable
- [ ] Zoom to 200% keeps the page usable
## Accessibility and content
- [ ] Every control is reachable by keyboard
- [ ] Focus is visible on every control
- [ ] Images carry alt text
- [ ] Text contrast passes AA
- [ ] Copy is spelled and cased correctly
## Before you sign off
- [ ] Console is free of errors
- [ ] No failed or slow network calls
- [ ] Page loads within the agreed budget
- [ ] Every failure has a bug report
- [ ] Result recorded against the build# QA checklist
## Before you start
- [x] Build and version under test recorded
- [x] Test environment matches production
- [x] Test data seeded and reachable
- [x] Feature flags set as released
- [x] Known open bugs reviewed
## Core journeys
- [x] Sign up and sign in work end to end
- [x] The main task completes in one pass
- [x] Payment or submission confirms
- [x] Emails and notifications arrive
- [x] Navigation reaches every main screen
## Forms and input
- [x] Required fields are enforced
- [x] Errors name the field and the fix
- [x] Long, empty and pasted values handled
- [x] Submitting twice creates one record
- [x] Values survive a validation failure
## Browsers and devices
- [x] Chrome, Firefox and Safari pass
- [x] One Windows and one macOS pass
- [x] Mobile width down to 320px holds
- [ ] Portrait and landscape both usable
- [ ] Zoom to 200% keeps the page usable
## Accessibility and content
- [x] Every control is reachable by keyboard
- [x] Focus is visible on every control
- [x] Images carry alt text
- [x] Text contrast passes AA
- [x] Copy is spelled and cased correctly
## Before you sign off
- [x] Console is free of errors
- [x] No failed or slow network calls
- [ ] Page loads within the agreed budget
- [x] Every failure has a bug report
- [x] Result recorded against the buildThe picture, and how to use it
An image of a finished pass, sized for an article. Use it anywhere, with the credit line that is already part of it.
Paste this where you want it. The credit is baked into the image, and the link under it points back to the checklist so your readers can tick one off themselves.
<a href="https://session-replay.com/templates/qa-checklist-template">
<img src="https://session-replay.com/images/templates/qa-checklist-template.png" alt="QA checklist, filled in" width="1200" height="630">
</a>
<p>QA checklist by <a href="https://session-replay.com/templates/qa-checklist-template">Session Replay</a></p>Related
Test plan template
What you will test, and what you are deliberately not testing, before the checks start.
Bug report template
When a check fails, the report that gets it fixed without three follow-up questions.
Bug report generator
Answer the questions and the finished report comes out the other end.
Smoke testing
The five-minute pass that decides whether the rest of this checklist is worth running.
A failed check is a bug report waiting to be typed
The checklist says what to try. When one fails, capture the screen, the console and the browser details in one link instead of retyping them.