vitest · itechmeat — скилл для Claude Code: что делает и как установить
Скилл для Claude Code помогает писать и настраивать тесты Vitest: моки, снимки, покрытие и браузерный режим. Работает с Vite- и TypeScript-проектами.
MIT 202 установок ★ 23 обновлён 2026-10-24
npx skills add itechmeat/llm-code --skill vitest -a claude-codeЧто делает vitest
Скилл даёт агенту рабочий контекст для Vitest: API тестов и проверок, хуки, моки через vi.fn и vi.mock, fake timers, snapshots, CLI и конфигурацию в vitest.config.ts. Он также охватывает покрытие, UI-режим, параллельный запуск и тесты в реальном браузере.
В примерах есть тестовые файлы *.test.* и *.spec.*, команды vitest, vitest run, vitest run --coverage и vitest --browser.enabled. Агент сможет подготовить тесты, добавить настройки или объяснить переход с Jest-совместимым API. Для Vitest v5 нужны Node.js >=22 и Vite >=6.4, иначе запуск сломается.
Какие задачи решает
- написать модульные тесты для функций и классов
- настроить моки API и fake timers
- добавить snapshots для результатов и компонентов
- включить отчёты о покрытии кода
- запустить тесты в браузерном режиме
Примеры запросов агенту
- Настрой Vitest в этом Vite-проекте и создай
vitest.config.ts. - Напиши тесты для
src/api.tsс моками внешнего API и проверкой вызовов. - Добавь скрипт покрытия и подготовь команду
vitest run --coverage.
Как установить vitest
1Через Skills CLI (Vercel)
npx skills add itechmeat/llm-code --skill vitest -a claude-code2Вручную: положить файлы
~/.claude/skills/vitest/SKILL.mdПапка скилла целиком; для одного проекта — .claude/skills/vitest/
1Через Skills CLI (Vercel)
npx skills add itechmeat/llm-code --skill vitest -a codex2Вручную: положить файлы
.agents/skills/vitest/SKILL.mdДля всех проектов — ~/.agents/skills/
1Через Skills CLI (Vercel)
npx skills add itechmeat/llm-code --skill vitest -a cursor2Вручную: положить файлы
.cursor/skills/vitest/SKILL.mdCursor читает и .agents/skills/, и .claude/skills/
1GitHub CLI
gh skill install itechmeat/llm-code skills/vitest2Вручную: положить файлы
.github/skills/vitest/SKILL.md1Через Skills CLI (Vercel)
npx skills add itechmeat/llm-code --skill vitest -a gemini-cli2Командой платформы
gemini skills install https://github.com/itechmeat/llm-code --path skills/vitestВручную: положить файлы
.devin/skills/vitest/SKILL.mdСтарый путь .windsurf/skills/ тоже читается
Через Skills CLI (Vercel)
npx skills add itechmeat/llm-code --skill vitest -a opencodeClaude.ai
Упакуйте папку в zip и загрузите в Settings → Capabilities → Skills
По шагам, с командами для каждой платформы: Как установить скилл в Claude Code: пять способов
Вопросы о vitest
Как установить vitest в Claude Code?
Выполните npx skills add itechmeat/llm-code --skill vitest -a claude-code, затем проверьте файл ~/.claude/skills/vitest/SKILL.md.
Что делает vitest?
Скилл помогает агенту писать и настраивать тесты Vitest, включая проверки, моки, snapshots, покрытие, CLI и браузерный режим.
Что нужно для Vitest v5?
Нужны Node.js >=22 и Vite >=6.4. Тестовые файлы по умолчанию содержат .test. или .spec. в имени, также поддерживается каталог __tests__.
Исходный текст
SKILL.md · MIT
---
name: vitest
description: "Vitest testing framework: Vite-powered tests, Jest-compatible API, mocking, snapshots, coverage, browser mode, and TypeScript support. Use when writing or configuring tests with Vitest, setting up mocking/snapshots, configuring coverage, or running browser-mode tests. Keywords: Vitest, testing, Vite, Jest, mocking, coverage."
metadata:
version: "5.0.5"
release_date: "2026-10-15"
---
# Vitest
Next generation testing framework powered by Vite.
## Quick Navigation
- [Test API](references/api.md) - test, describe, hooks
- [Expect API](references/expect.md) - matchers and assertions
- [Mocking](references/mocking.md) - vi.fn, vi.mock, fake timers
- [Configuration](references/config.md) - vitest.config.ts options
- [CLI](references/cli.md) - command line reference
- [Browser Mode](references/browser.md) - real browser testing
## When to Use
- Testing Vite-based applications (shared config)
- Need Jest-compatible API with native ESM support
- Component testing in real browser
- Fast watch mode with HMR
- TypeScript testing without extra config
- Parallel test execution
## Installation
Install: `npm install -D vitest`. Requires Node.js >=22 and Vite >=6.4 in v5.
## Release Highlights (5.0.0)
- **Requirements:** Node.js >=22 and Vite >=6.4 are required. `@vitest/runner` is inlined (the package is no longer published) and `expect` is inlined, so old entry points were removed.
- **Mock/timer behavior:** mocks are cleared by default before each test, and `Temporal` can now be mocked (with or without fake timers).
- **Replaced APIs:** `sequential` test/suite options are removed in favor of `concurrent`; the `webdriverio` browser provider is removed; `toHaveTextContent` is strict with `toMatchTextContent` as the alternative; `expect.poll` fails when the function does not resolve in time.
- **New defaults/outputs:** `attachmentsDir` defaults to `.vitest/attachments/` (was `.vitest-attachments/`), and blob/json/junit/html reporter outputs default to `.vitest`; a `createReport` API and `.vitest` report directory convention are introduced.
- **Projects:** inline projects extend the root config by default, nested projects are supported, distinct projects share one Vite server, and the config file is no longer looked up from ancestor directories (parent dirs no longer apply).
- **Browser:** locator objects replace locator strings, `locators.exact` is on by default, and a `screenshotDirectory` config controls `toMatchScreenshot` output.
- **Misc:** benchmark public API was rewritten with a pluggable provider API; `-p` is a shorthand for `--project`; `-t` uses `>` as separator; coverage `thresholds.perFile` accepts an object and TypeScript build mode / `vitest list` static parsing are supported.
## Patch Notes (5.0.1 -> 5.0.5)
- `5.0.2` to `5.0.5` are fixes only — the `5.0` API surface is unchanged.
- The root temp directory is removed when the run closes, and `--changed` handles quoted file names.
- `import.meta.hot` stubs expose `data`, `skipIf` sets `skip` and ignores `undefined` options, and the native loader keeps the import frame inside its errors.
- Browser mode: late connections of closed sessions are dropped, global setup runs once with instances, the browser waits up to 30s to close, and synthetic `pagehide` events are ignored.
- Hook cleanups run even when a later hook fails, mocks of finished test files are released, and all running tests are aborted on cancel.
- The reporter reports end reason `failed` when a worker crashes.
## Release Highlights (4.1.0 -> 4.1.6)
- New control-flow hooks: `aroundEach` and `aroundAll`.
- Test metadata expands with tags, `meta`, and improved `test.extend` type inference.
- CLI adds `--detect-async-leaks`, richer `--update` modes, and static collection for `vitest list`.
- Browser mode grows Playwright persistent contexts, `userEvent.wheel`, and stronger trace/artifact handling.
- Mocking/timers add disposable `doMock()`, `mockThrow` / `mockThrowOnce`, and `setTickMode`.
- `4.1.4` adds experimental ARIA snapshots, `filterMeta` for the JSON reporter, and exposes `assertion` as a public experimental field.
- `4.1.5` adds coverage `instrumenter` support and improves reporter/UI behavior around large snapshots and HTML output.
- `4.1.6` tightens browser screenshot path resolution and fixes `sequence.concurrent` handling for concurrent test scheduling.
## Quick Start
```js
// sum.js
export function sum(a, b) {
return a + b;
}
```
```js
// sum.test.js
import { expect, test } from "vitest";
import { sum } from "./sum.js";
test("adds 1 + 2 to equal 3", () => {
expect(sum(1, 2)).toBe(3);
});
```
```json
// package.json
{
"scripts": {
"test": "vitest",
"test:run": "vitest run",
"coverage": "vitest run --coverage"
}
}
```
## Configuration
```ts
// vitest.config.ts (recommended)
import { defineConfig } from "vitest/config";
export default defineConfig({
test: {
globals: true, // Enable global test APIs
environment: "jsdom", // Browser-like environment
include: ["**/*.{test,spec}.{js,ts,jsx,tsx}"],
coverage: {
provider: "v8",
reporter: ["text", "html"],
},
},
});
```
Or extend Vite config:
```ts
// vite.config.ts
/// <reference types="vitest/config" />
import { defineConfig } from "vite";
export default defineConfig({
test: {
// test options
},
});
```
## Test File Naming
By default, tests must contain `.test.` or `.spec.` in filename:
- `sum.test.js`
- `sum.spec.ts`
- `__tests__/sum.js`
## Key Commands
```bash
# Watch mode (default)
vitest
# Single run
vitest run
# With coverage
vitest run --coverage
# Filter by file/test name
vitest sum
vitest -t "should add"
# UI mode
vitest --ui
# Browser tests
vitest --browser.enabled
```
## Common Patterns
### Basic Test
```ts
import { describe, it, expect, beforeEach } from "vitest";
describe("Calculator", () => {
let calc: Calculator;
beforeEach(() => {
calc = new Calculator();
});
it("adds numbers", () => {
expect(calc.add(1, 2)).toBe(3);
});
it("throws on invalid input", () => {
expect(() => calc.add("a", 1)).toThrow();
});
});
```
### Mocking
```ts
import { vi, expect, test } from "vitest";
import { fetchUser } from "./api";
vi.mock("./api", () => ({
fetchUser: vi.fn(),
}));
test("uses mocked API", async () => {
vi.mocked(fetchUser).mockResolvedValue({ name: "John" });
const user = await fetchUser(1);
expect(fetchUser).toHaveBeenCalledWith(1);
expect(user.name).toBe("John");
});
```
### Snapshot Testing
```ts
import { expect, test } from "vitest";
test("matches snapshot", () => {
const result = generateConfig();
expect(result).toMatchSnapshot();
});
// Inline snapshot (auto-updates)
test("inline snapshot", () => {
expect({ foo: "bar" }).toMatchInlineSnapshot();
});
```
### Async Testing
```ts
import { expect, test } from "vitest";
test("async/await", async () => {
const result = await fetchData();
expect(result).toBeDefined();
});
test("resolves", async () => {
await expect(Promise.resolve("ok")).resolves.toBe("ok");
});
test("rejects", async () => {
await expect(Promise.reject(new Error())).rejects.toThrow();
});
```
### Fake Timers
```ts
import { vi, expect, test, beforeEach, afterEach } from "vitest";
beforeEach(() => {
vi.useFakeTimers();
});
afterEach(() => {
vi.useRealTimers();
});
test("advances time", () => {
const callback = vi.fn();
setTimeout(callback, 1000);
vi.advanceTimersByTime(1000);
expect(callback).toHaveBeenCalled();
});
```
## Jest Migration
Most Jest code works with minimal changes:
```diff
- import { jest } from '@jest/globals'
+ import { vi } from 'vitest'
- jest.fn()
+ vi.fn()
- jest.mock('./module')
+ vi.mock('./module')
- jest.useFakeTimers()
+ vi.useFakeTimers()
```
**Key differences:**
- Use `vi` instead of `jest`
- Globals not enabled by default (add `globals: true`)
- `vi.mock` is hoisted (use `vi.doMock` for non-hoisted)
- No `jest.requireActual` (use `vi.importActual`)
## Environment Selection
```ts
// vitest.config.ts
{
test: {
environment: 'jsdom', // or 'happy-dom', 'node', 'edge-runtime'
}
}
// Per-file (docblock at top)
/** @vitest-environment jsdom */
```
## TypeScript
```json
// tsconfig.json
{
"compilerOptions": {
"types": ["vitest/globals"]
}
}
```
## References
See `references/` directory for detailed documentation on:
- Test API and hooks
- All expect matchers
- Mocking functions and modules
- Configuration options
- CLI commands
- Browser mode testing
## Links
- [Documentation](https://vitest.dev/)
- [API Reference](https://vitest.dev/api/)
- [GitHub](https://github.com/vitest-dev/vitest)
- [VS Code Extension](https://marketplace.visualstudio.com/items?itemName=vitest.explorer)
© itechmeat · MIT · itechmeat/llm-code
Похожие скиллы
Все скиллы по теме «Тесты и QA» →Сначала — vitest от других авторов.