Test plan template

# Test plan

## Objective
[One or two sentences on what this release or feature is being tested for.]

## Scope, in and out
[What the plan covers, and just as importantly what it does not.]

## Test approach
[Manual, automated, exploratory - how the testing is actually done, and by whom.]

## Entry and exit criteria
[What has to be true before testing starts, and before it can stop.]

## Environments and test data
[Browsers, devices, builds, and the data the cases run against.]

## Schedule and responsibilities
[Who does what, and by when.]

## Risks and mitigations
[What could stop the plan working, and what you will do about it.]

## Deliverables and sign-off
[What the testing produces, and who signs it off.]

# Test plan

## Objective
Confirm the demo shop prices a basket correctly, discount codes included, before build 2026.08.14 ships.

## Scope, in and out
In: basket, discount codes, totals, payment step. Out: the admin area, receipt e-mails, anything behind a flag.

## Test approach
Scripted manual passes over the eleven checkout cases, an exploratory hour on the basket, smoke run on each deploy.

## Entry and exit criteria
Entry: build 2026.08.14 on staging with the seeded catalogue. Exit: no open blocker, every discount case passing twice.

## Environments and test data
Chrome 139 and Safari 18 on macOS 15.5 at 1440x900, staging build 2026.08.14, seeded with "Field Notebook" and SPRING10.

## Schedule and responsibilities
Two testers, 26 to 29 August. Priya takes the basket and totals, Sam takes payment and the Safari pass.

## Risks and mitigations
Discount rules changed late, so the totals cases run first and a failure there stops the release, not the plan.

## Deliverables and sign-off
This plan, the eleven case results, a bug report per failure, and sign-off from the release owner before deploy.