agentleFS
Sign inStart free
CaduS0uzaCaduS0uza/qa-supreme/skills/test-strategy/SKILL.md

test-strategy

Skill1 starsChanged 2 months agoMITView on GitHub

Turn a risk register into a concrete, decision-complete test plan — which level tests what, what is deliberately NOT tested, and what the exit criteria are. Use after risk-map, when a team asks for a QA strategy, or when a suite grew without a rationale.

39 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use data-pipelines, exploratory-testing and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • YepAPISkill

    data-pipelines

    ETL patterns, cron scheduling, queue-based processing, and batch jobs with Inngest/BullMQ.

    Also in 3 projects that use this

  • testified-ossSkill

    exploratory-testing

    Guide exploratory testing sessions including charter creation, session-based testing, heuristics application, and finding documentation. Use when planning exploratory testing, conducting test sessions, or documenting discoveries.

    Also in 3 projects that use this

  • ffsshhttiikkSkill

    unit-testing

    Unit testing best practices and patterns

    Also in 4 projects that use this

  • AnthropicSkill

    incident-response

    Run an incident response workflow — triage, communicate, and write postmortem. Trigger with "we have an incident", "production is down", an alert that needs severity assessment, a status update mid-incident, or when writing a blameless postmortem after resolution.

    Also in 7 projects that use this

  • OpenAISkill

    observability

    Vercel Observability expert guidance — Drains (logs, traces, speed insights, web analytics), Web Analytics, Speed Insights, runtime logs, custom events, OpenTelemetry integration, and monitoring dashboards. Use when instrumenting, debugging, or optimizing application performance and user experience on Vercel.

    Also in 6 projects that use this

  • Microsoft AzureSkill

    release-readiness

    Complete ODIN release documentation and validation checks before declaring user-visible work complete, preparing a release, or opening the Release-to-main pull request.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 2 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 34 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Default split for a web product: 70/20/10 by count, but 100% of P0 risks get at least one test at the level that can catch them — that rule …

    line 22
  2. Distinctive:

    every P0 has a passing test that has been mutation-proven

    line 40
  3. Very specific:

    no test in the suite is on the false-positive-hunter P0 list

    line 42
  4. Very specific:

    Write to .qa-supreme/test-strategy.md and print the summary table only.

    line 43
  5. Distinctive:

    Never propose a level whose infrastructure does not exist without also proposing the setup task.

    line 55
  6. Very specific:

    Never write "increase coverage to N%" as an exit criterion.

    line 56

“Common” is measured: kept by at least 6 in 10 of the 34 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Test Strategy

A strategy is a set of decisions, not a wish list. Every line answers "what do we do Monday" and every omission is deliberate and written down.

Level assignment

Assign each P0/P1 risk to the cheapest level that can actually catch it:

LevelCatchesCostUse when
Unitlogic, branches, math, parsing~msthe rule lives in one function
Integration / APIcontracts, persistence, authz, wiring~100msthe risk crosses a boundary
E2Ethe user's actual path through real UI~secondsthe risk only exists end to end
Non-functionala11y, perf, security regressionsvariesthe risk is a property, not a path

Default split for a web product: 70/20/10 by count, but 100% of P0 risks get at least one test at the level that can catch them — that rule outranks the ratio.

The NOT-testing list (mandatory section)

Name at least three things you will not test and why. Examples: third-party SDK internals, generated code, styling that no assertion can meaningfully pin, admin tooling used by two people. A strategy without exclusions is a fantasy.

Procedure

  1. Load .qa-supreme/risk-register.md (run risk-map first if absent).
  2. For each P0/P1: assign level, name the specific assertion that proves it, name the owner skill (unit-test-authoring, api-contract-testing, e2e-authoring, security-regression...).
  3. Define test data: factories over fixtures, one seeded tenant per test, no shared mutable state, deterministic clock and IDs.
  4. Define environments: where each level runs, what is mocked (see ci-wiring).
  5. Define exit criteria as booleans, not adjectives:
    • every P0 has a passing test that has been mutation-proven
    • flake rate on the E2E suite < 1% over the last 20 CI runs
    • no test in the suite is on the false-positive-hunter P0 list
  6. Write to .qa-supreme/test-strategy.md and print the summary table only.

Output

| Risk | Tier | Level | Assertion that proves it | Skill | Status |
|---|---|---|---|---|---|
| double charge on retry | P0 | integration | second webhook with same id -> 1 charge row | api-contract-testing | todo |

Rules

  • Never propose a level whose infrastructure does not exist without also proposing the setup task.
  • Never write "increase coverage to N%" as an exit criterion. Coverage is a symptom (see coverage-ratchet).
  • Strategy fits on one screen. Longer means undecided.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free