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:37
从测试原则转向具体的骨架契约规范，引入基于注释的测试车道标记和路由一致性审查标准，移除冗余的选择规则。
-
910f9dd
2026-10-18 21:10
整合测试指南，统一为单一测试技能；移除测试优先执行要求；优化代码审查以检测重复测试；调整测试骨架生成逻辑。
-
6d58447
2026-09-08 22:27
调整 service-integration-e2e 的执行时机描述，从最终阶段改为可执行时尽早进行。
-
416af89
2026-08-12 16:38
修复因缺失AskUserQuestion协议导致的Agent声明问题，明确技能所有权边界及约束条件。
- d439b50 2026-07-31 02:52
-
56ab6c1
2026-07-19 22:43
重构：改进了提示词执行指南，优化了测试类型定义表中的列名（从Limits改为Standard Budget per Input Design Doc），并细化了预算应用规则说明。
- 66e3b29 2026-07-05 11:59
