risk-based-testing
Installation
SKILL.md
Overview
Risk-based testing focuses effort where failures cause the most harm. Based on "How Google Tests Software" by James Whittaker, Jason Arbon, and Jeff Carollo, this approach maps product risk to test investment - instead of testing everything equally, you test the highest-risk components most deeply.
The core insight: not all code carries equal risk. A bug in a payment flow is not the same as a bug in a tooltip. Risk-based testing makes that distinction explicit, then allocates testing hours accordingly.
Workflow
Step 1: Map product into Attribute Component Capability (ACC) format
Break the product into three levels:
- Attribute: Quality characteristics users care about (reliable, secure, fast, correct)
- Component: Major subsystems or modules (auth, payments, search, notifications)
- Capability: Specific behaviors each component must support (login with OAuth, process refund, filter by date)