# Test plan: [Release or feature name]

> Lean, one-page test plan template from TestPlum (testplum.com/templates/test-plan/).
> Replace the example text in each section. Delete any section that does not apply, but keep the
> entry and exit criteria: they are what make the plan checkable.

| | |
|---|---|
| **Release** | Checkout 2.4 |
| **Build or version** | 2.4.0-rc1 |
| **Plan owner** | [Name], QA lead |
| **Last updated** | [YYYY-MM-DD] |
| **Status** | Draft / Agreed / Done |

## 1. Scope

What this release changes and therefore what we test:

- Pay with a saved card (new).
- Declined and expired card handling (changed).
- Discount codes at checkout (changed).
- Regression: guest checkout, order history, order confirmation email.

## 2. Out of scope

What we will not test in this plan, and why:

- Gift cards: not part of this release; covered by the existing regression run.
- Load testing: done separately by the platform team before the sale on [date].
- Older browsers outside the support list.

## 3. Risks

| Risk | Likelihood (L/M/H) | Impact (L/M/H) | How we test for it |
|---|---|---|---|
| Customers are charged but no order is created | L | H | Critical tests CHK-1 and CHK-2 on every build, plus a manual check of the payment provider dashboard |
| A declined card empties the cart | M | M | CHK-2, CHK-8 |
| Discounts are applied twice | M | M | CHK-3, CHK-6 and an exploratory session of 60 minutes |
| Saved cards are shown to the wrong customer | L | H | Manual test with two accounts on two devices |

Test the high-impact, high-likelihood rows first and most deeply.

## 4. Approach

- **Automated:** the Playwright checkout suite runs on every pull request and on each release candidate.
- **Manual:** new and changed flows, payment provider screens and anything the automated suite cannot see.
- **Exploratory:** one timeboxed session per changed area, with notes kept as evidence.
- **Regression:** the existing checkout regression run, critical and high priority first.

## 5. Environments and data

| Environment | Used for | Notes |
|---|---|---|
| Staging | Manual, exploratory and automated runs | Payment provider in test mode |
| Production | Smoke test after release only | One real order, refunded the same day |

Test data: two customer accounts with saved cards, one guest email, discount codes SAVE10 (active) and OLD10 (expired).

## 6. Entry criteria

Testing starts when every line is true:

- [ ] The release candidate is deployed to staging.
- [ ] The automated checkout suite passes on that build.
- [ ] Test data above exists on staging.
- [ ] Every requirement in scope has at least one linked test.

## 7. Exit criteria

We recommend shipping when every line is true. Example thresholds, agreed before testing starts:

- [ ] 100% of tests in scope have a final result.
- [ ] Pass rate of executed tests is 95% or higher.
- [ ] 0 critical-priority tests failing or blocked.
- [ ] 0 open bugs of critical priority or blocker severity.
- [ ] At least 80% of requirements in scope are passing, and none is failing.

## 8. Schedule

| Milestone | Date |
|---|---|
| Release candidate on staging | [date] |
| Testing complete | [date] |
| Go/no-go meeting | [date] |
| Release | [date] |

## 9. Roles

| Role | Person | Responsible for |
|---|---|---|
| QA lead | [Name] | This plan, the regression run, the exit criteria report |
| Tester | [Name] | Manual and exploratory testing |
| Engineering lead | [Name] | Fixes, automated suite, rollback plan |
| Product owner | [Name] | Scope, accepting known issues, the final decision |

## 10. Evidence and sign-off

Evidence lives here: [link to the test runs, the bug list and the traceability matrix].

| Role | Name | Decision (Go / No-go) | Date |
|---|---|---|---|
| QA lead | | | |
| Product owner | | | |
