agentleFS
shinprshinpr/agentic-code/.agents/skills/integration-e2e-testing/SKILL.md

integration-e2e-testing

Skill51 starsChanged 9 days agoMITView on GitHub

Applies integration and E2E implementation, mock-boundary, and review rules. Use when: writing integration or E2E tests or reviewing their quality.

3 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

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

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 2

    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:

    Pass Criteria: Test passes if "observable result" is verified as return value or mock call argument

    line 18
  2. Distinctive:

    Do not use mocks (full system integration required)

    line 30

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

Integration and E2E Test Implementation and Review Rules

Implementation Rules

Behavior Verification

Step TypeVerification Target
TriggerReproduce in test setup (Arrange)
ProcessIntermediate state or function call
Observable ResultFinal output value (return value, error message, log output)

Pass Criteria: Test passes if "observable result" is verified as return value or mock call argument

Integration Test Mock Boundaries

Judgment CriteriaMockActual
Part of test target?No → Can mockYes → Actual required
External network communication?Yes → Mock requiredNo → Actual recommended

E2E Test Execution Conditions

  • Execute once every component the journey crosses is implemented
  • Do not use mocks (full system integration required)

Review Criteria

Skeleton and Implementation Consistency

CheckFailure Condition
Behavior VerificationNo assertion for "observable result"
Verification Item CoverageListed verification items not included in assertions
Mock BoundaryInternal components mocked in integration test

Implementation Quality

CheckFailure Condition
AAA StructureArrange/Act/Assert separation unclear
IndependenceState sharing between tests, execution order dependency
ReproducibilityDepends on date/random, results vary
ReadabilityTest name and verification content don't match

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.