ts-testing

原文涵盖的主题

• TypeScript Testing
• Agent Workflow (MANDATORY)
• Overview
• Critical Rules
• Decision Guide
• Reference Guide
• Concepts
• Templates

This skill covers choosing between bun test (fastest cold start, zero-config TS/JSX, experimental coverage) and Vitest (V8/Istanbul coverage, multi-worker CI scaling, browser mode via Playwright) via a decision matrix by project shape, then configuring the chosen runner's shared Jest-like API — describe/it/expect, lifecycle hooks, mocks, and snapshots. It also covers coverage thresholds, deterministic test isolation, and the rule to never mix bun:test and vitest imports in one package, or run bun test when the configured runner is actually Vitest. Out of scope: framework-specific testing (React components → react-expert's react-testing, Laravel → laravel-testing) and browser E2E suites are not covered. Pick the right runner, then write tests with a shared Jest-compatible API. Before ANY implementation, spawn 3 agents in parallel, one Agent call each with a name: 1. fuse-ai-pilot:explore-codebase - Detect existing runner, config, test layout 2. fuse-ai-pilot:research-expert - Verify latest bun test / Vitest docs via Context7/Exa 3. mcpcontext7query-docs - Check mock, coverage, config APIs After implementation, run fuse-ai-pilot:sniper for validation. -- Both runners share a Jest-lik

这里只展示节选，请以完整原文和当前要求为准。