# Test plan

- Product:
- Release / version:
- Author:
- Date:
- Status: Draft | Review | Approved

## 1. Purpose

What this plan is for, in one paragraph. Name the release or change, not the company mission.

## 2. Scope

### In scope

- Features / journeys:
- Platforms / browsers / devices:
- Environments:

### Out of scope

- Explicit exclusions (and why):

## 3. Test items

| ID | Item | Notes |
| --- | --- | --- |
| TI-01 | | |

## 4. Approach

- Manual:
- Automated:
- Exploratory:
- Non-functional (performance, accessibility, security) — in or out:

## 5. Entry and exit criteria

- Entry:
- Exit:
- Suspension / resumption:

## 6. Environments and test data

- Environments:
- Data needs:
- Access / accounts:

## 7. Schedule and roles

| Activity | Owner | Window |
| --- | --- | --- |
| | | |

## 8. Risks and contingencies

| Risk | Impact | Mitigation |
| --- | --- | --- |
| | | |

## 9. Deliverables

- Traceability matrix:
- Test cases:
- Execution log:
- Defect reports:
- Summary:

## 10. Approvals

| Role | Name | Date |
| --- | --- | --- |
| | | |