Test Plan: [Feature or release]

Test owner: [Name]
Build or version: [Identifier]
Test window: [Dates]
Requirements: [PRD and acceptance criteria links]

Objective and scope

[Describe the behaviors and risks this test effort will validate.]

• In scope: [Features, integrations, platforms, and migrations.]
• Out of scope: [Excluded areas and reason.]
• Highest risks: [Critical user journeys and likely failure points.]

Environment and test data

Environment	Build	Configuration	Owner
[Staging]	[Version]	[Flags, dependencies, browsers]	[Name]

Data: [Fixtures, roles, tenant boundaries, edge cases, setup and cleanup. Use synthetic or approved sanitized data.]

Test strategy

Level or area	Coverage	Method	Owner
Unit	[Rules and transformations]	[Automated]	[Name]
Integration	[Storage and service contracts]	[Automated]	[Name]
End-to-end	[Critical user journeys]	[Automated or manual]	[Name]
Accessibility	[Keyboard, focus, screen readers]	[Manual and automated]	[Name]
Security	[Authorization and input boundaries]	[Review and targeted tests]	[Name]
Performance	[Latency and representative load]	[Measured workload]	[Name]

Requirement coverage

Requirement	Test cases	Coverage gap
[FR-01]	[TC-01, TC-02]	[None or known limitation]

Test cases

ID	Scenario and preconditions	Steps	Expected result	Actual result	Status
TC-01	Member can save a draft	Edit, save, close, reopen	Saved content is unchanged	[Observation]	Not run
TC-02	Viewer cannot modify content	Open as a viewer and attempt a write	Write is rejected and content stays unchanged	[Observation]	Not run
TC-03	[Boundary or failure scenario]	[Reproducible steps]	[Observable outcome]	[Observation]	Not run

Entry criteria

• Requirements and acceptance criteria are reviewed.
• The target build and dependencies are available.
• Test accounts, data, and access are prepared.

Defect handling

Defect	Severity	Steps and evidence	Owner	Status	Retest result
[Issue link]	[Impact-based severity]	[Reproduction and artifacts]	[Name]	[Open]	[Pending]

Exit criteria and release recommendation

• Critical journeys pass on supported configurations.
• No unresolved release-blocking defects remain.
• Required regression and quality checks pass.
• Residual risks are documented and accepted by [owner].

Summary: [Passed / failed / blocked / not run counts.]

Recommendation: [Release / do not release / conditional release, with rationale.]

Approval: [Name, date, and evidence link.]