Defines integration/E2E skeleton annotations, lane and file contracts, and route-parity review criteria. Use when generating or consuming test skeletons or reviewing shared mutation routes.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Integration and E2E Skeleton Contracts
## Test Lanes
| Lane | Observable boundary | Dependencies |
|------|---------------------|--------------|
| `integration` | Interactions within a process, including framework-rendered UI and module/API handlers | Real participating components; mock only outside the claimed boundary |
| `fixture-e2e` | Actual UI behavior in a real browser with deterministic fixtures | Fixtures may replace dependencies outside the claimed boundary |
| `service-integration-e2e` | Outcome depends on actual cross-service interaction or persistence | Required local services and stores are real; stubs only outside that proof boundary |
## Test Skeleton Specification
### Required Comment Patterns
Each test MUST include the following annotations:
```
AC: [Original acceptance criteria text]
Behavior: [Trigger] → [Process] → [Observable Result]
@lane: integration | fixture-e2e | service-integration-e2e
@dependency: none | [component names] | full-system
Selection evidence: [required claim, uncovered failure, and why cheaper existing proof is insufficient]
```
…
The line at the top of this page pins the label git:20261019.4d66b0c, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_33zmuzmu5euqshwt
GET https://markdownregistry.com/api/v1/resolve?ref=shinpr/claude-code-workflows/integration-e2e-testing
GET https://markdownregistry.com/api/v1/blob/12648db76c8340c9242943dee65f0d8aad4e7071b0133283a7251bfc51da16ba
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
shinpr/claude-code-workflows · dev-skills/skills/coding-principles/SKILL.md · Language-agnostic coding principles for maintainability, readability, and quality. Use when implementing features…
shinpr/claude-code-workflows · dev-skills/skills/documentation-criteria/SKILL.md · Determines which of PRD, ADR, UI Spec, Design Doc, and Work Plan a change requires, and where each is stored. Use when…
shinpr/claude-code-workflows · dev-skills/skills/external-resource-context/SKILL.md · Records where resources outside the repository live (design source, design system, API schema, IaC source, secret…
shinpr/claude-code-workflows · dev-skills/skills/integration-e2e-testing/SKILL.md · Defines integration/E2E skeleton annotations, lane and file contracts, and route-parity review criteria. Use when…
shinpr/claude-code-workflows · dev-skills/skills/requirement-convergence/SKILL.md · Separates the outcome a change must produce from the requirements proposed to reach it, records what the user excluded…
shinpr/claude-code-workflows · dev-skills/skills/testing-principles/SKILL.md · Language-agnostic testing principles for choosing which tests a change needs, test quality, and proof ownership, with…
shinpr/claude-code-workflows · dev-skills/skills/typescript-rules/SKILL.md · React/TypeScript frontend development rules including type safety, component design, state management, and error…
shinpr/claude-code-workflows · dev-workflows-frontend/skills/coding-principles/SKILL.md · Language-agnostic coding principles for maintainability, readability, and quality. Use when implementing features…
shinpr/claude-code-workflows · dev-workflows/skills/integration-e2e-testing/SKILL.md · Defines integration/E2E skeleton annotations, lane and file contracts, and route-parity review criteria. Use when…
shinpr/claude-code-workflows · dev-workflows-frontend/skills/integration-e2e-testing/SKILL.md · Defines integration/E2E skeleton annotations, lane and file contracts, and route-parity review criteria. Use when…
shinpr/claude-code-workflows · dev-skills/skills/integration-e2e-testing/SKILL.md · Defines integration/E2E skeleton annotations, lane and file contracts, and route-parity review criteria. Use when…
shinpr/claude-code-workflows · dev-workflows-fullstack/skills/integration-e2e-testing/SKILL.md · Defines integration/E2E skeleton annotations, lane and file contracts, and route-parity review criteria. Use when…
shinpr/ai-coding-project-boilerplate · .claude/skills-en/integration-e2e-testing/SKILL.md · Selects and designs the smallest integration/E2E test set that proves accepted behavior at an observable boundary. Use…
shinpr/agentic-code · .agents/skills/integration-e2e-testing/SKILL.md · Applies integration and E2E implementation, mock-boundary, and review rules. Use when: writing integration or E2E tests…