菜单
Implement Playwright E2E tests for X4 changes from `e2e_test_tasks.md` and validate task-to-test mapping. Trigger with /x4:e2e-test-impl <change-name>.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | x4-e2e-test-impl |
| description | Implement Playwright E2E tests for X4 changes from `e2e_test_tasks.md` and validate task-to-test mapping. Trigger with /x4:e2e-test-impl <change-name>. |
根据 openspec/changes/<change-name>/e2e_test_tasks.md 与 knowledge.md 实现或补充 Playwright E2E 测试。
本 skill 只处理 E2E 测试实现，不处理旧 test_tasks.md 的 Unit/E2E/Bug 混合任务。
如果 change 存在 fixture patch 需求，必须先由 x4-e2e-test-doc-details 准备并校验 fixture，再进入本 skill。
openspec/changes/<change-name>/e2e_test_tasks.mdopenspec/changes/<change-name>/knowledge.mdopenspec/changes/<change-name>/fixtures.md（如存在）tests/e2e/<change-name>/fixtures/*.patch.json（如存在）tests/e2e/<change-name>/**/*.spec.tse2e_test_tasks.md 中每个顶层任务 x.y 必须对应一个 Playwright test() 用例。test('1.1 自动分组入口展示核心状态', async ({ page }) => {
x.y.z 必须在对应测试用例中以注释标记：
// 1.1.1 进入地图视图并定位自动分组入口
knowledge.md 中记录的 locator、fixture、UI 入口与断言策略。fixtures.md 记录了当前 case 需要的 patch，测试必须 import 对应 tests/e2e/<change-name>/fixtures/*.patch.json。tests/helper/e2eFixturePatch.ts 中的 helper 载入基础 fixture 和 patch。save.json patch；localStorage / db.json 状态优先通过 UI 操作形成。db.json patch。openspec/changes/<change-name>/fixtures/generate-*-patch.ts。fixtures.md 中声明的 patch，或 patch 无法通过校验，返回 x4-e2e-test-doc-details，不要在实现阶段临时改数据结构。实现或修改测试后，必须运行：
python3 .trae/skills/x4-e2e-test-impl/scripts/validate_e2e_case_refs.py <change-name> --json
如果校验失败，先修复任务-用例映射，再进入测试运行阶段。
遵守仓库 AGENTS.md 中的 E2E beforeEach 规则：
tests/fixtures/db.json 到 localStorage，排除 vsn。db.json patch 应用到基础 fixture，再写入 localStorage。localStorage.clear()。x4-e2e-test-doc-details 产出的 save patch 约定扩展 wrapper。e2e_tests.md 和 e2e_test_tasks.md 的任务定义；发现文档缺失时，返回 x4-e2e-test-doc。test_tasks.md。validate_e2e_case_refs.py 结果。x4-e2e-test-run 的测试命令。Use when x4-e2e-test-doc-details needs fixture patch rules or helper guidance for X4 E2E test data.
Use when refining X4 `e2e_tests.md` into detailed E2E task, fixture, and implementation knowledge documents before Playwright implementation.
Use when creating or updating only the high-level X4 E2E test plan `e2e_tests.md` before detail expansion.
Review X4 E2E test documentation draft and gate x4-e2e-test-doc completion. Must run in a dedicated isolated subagent. Trigger with /x4:e2e-test-doc-viewer <change-name>.
Run change-scoped X4 Playwright E2E tests and validate implementation coverage against `e2e_test_tasks.md`. Trigger with /x4:e2e-test-run <change-name>.
Orchestrate X4 E2E-only test workflow across high-level docs, detailed docs, review, implementation, and run phases. Trigger with /x4:e2e-test <change-name>.