Use when writing unit/integration tests for Vite projects - configure vitest.config.ts, write test suites with describe/it, create mock implementations with vi.fn and vi.mock, set up code coverage thresholds, and run tests in parallel
95
100%
Does it follow best practices?
Impact
78%
1.50xAverage score across 3 eval scenarios
Passed
No known issues
Vitest config and coverage setup
mergeConfig usage
100%
100%
Correct import source
100%
100%
globals enabled
0%
100%
Node environment
100%
100%
fileParallelism enabled
0%
100%
Coverage provider
100%
100%
Coverage reporters
100%
100%
Coverage include filter
0%
100%
Coverage thresholds
100%
100%
Pool configured
100%
100%
Coverage include sources
0%
0%
Module mocking patterns
vi.mock hoisted
100%
100%
vi.hoisted usage
0%
0%
Partial mock with importOriginal
0%
0%
Spy-mode mock
30%
0%
vi.doMock usage
100%
100%
vi.stubEnv usage
100%
100%
vi.mocked TypeScript helper
100%
100%
Mock return values
100%
100%
toHaveBeenCalledWith assertions
100%
100%
vi.unstubAllEnvs cleanup
100%
100%
Advanced test patterns and fixtures
test.for usage
0%
0%
No test.each
0%
0%
test.concurrent with context expect
0%
83%
test.extend fixture
0%
100%
Fixture teardown
0%
100%
onTestFinished usage
100%
100%
expect.soft usage
100%
100%
expect.poll usage
0%
100%
Fixture dependency injection
0%
100%
00fb59d
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.