菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | integration-ui-tester |
| description | 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. |
测试 组件 + 工作区挂载，路径 tests/integration/*.spec.tsx。
EpcValidationPanel, EpcCoveragePanel, ScenarioWorkspaceElementLibrary, ElementCoverageBadgeBusinessChainDetail 子树（可 mock 重型依赖）import { render, screen, fireEvent } from '@testing-library/react';
import { useOntologyStore } from '@/store/ontology-store';
// setup store in beforeEach, then:
render(<ScenarioWorkspace scenario={...} childEpcs={...} ... />);
fireEvent.click(screen.getByTestId('vp-tab-vx'));
expect(screen.getByTestId('vp-vx-0')).toHaveTextContent('VX-09');
// 避免 getByText 匹配到 filter 按钮与列表重复
panelInactive → vp-empty-statevp-tab-vmvi.useFakeTimers() 与 waitFor 同文件（E2E 规则；integration 慎用 fake timers）npx vitest run tests/integration/epc-validation-panel.spec.tsx
npx vitest run tests/integration/
pnpm test:integration
test-driven-developmentreceiving-code-reviewGoal-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 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.
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.