agentleFS
Asno-devAsno-dev/apex/skills/test-harness/SKILL.md

test-harness

Skill1 starsChanged 5 months agoMITView on GitHub

Invoke when writing tests, adding test coverage, generating test suites. "write tests for", "add coverage", "test generation", "unit tests", "integration tests", "test this function". SDLC categories: Testing (25 benchmarks).

5 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

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

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 3

    Distinctive

    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:

    Test behavior, not implementation

    line 20
  2. Distinctive:

    Test names: "it should [behavior] when [condition]"

    line 22
  3. Distinctive:

    No mocking what you own (mock external services only)

    line 23

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

  1. RISK MAP — Identify 3 highest-risk code paths. Risk = (failure probability) × (failure cost)
  2. TEST STRATEGY per path:
    • Unit: pure functions, utilities, transformations
    • Integration: DB operations, API calls, service interactions
    • E2E: critical user journeys only (login, checkout, core workflow)
  3. QUALITY RULES:
    • Test behavior, not implementation
    • One assertion per test (or one logical group)
    • Test names: "it should [behavior] when [condition]"
    • No mocking what you own (mock external services only)
    • Arrange-Act-Assert structure, always
  4. For each test: output failing case first, then passing case. Happy-path-only tests are worth 0.
  5. Output: Complete test files, runnable with: npm test

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.

Reviews can't be read right now.

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.