integration-e2e-testing
GitHub定义集成与E2E测试骨架规范，包括测试车道划分、文件命名约定及路由一致性审查标准。用于生成或消费测试骨架，以及审查共享变更路径的测试覆盖情况。
触发场景
安装
npx skills add shinpr/claude-code-workflows --skill integration-e2e-testing -g -y
SKILL.md
Frontmatter
{
"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 undertests/e2e/fixture/) - service-integration-e2e tests:
*.service.e2e.test.*(or organize undertests/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.
版本历史
-
eba53e4
当前 2026-11-02 13:35
从测试原则预算转向具体的骨架注解、文件命名和路由一致性审查标准，简化工作流合同。
-
910f9dd
2026-10-18 21:08
整合测试指南至统一技能，移除重复的测试类型定义，优化测试所有权与ROI评估逻辑。
-
6d58447
2026-09-08 22:26
更新service-integration-e2e的实施时机描述；修复工作流验证与QA合同对齐问题。
-
416af89
2026-08-12 16:36
重构以对齐证据驱动模型自主性，修复外部资源上下文引用问题。明确技能所有权边界，规定在特定条件下才能发出低于标准的测试候选项，并将合并的检查清单拆分为独立可检查项。
- d439b50 2026-07-31 02:50
-
56ab6c1
2026-07-19 22:41
重构提示词执行指南，将‘Limits’统一为‘Standard Budgets’以明确预算概念，并优化相关描述以提升一致性。
- 66e3b29 2026-07-05 11:57
