integration-e2e-testing
/integration-e2e-testing
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.
- Author
- shinpr ↗
- Repository
- claude-code-workflows ↗
- Licence
- MIT
- Last repository change
- 23.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 23.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
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.
Original author description
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.
How it works
- Test Lanes
- Test Skeleton Specification
- Test File Naming Convention
- Route Parity for Shared Mutations
SKILL.md preview
--- name: integration-e2e-testing description: 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. --- # 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] ``` Use the project's comment syntax to wrap these annotations (e.g., `//` for C-family, `#` for Python/Ruby/Shell). ### Verification Items (Optional) When verification points need explicit enumeration: ``` Verification items: - [Item 1] - [Item 2] ``` ## Test File Naming Convention - Integration tests: `*.int.test.*` or `*.integration.test.*` - fixture-e2e tests: `*.fixture.e2e.test.*` (or organize under `tests/e2e/fixture/`) - service-integration-e2e tests: `*.service.e2e.test.*` (or organize under `tests/e2e/service/`) The test runner or framework in the project determines the appropriate file extension. Repos that already use a single `*.e2e.test.*` convention may keep it as long as each file declares `@lane:` in its header — the lane annotation is the source of truth for routing. ## Route Parity for Shared Mutations When multiple routes reach the same mutation, compare validation, classification, resource bounds, and read/parse/mutation/reporting order. A difference becomes a proof obligation when it can violate an authoritative contract or expose a material bypass in the changed boundary. Reuse existing proof or add the smallest test that detects that failure.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · shinpr/claude-code-workflows | 100 | MIT |
| shinpr/ai-coding-project-boilerplate | 100 | MIT |
| shinpr/ai-coding-project-boilerplate | 96 | MIT |
| shinpr/agentic-code | 85 | MIT |
Identical content appears in 9 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 2f2d056deb6a (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100testing
Apply comprehensive testing best practices including unit, integration, and e2e tests. Use when writing tests, reviewing test coverage, designing testable code, or setting up test infrastructure. - 100integration-testing
Integration testing patterns for database state, API contracts, service boundaries, and component wiring. Use when testing how multiple parts of a system work together without mocks. - 100integration-test-setup
Configure integration test setup operations. Auto-activating skill for Test Automation. Triggers on: integration test setup, integration test setup Part of the Test Automation skill category. Use when writing or running tests. Trigger with phrases like "integration test setup",… - 100testing-best-practices
Unit testing, integration testing, and test-driven development principles. Use when writing tests, reviewing test code, improving test coverage, or setting up testing strategy. Triggers on "write tests", "review tests", "testing best practices", or "TDD". - 90quality-integration-testing
Use when the user asks about integration testing, component testing, API testing, database testing, test containers, wiremock, contract testing, or service-level testing. Do NOT use for: unit testing (quality-unit-testing), E2E testing (quality-e2e-testing), or contract testing… - 100agent-integration-testing
Use when the user requests integration testing, feature validation, or test plan execution