risk-based-testing SKILL.md skillA
risk-based-testing from qa-aman/claude-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add qa-aman/claude-skills/risk-based-testing@git:20260303.9d46210Pins git:20260303.9d46210 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- qa-aman/claude-skills
- Path
skills/by-role/qa/risk-based-testing/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260303.9d46210, committed Mar 3, 2026
- Size
- 5,542 bytes
- Repository stars
- 25
- License
- MIT
Allocate testing effort based on risk and failure likelihood using Google's SET/SWE/TE model. Use when user says "risk-based testing", "where should I focus testing", "test coverage strategy", "prioritize what to test", "high risk areas", or needs to decide how to distribute QA effort across a codebase - even if they don't explicitly say "risk-based".
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
## 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) ACC gives you a structured map of what exists to test. Without it, coverage is guesswork. ### Step 2: Score each capability for risk For every capability in your ACC map, assign two scores (1-3 scale): | Dimension | 1 | 2 | 3 | |-----------|---|---|---| …
Read the whole file at its exact version.
How to install
mdr add qa-aman/claude-skills/risk-based-testing@sha256:b3a7e61f93e7294dThe line at the top of this page pins the label git:20260303.9d46210, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_ffymeatkc6oocnty)
7 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Mar 3, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5542 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
qa-aman/claude-skills · 25 stars · license MIT · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ffymeatkc6oocnty GET https://markdownregistry.com/api/v1/resolve?ref=qa-aman/claude-skills/risk-based-testing GET https://markdownregistry.com/api/v1/blob/b3a7e61f93e7294d2c1608e893678ef1adf28319f5362e329a9e8281ad09fa44
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from qa-aman/claude-skills
Every file in qa-aman/claude-skills