القائمة
Use before Coding (Unit step 3)—translate Unit Spec AC into Testing Cases with file paths, TC IDs, and pass/fail scenarios. Must complete before any production code for the Unit.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Goal-Loop methodology for multi-step agent work: strategy exploration, GOAL/GOALS/REPORT files, sub-goal state machine, iteration budgets, rollback, and decision logs. Use when the user asks for Goal-Loop, Goal Kit, GOAL.md, GOALS.md, REPORT.md, .hermes planning, multi-phase delivery with checkpoints, or structured goal decomposition before execution.
Use for rule-engine and domain logic tests—VX-01~12 cross-consistency, W-EPC-01~17 linter, epc-coverage computeCoverage, deriveEpcSteps ordering. Table-driven; one positive and one negative case per rule minimum.
Use for tests/e2e smoke flows—ModelingWorkspace, business chain navigation, C workspace panels, derive/apply EPC. Tag @smoke; use waitFor; never mix vi.useFakeTimers with waitFor.
Use for tests/integration—React components with @testing-library/react, ScenarioWorkspace, panels, element-library. Focus on testids, tabs, empty states, and store wiring without full E2E.
Use when orchestrating a US/Unit test effort—assigning subagents, defining exit criteria, and signing off only with fresh verification evidence. Test Lead does not write all tests; it plans, dispatches, and gates.
Use for tests/unit and store integration—pure functions (lib/*), Zustand store getters, and helpers. RED-GREEN with vitest; no React unless unavoidable.
| name | test-designer |
| description | Use before Coding (Unit step 3)—translate Unit Spec AC into Testing Cases with file paths, TC IDs, and pass/fail scenarios. Must complete before any production code for the Unit. |
Testing Cases 先于 Coding。 把 AC 变成可执行的 TC 矩阵与测试文件骨架。
Iron law: Step 3 checked before Step 4 starts.
tests/unit|integration|e2e 路径与 TC 表docs/ontology-simplification/units/US-*-U*-*.md（§4 AC、§2 范围）src/types/ontology.tsus-s16-testing-cases.md）| AC 类型 | 测试层 | 示例 |
|---|---|---|
| 纯函数 / Store API | tests/unit/ | deriveEpcSteps, getCrossConsistency |
| 组件渲染 / Tab 切换 | tests/integration/ | EpcValidationPanel |
| 业务链用户路径 | tests/e2e/ + @smoke | 选 C → 面板可见 |
| 每条规则 VX/W-EPC | tests/unit/ 表驱动 | 1 pass + 1 fail per rule |
每条 TC 必须：
Ontology 常见门禁，Designer 必须覆盖：
test-driven-developmentwriting-plans[x]