Test Plan Template: Free Example for Website and UAT Testing

Last updated: November 18, 2026

A test plan is the document that says what you will test, how, where, by whom, and what counts as done. For a website release it fits on one or two pages: scope, approach, environments, browsers and devices, entry and exit criteria, roles, schedule, risks, and sign-off. Copy the template below or download it as a PDF.

ISTQB defines a test plan as “documentation that describes test objectives, means and schedule for achieving test coordination.” This guide is for agency project leads, QA testers, and developers who test websites before launch. It gives you a template, a filled-in example for a marketing site, and a version for user acceptance testing (UAT).

What a Test Plan Is, and What It Is Not

The formal standard for test documentation is ISO/IEC/IEEE 29119-3, which replaced IEEE 829. Under IEEE 829, a test plan describes the scope, approach, resources, and schedule of testing, and names the items and features to test, the tasks, who owns each task, and the risks. You do not need the full standard for a website. You need the decisions it asks for, written down before testing starts.

DocumentAnswersExample
Test planWhat, how, where, who, when, and what counts as done“Test the 12 pages on four browsers, at three widths, in two rounds.”
Test strategyThe general approach a team uses on every project“We test accessibility to WCAG 2.2 AA on every release.”
Test caseThe exact steps and expected result for one check“Submit the contact form empty. Each required field shows an error.”
ChecklistA list of things to confirmA website QA checklist
Bug reportWhat went wrong in one placeA bug report with steps to reproduce

Test Plan Template

Fill in every section before testing starts. A blank section is a decision someone will make later, under deadline.

SectionWhat to write
1. Project and releaseThe project, the version or release being tested, and who owns the plan.
2. ObjectiveWhat this round of testing must show, in one or two sentences.
3. ScopeThe pages, flows, and features in scope, and a separate list of what is out of scope.
4. ApproachThe kinds of testing: functional, visual and design QA, responsive, accessibility, performance, cross-browser, content, and UAT.
5. Environments and test dataThe staging address, test accounts, and any data the tests need.
6. Browsers and devicesEach browser, version, and screen width you will test, so “we tested it” means the same thing to everyone.
7. Entry and exit criteriaWhat must be true before testing starts, and what must be true for testing to be done.
8. RolesWho leads testing, who tests, which developer fixes, and who approves for the client.
9. ScheduleDates for each test round, the fix window between rounds, client UAT, and sign-off.
10. RisksWhat could stop testing or delay launch, and what you will do about each.
11. Defect processWhere bugs are reported, the severity levels, and how fixes are checked.
12. Sign-offWho approves the release, and the date.

Get the test plan template as a two-page PDF with every section above, ready to fill in for your next release.

Test Plan Example: A 12-Page Marketing Website

Here is the template filled in for a typical agency launch. The values are an example to adapt, not a standard.

SectionExample
ObjectiveShow that the new site is ready to replace the current one on the launch date.
In scopeAll 12 pages, the contact and newsletter forms, the booking flow, and the cookie banner.
Out of scopeThe client’s CRM, which receives form leads but is tested by the client’s own team.
ApproachFunctional, visual against the approved design, responsive, accessibility, performance, cross-browser, and client UAT.
EnvironmentStaging site behind a password; two test accounts; a test email inbox for form submissions.
Browsers and devicesLatest Chrome, Safari, Firefox, and Edge; widths of 360, 390, 768, and 1440 pixels.
Accessibility targetWCAG 2.2 level AA.
Performance targetThe “good” Core Web Vitals thresholds: LCP of 2.5 seconds or less, INP of 200 milliseconds or less, CLS of 0.1 or less.
Entry criteriaAll pages built on staging, final copy and images in place, forms connected.
Exit criteriaNo open blocker or major bugs, every in-scope flow passes, and the client approver has signed off UAT.
ScheduleRound 1, then two days of fixes, round 2, then three days of client UAT, then sign-off.
RisksLate copy from the client delays round 1; the booking provider’s test mode differs from live.

UAT Test Plan Template

A user acceptance testing plan has the same bones, but different people and a different question. The testers are the client and their users, not your QA team, and the question is whether the site does what the business needs. Write scenarios instead of step-by-step test cases, and tie each one to an acceptance criterion.

SectionWhat changes for UAT
TestersThe client’s staff or real users, with the time each person can give.
ScenariosTasks in the user’s words, such as “Book a consultation for next Tuesday.”
Acceptance criteriaWhat each scenario must achieve to pass. See UAT acceptance criteria.
How to report issuesOne simple way for non-technical testers to show what went wrong and where.
CommunicationThe invitation, instructions, reminder, and sign-off request. See our UAT email templates.
Sign-offWho signs for the client, and what they are agreeing to.

For the full process, see our guide to user acceptance testing, and SIT vs UAT for where each kind of testing fits.

How to Write a Test Plan in 6 Steps

  1. Start from the scope. List the pages and flows the release changes, then write down what you will not test and why.
  2. Choose the kinds of testing. Most website releases need functional, visual, responsive, accessibility, and cross-browser testing. Add performance and UAT for a launch.
  3. Name the browsers, devices, and widths. A device list turns “tested on mobile” into something two people mean the same way.
  4. Write exit criteria you can check. “No open blocker or major bugs” can be checked. “Works well” cannot.
  5. Plan at least two rounds. Leave time to fix what the first round finds and to test the fixes.
  6. Agree it with the client. Send the plan to the client approver before testing starts, so the exit criteria are shared.

Common Test Plan Mistakes

Where a Tool Helps

A test plan decides what to test. The testing itself produces bugs that need to reach a developer with enough detail to fix them. In OverlayQA, testers and clients pin a comment to the element that is wrong, and it becomes an issue with a screenshot, the page address, browser, and screen size. Accessibility Audit, Auto Review, and Visual Comparison check pages for problems nobody reported, and issues sync both ways with Jira, Linear, and other trackers.

Frequently Asked Questions

What should a test plan include?

Scope and out of scope, the testing approach, environments and test data, browsers and devices, entry and exit criteria, roles, schedule, risks, the defect process, and sign-off.

What is the difference between a test plan and a test strategy?

A test strategy is the general approach a team uses across projects. A test plan applies it to one project or release, with its own scope, dates, and people. In ISO/IEC/IEEE 29119-3, the test plan includes the test strategy for that project.

How long should a test plan be?

For a website release, one or two pages is usually enough. Length matters less than whether every section has an answer before testing starts.

Who writes the test plan?

Usually the test lead or the project lead. The client approver should agree the exit criteria, because they decide when the site is ready.

What are entry and exit criteria?

Entry criteria say what must be true before testing starts, such as final content on staging. Exit criteria say what must be true for testing to be done, such as no open blocker or major bugs.

Is a test plan the same as test cases?

No. The plan decides what to test and when. Test cases give the exact steps and expected result for each check.

What is a UAT test plan?

A test plan for user acceptance testing, where the client or real users check that the site does what the business needs. It lists testers, scenarios, acceptance criteria, how to report issues, and who signs off.

Turn every bug found in testing into a tracked issue. With OverlayQA, testers and clients pin comments to the page, and each one arrives with the screenshot, browser, and screen size attached.