# Test Plan: [Feature / Release name]

<!--
Qualflare test plan template — https://qualflare.com/blog/test-plan-template/
Delete any section that does not earn its place. A test plan nobody reads is
worse than no test plan; nine short sections beat a thirty-page document.
-->

**Release:** [version / date]
**Test lead:** [name]
**Status:** Draft | In review | Approved

## 1. Objectives

What this testing effort is trying to achieve, in one or two sentences.

> Example: Verify the redesigned checkout works across supported browsers and
> payment methods before release.

## 2. Scope

- **In scope:** [features, flows, platforms being tested]
- **Out of scope:** [what you are explicitly NOT testing — and why]

> Example — in: Cart, checkout, payment, order confirmation on Chrome, Safari,
> Firefox. Out: Admin tooling, email receipts (covered separately).

## 3. Approach

Types of testing (unit, integration, end-to-end, performance, manual
exploratory) and how they will be run (CI, framework, automation vs manual).

## 4. Environment & Test Data

Where tests run (environments, browsers/devices) and what data they use.

## 5. Entry Criteria

What must be true before testing starts.

- [ ] Build deployed to the test environment
- [ ] Environment stable
- [ ] Test data loaded

## 6. Exit Criteria

What "done" means. Be specific enough that two people would agree on whether
it has been met.

- [ ] Critical-path tests pass
- [ ] No open blockers
- [ ] Flake rate below [threshold]
- [ ] Coverage target met

## 7. Risks & Mitigations

| Risk | Likelihood | Impact | Mitigation |
|---|---|---|---|
| [e.g. payment sandbox unavailable] | Med | High | [stub provider, book slot early] |
| | | | |

## 8. Roles

| Role | Owner |
|---|---|
| Test lead | |
| Automation | |
| Manual / exploratory | |
| Sign-off | |

## 9. Schedule (optional)

| Milestone | Date |
|---|---|
| Test start | |
| Feature freeze | |
| Sign-off | |