agentleFS
charliehzmcharliehzm/medharness/.claude/skills/mocking-stubbing/SKILL.md

mocking-stubbing

Skill85 starsChanged 6 months agoApache-2.0View on GitHub

Use this skill at Step 9 of the v2 SOP to run the change's tests against the stage-isolated synthetic mock data produced at Step 5. Handles fixture loading, mock service stand-up (DB / external APIs / LLM endpoints), runs the test pyramid (unit + integration + e2e where applicable), and produces a test result report. On failure, hand off to systematic-debugging. Chinese trigger examples: "mock 测试", "Step 9", "跑测试用 mock", "联调 mock", "存根服务测试". Do NOT use to test against production data, do NOT use without verified mock fingerprints. Success = all tests green against stage mock, test result XML produced, no real service contacted.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 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.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    No real service contacted during Step 9: If a test "needs prod", the test is wrong.

    line 41
  2. Distinctive:

    Run test pyramid: unit → integration → e2e.

    line 49
  3. Very specific:

    If green → emit TEST_REPORT.md + hand off to Step 10.

    line 51
  4. Very specific:

    If red → hand off to systematic-debugging.

    line 52

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

Mocking Stubbing

The "tests must pass against synthetic data" gate.

Mock layers

LayerWhat's mockedHow
DBAll persistencesqlite-in-memory or testcontainers + synthetic fixtures
External APIsHospital HIS / 3rd partyresponses library / wiremock
LLMModel callsdeterministic stub via mcp-model-router test mode
Timeclocksfreezegun / fake clock
StorageObject storelocalstack / minio

Discipline

  • No real service contacted during Step 9. If a test "needs prod", the test is wrong.
  • No real PHI in fixtures (enforced upstream by test-data-generation).
  • Deterministic — LLM stubs return canned responses; flaky tests are bugs.

Workflow

  1. Load fixtures from mock/阶段N-*/.
  2. Stand up mock services (script: scripts/test/up_mocks.sh).
  3. Run test pyramid: unit → integration → e2e.
  4. Collect results as JUnit XML.
  5. If green → emit TEST_REPORT.md + hand off to Step 10.
  6. If red → hand off to systematic-debugging.

Common failure modes

  1. "Just this once" real call — test reaches real LLM. Mitigation: hooks block production endpoints in test env.
  2. Flaky LLM stub — random response in stub. Mitigation: deterministic by seed.
  3. Fixture drift — fixtures stale vs schema. Mitigation: schema-driven generation.
  4. Mock leak — test uses real env var. Mitigation: explicit env clear before each 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.

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.