Risk-Based Testing

Translate supplied quality risks, failure modes, and delivery constraints into evidence-backed test priority, level/method, depth, and scope tradeoffs. Produce RBT-## decisions. This is not a full test strategy; it does not replace risk analysis or regression selection, and it does not execute tests.

When to Use

• Use it when business criticality, change surface, past defects, or failure modes must determine test order and depth.
• Use it when time, environment, or capacity is constrained and the tradeoffs between focus, sampling, and deferral must be explicit.
• Use it when risk evidence is incomplete but a bounded priority view with assumptions and triggers is useful.

Do not use it only to identify quality risks, write a complete test strategy, select an existing executable set, or announce release readiness.

Output Format Options

• Use Markdown by default; when a table, CSV, or JSON is requested, preserve the same evidence, status, impact, owner, and validation fields.
• Do not present a structured format or static inventory as execution, pass, approval, or release evidence.

How to Use