integration-e2e-testing
Integration and E2E test design principles, ROI calculation, test skeleton specification, and review criteria. Use when designing integration tests, E2E tests, or reviewing test quality.
npx skills add shinpr/claude-code-workflows --skill integration-e2e-testing --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Integration and E2E Testing Principles ## References **E2E test design**: See [references/e2e-design.md](references/e2e-design.md) for UI Spec-driven E2E test candidate selection and browser test architecture. The reference uses Playwright as the default browser harness; substitute the project's standard when different. ## Test Type Definition and Standard Budgets | Test Type | Purpose | Scope | External Deps | Standard Budget per Input Design Doc | Implementation Timing | |-----------|---------|-------|---------------|-------------------|----------------------| | Integration | Verify component interactions in-process | Partial system integration (in-process modules; for UI components, the framework's in-process renderer e.g., RTL+MSW for React/TS) | Mocked or in-process | MAX 3 | Created alongside implementation | | fixture-e2e | Verify UI behavior in a browser with deterministic fixtures | Full UI flow with mocked backend / fixture-driven state | Mocked / fixture only — no live services | MAX 3 | Created alongside the UI feature | | service-integration-e2e | Verify critical user journeys against a running local stack | Full system across services | Live local services or stubs
- References
- Test Type Definition and Standard Budgets
- Behavior-First Principle
- Include (High ROI)
- Redirect to Other Test Types
- ROI Calculation
- ROI Thresholds by Lane
- ROI Calculation Examples
- Multi-Step User Journey Definition
- User-Facing vs Service-Internal Journeys
- Test Skeleton Specification
- Required Comment Patterns
- Verification Items (Optional)
- EARS Format Mapping
What does the integration-e2e-testing skill do?
Integration and E2E test design principles, ROI calculation, test skeleton specification, and review criteria. Use when designing integration tests, E2E tests, or reviewing test quality.
How do I install it?
Run `npx skills add shinpr/claude-code-workflows --skill integration-e2e-testing --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From shinpr/claude-code-workflows, a repository with 664 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.