QA Checklist

A process-level quality-assurance checklist for managing a software release.

Published June 27, 2026

Plan the QA cycle

Confirm the scope of the release and what is in and out of testing.
Review requirements, designs and acceptance criteria with the team.
Write a test plan covering test types, schedule and responsibilities.
Define entry criteria for when testing can begin.
Define exit and sign-off criteria for when testing is complete.
Identify risks and prioritize areas that need the most coverage.
Estimate effort and confirm resourcing for the cycle.

Prepare environments and data

Set up a stable test environment that mirrors production closely.
Deploy the correct build and confirm the version under test.
Prepare realistic test data covering common and edge scenarios.
Configure required integrations, accounts and feature flags.
Verify access for all testers and the tools they need.
Confirm the test management and bug tracking tools are ready.

Author test cases

Write clear test cases mapped to requirements and acceptance criteria.
Cover positive, negative and boundary scenarios for each feature.
Mark which cases are candidates for automation.
Prepare a regression suite for previously released functionality.
Peer review test cases for coverage and clarity.
Link test cases to the stories or tickets they verify.

Execute tests

Run smoke tests first to confirm the build is testable.
Execute planned test cases and record actual results.
Run the regression suite to catch unintended side effects.
Log defects with clear steps, expected and actual results.
Capture evidence such as screenshots, logs and recordings.
Track test execution progress and coverage against the plan.

Triage and manage defects

Triage each defect by severity, priority and impact.
Assign defects to owners with clear reproduction steps.
Agree which defects block the release and which can be deferred.
Verify fixes and confirm they don't introduce regressions.
Re-test resolved issues and close them when verified.
Maintain a current list of open issues and their status.

Sign-off and reporting

Confirm exit criteria are met, including critical tests passing.
Verify there are no open blocker or critical defects.
Summarize results in a test report with coverage and known issues.
Document any agreed risks or workarounds for remaining issues.
Obtain formal sign-off from QA and stakeholders.
Capture lessons learned to improve the next QA cycle.

0 / 37 done

A QA checklist is a process-level list that guides a quality-assurance team through testing a software release from planning to sign-off. It covers building a test plan, preparing environments and data, executing tests, triaging bugs and deciding when the release is ready to ship — keeping the QA process organized and repeatable.

Quality assurance is more than running tests. It's a workflow: agreeing on what to test, setting up the right environments, tracking results, prioritizing defects and making a clear go or no-go decision. Skipping any of these leads to missed bugs or releases that stall without a clear owner.

This checklist organizes the QA process into stages — planning, environment setup, execution, defect management and sign-off — so testers, developers and product owners share one view of release readiness.

Use the printable version in test cycles, or share the PDF with your QA team and stakeholders so everyone knows the entry and exit criteria. Pair it with a separate software testing checklist for the specific test types to run.

FAQ

What is the difference between QA and testing?

Testing is the act of running checks to find defects. QA is the broader process that ensures quality throughout a release — planning, environments, execution, triage and sign-off. This checklist covers the QA process; a software testing checklist covers the specific tests to run.

What goes into a test plan?

A test plan defines scope, what's in and out, the test types you'll run, environments and data needed, roles, schedule, and entry and exit criteria. It gives the whole team a shared definition of what 'tested' means for the release.

How should we prioritize bugs during QA?

Triage each defect by severity and impact, then agree which must be fixed before release and which can wait. Clear priorities prevent low-impact issues from blocking a release while ensuring critical bugs are never shipped.

What are sign-off criteria?

Sign-off criteria are the conditions that must be met to approve a release, such as all critical tests passing, no open blockers, and stakeholders' approval. Defining them up front avoids subjective last-minute decisions.

Is this QA checklist available as a printable PDF?

Yes. You can print it or download the PDF to run your QA cycles consistently and share it with testers, developers and product owners for each release.