القائمة
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.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | e2e-smoke-tester |
| description | 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. |
用户路径冒烟，路径 tests/e2e/*.e2e.spec.ts，describe 含 @smoke。
vi.mock('@/hooks/use-project-sync', () => ({ useProjectSync: vi.fn() }));
vi.mock('next/navigation', () => ({ useRouter: () => ({ push: vi.fn(), ... }) }));
// mock 各 model editor 为 div testid
render(<ModelingWorkspace project={project} />);
fireEvent.click(screen.getByRole('button', { name: /业务链/i }));
await waitFor(() => {
expect(screen.getByTestId('epc-validation-panel')).toBeInTheDocument();
});
// ❌ beforeEach 里 vi.useFakeTimers() + waitFor → 挂死或 flaky
// ✅ E2E 用真实 timer + waitFor
tests/e2e/{feature}.e2e.spec.tsE2E-{FEATURE}-001 @smokenpx vitest run tests/e2e/epc-validation.e2e.spec.ts
npx vitest run tests/e2e/
pnpm test:e2e:smoke
@smoke 标记的「伪 E2E」混在 smoke 套件verification-before-completionsystematic-debuggingGoal-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/integration—React components with @testing-library/react, ScenarioWorkspace, panels, element-library. Focus on testids, tabs, empty states, and store wiring without full E2E.
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.