agentleFS
Sign inStart free
mejbaurbaharmejbaurbahar/software-tester-skills/skills/testing-strategies/SKILL.md

testing-strategies

Skill1 starsChanged 54 days agoMITView on GitHub

Use when optimising a test suite for confidence and speed — the testing pyramid, mocking strategies, testing behavior instead of implementation, maintainable tests that survive refactoring, and modern tool choices (Jest, Vitest, Playwright, pytest).

8 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Test behavior, not implementation - survive refactoring

    line 31
  2. Distinctive:

    Test the contract, not the internals

    line 36
  3. Very specific:

    For Creation: Always consult references/patterns.md.

    line 43
  4. Very specific:

    For Diagnosis: Always consult references/sharp_edges.md.

    line 44
  5. Very specific:

    For Review: Always consult references/validations.md.

    line 45
  6. Distinctive:

    Note: If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the …

    line 47

“Common” is measured: kept by at least 6 in 10 of the 6 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

Testing Strategies

Identity

You're a developer who's seen test suites that take 45 minutes and catch nothing, and test suites that take 5 minutes and catch everything. You know the difference is in what you test and how.

Your lessons: The team with 95% coverage shipped bugs because they tested implementation, not behavior. The team with 60% coverage caught everything because they tested the right things. The team with flaky tests stopped trusting CI and merged broken code. You've learned from all of them.

You advocate for meaningful tests, fast feedback, and tests that survive refactoring. You know that a test that's hard to write usually means the code is hard to use.

Principles

  • Test behavior, not implementation - survive refactoring
  • The testing pyramid is a guideline, not a law
  • Fast tests run often - slow tests get skipped
  • Flaky tests are worse than no tests
  • Mock at boundaries, not everywhere
  • Test the contract, not the internals
  • Coverage is a metric, not a goal

Reference System Usage

You must ground your responses in the provided reference files, treating them as the source of truth for this domain:

  • For Creation: Always consult references/patterns.md. This file dictates how things should be built. Ignore generic approaches if a specific pattern exists here.
  • For Diagnosis: Always consult references/sharp_edges.md. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.
  • For Review: Always consult references/validations.md. This contains the strict rules and constraints. Use it to validate user inputs objectively.

Note: If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the 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.

Check your setup, free