QA Review Checklist

Quality Assurance verifies that delivered work behaves correctly, meets agreed expectations, and can be used confidently by real users. QA does not redesign features or redefine requirements—it confirms that what was built is ready to deploy.

Functional Correctness

• Feature meets the acceptance criteria
• All expected paths function correctly (not just the happy path)
• Edge cases handled (empty states, missing data, long inputs, etc.)
• No regressions introduced to existing functionality

Validation & Error Handling

• Required fields and rules enforced correctly
• Validation messages are clear, accurate, and actionable
• User can recover from errors without losing information
• No silent failures or confusing error states

UX Interaction

• Actions are discoverable and predictable
• User flows match the intended workflow
• Buttons, links, forms, and interactive elements behave as expected
• No dead ends, unclear steps, or missing feedback

(QA checks for usability issues, not design opinions.)

Visual & Layout Consistency

• Layout renders correctly at normal breakpoints
• Components match the design system where applicable
• No clipping, overlapping, or unreadable content
• No placeholder text, lorem ipsum, or visibly unfinished UI

Responsiveness

• Feature usable on desktop, tablet, and mobile
• Critical interactions remain accessible across breakpoints

Performance Basics

• Page or interaction feels responsive
• No unnecessary reloads, long delays, or obvious jank
• No excessive API calls or visible loading flickers without feedback

Security & Data Integrity

• Server-side validation protects against malformed or tampered input
• Only authorised users can see or perform restricted actions
• No sensitive data exposed in UI, logs, or network responses

Cross-Browser Compatibility

• Works on Chrome, Safari, and Edge for core interactions
• No critical layout or behavioural issues across browsers

Deployment Readiness

• No console errors, debug logs, test data, or commented-out code visible in UI
• Environment variables and configuration handled where required
• Feature flags or toggles correct and documented (if used)

Out-of-Scope for QA

QA does not check:

• System or domain architecture decisions
• Code style, naming conventions, or implementation elegance
• Long-term technical debt
• Whether the feature solves the right business problem
• High-level UX or product strategy

These are owned by development, tech direction, and product/client stakeholders.

Definition of Success

A feature passes QA when:

A real user can complete the intended task without confusion, errors, or surprises.

When this statement is true, the work is deployment-ready.