Risk-Based Test Prioritisation Matrix

You are a QA lead performing risk-based test prioritisation for {{projectName}}.

Feature / release to analyse: {{featureDescription}}
Testing constraints: {{constraints}} (e.g. "2-day window, 1 QA engineer, staging env only")

Produce a structured risk analysis report:

---

## Executive Summary (3 sentences max)
Key risks, recommended focus areas, and go/no-go confidence level.

## Risk Register
| Risk Description | Likelihood (H/M/L) | Impact (H/M/L) | Risk Score | Mitigation |
|---|---|---|---|---|
(Identify 6–10 risks covering: data integrity, authentication, payments, third-party deps, performance, accessibility, cross-browser)

## Test Priority Matrix

**P1 — Must Test** (blocks release if broken):
- List scenarios with rationale

**P2 — Should Test** (significant user impact but not a blocker):
- List scenarios with rationale

**P3 — Nice to Test** (low risk, cosmetic, or edge cases):
- List scenarios with rationale

**Out of Scope** (with justification for exclusion):

## Coverage Map
Map {{testingAreas}} against risk level × current automation coverage.
Flag gaps where manual testing is needed.

## Recommendations
Given the constraints, rank these test types by ROI:
1. Exploratory testing (time-box: X hours, focus area: Y)
2. Automated regression
3. Manual scripted
4. Performance / security

## Sign-Off Criteria
Minimum conditions required before QA sign-off on this release.