agentleFS
jhonatan-oliveiradevjhonatan-oliveiradev/agent-skills/skills/designing-test-strategies/SKILL.md

designing-test-strategies

Skill1 starsChanged 3 months agoMITView on GitHub

Use when a feature, service, or release needs a deliberate verification plan and the team is unsure which risks belong in unit, integration, end-to-end, or non-functional tests.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Add non-functional verification only where the requirement exists: accessibility, performance, load, reliability, security, compatibility, …

    line 18
  2. Distinctive:

    Before accepting the strategy, pick one critical behavior and one high-risk failure mode.

    line 43

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “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

Designing Test Strategies

Core principle

Design tests around the failures that matter, then choose the smallest test scope that can provide trustworthy evidence. Coverage percentage is a diagnostic signal, not a testing strategy.

Strategy workflow

  1. Define the product behaviors and contracts that must remain true. Include critical user journeys, data integrity, authorization, failure recovery, and externally visible interfaces.
  2. Rank risks by impact and likelihood. Give the most expensive or dangerous failures the strongest independent evidence.
  3. Choose the lowest useful layer for each risk:
    • small/unit tests for deterministic logic and edge cases;
    • integration tests for serialization, persistence, process boundaries, and external dependencies;
    • end-to-end tests for a small set of critical user journeys that require the assembled product.
  4. Add non-functional verification only where the requirement exists: accessibility, performance, load, reliability, security, compatibility, or recovery.
  5. Define the environment and test data needed for repeatability. Tests that depend on shared mutable state, execution order, or uncontrolled production services are weak evidence.
  6. Decide which gates block a change or release. A gate should have an owner, a deterministic command, and a clear failure interpretation.
  7. Review the portfolio for redundancy. Keep a higher-level test when it proves something a narrower test cannot.

Evidence matrix

For each important risk, record:

  • behavior or contract at risk;
  • failure impact;
  • test layer;
  • environment/dependencies;
  • expected evidence;
  • execution cadence;
  • owner when the gate fails.

Quality checks

A strategy is weak when it:

  • treats a coverage target as the primary objective;
  • duplicates the same assertion across every layer;
  • puts most confidence in broad UI tests;
  • omits integration boundaries because unit tests are fast;
  • has no explicit critical user journeys;
  • cannot explain what a failed gate means.

Verification

Before accepting the strategy, pick one critical behavior and one high-risk failure mode. Confirm that each has a test at the narrowest layer that can prove it, plus broader evidence only when assembly or user workflow adds unique confidence.

References

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.