Manual QA Testing Checklist for Release-Ready Builds

Manual QA remains essential for exploratory depth, usability judgment, and release confidence. Automation catches known regressions; skilled manual testing finds what scripts were never written to see. Use this checklist as a reusable baseline for feature testing, regression, UAT, and production readiness reviews.

How to use this checklist

• Start with smoke before deep testing
• Prioritize by business risk (payments, auth, data integrity first)
• Record environment, build/version, role, and browser/device for every cycle
• Mark N/A for sections that do not apply
• Block release on critical/blocker defects unless explicitly accepted

1) Pre-test setup

• Correct build/version deployed to the target environment
• Test accounts ready for each role (user, admin, etc.)
• Feature flags / config match release intent
• Test data prepared (and disposable where needed)
• Known issues list reviewed before new findings

2) Smoke checklist (must-pass)

• App/site loads without major errors
• Login / logout works
• Primary navigation works
• Top 3–5 critical user journeys complete successfully
• No crash/blank screen on first-run paths
• Basic create/view/update for core entity works

3) Functional testing

• Requirements/acceptance criteria covered for in-scope features
• Positive paths pass
• Negative paths show clear validation errors
• Required fields enforced
• Optional fields behave correctly when empty
• Edit/update persists after refresh
• Delete/archive flows confirm and remove access correctly
• Search, filter, sort, and pagination stay consistent
• Uploads/downloads work with allowed file types/sizes

4) UI/UX & usability

• No overlapping/clipped text on key screens
• Buttons/links have clear labels and states (default, hover, disabled, loading)
• Empty states are helpful
• Loading indicators appear for slow actions
• Success/error toasts are readable and dismiss correctly
• Forms are usable with keyboard tab order
• Mobile web layout does not break primary flows (if applicable)

5) Cross-browser & cross-device

• Chrome / Safari / Firefox (as required by product support matrix)
• Desktop + at least one mobile viewport
• iOS Safari / Android Chrome for mobile web
• No major layout or functional break on small screens

6) Roles, permissions & session

• Each role sees only allowed menus/actions
• Direct URL access blocked for unauthorized pages
• User A cannot access User B records
• Session expires / logout clears protected content
• Back button does not expose secured pages after logout

7) API / data sanity (manual + tools)

• Critical API calls succeed with valid auth
• Invalid/expired tokens are rejected
• UI state matches API/database after create/update
• No obvious sensitive fields leaked in responses
• Exports match on-screen filtered data

8) Network & resilience

• Clear message when offline / server unreachable
• Retry works after connectivity returns
• Slow network does not freeze the UI permanently
• Duplicate submit (double-click) does not create duplicate records

9) Accessibility & content basics

• Keyboard can complete critical journeys
• Focus is visible on interactive elements
• Form errors are understandable
• Meaningful images have alt text (spot-check)
• Contrast is readable on primary screens (spot-check)

10) Regression pack

• Impacted modules retested after fixes
• Adjacent high-risk modules smoke-tested
• Previous production bugs in related areas rechecked
• No new critical defects introduced by the fix

11) UAT & stakeholder validation

• Business scenarios agreed with product/owner
• UAT environment and data prepared
• Stakeholder sign-off captured (or blockers listed)
• Open questions documented with owners

12) Release readiness sign-off

• No open critical/blocker bugs
• High bugs reviewed and accepted or fixed
• Known issues documented with workarounds
• Test summary shared (scope, coverage, residual risk)
• Build/version approved for production

Sign-off template
Release:
Build/Version:
Environment:
Tester:
Date:
Smoke: Pass / Fail
Critical open: Yes / No
Decision: Go / No-Go
Notes:

Used consistently, this manual QA checklist keeps releases disciplined: smoke first, risk next, evidence always, and a clear go/no-go decision at the end.