vitest

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Chinese

<skill_doc> <trigger_keywords>

Activate this skill when the user mentions any of:

Core: Vitest, Vite Test, vi.mock, vi.fn, describe, it, test, expect

Configuration: vitest.config.ts, in-source testing, coverage

Comparison: Jest replacement, faster than Jest </trigger_keywords>

当用户提及以下任意内容时激活此技能：

核心：Vitest, Vite Test, vi.mock, vi.fn, describe, it, test, expect

配置：vitest.config.ts, 源码内测试, coverage

对比：Jest替代方案, 比Jest更快 </trigger_keywords>

NO
jest
Global: Do not use

jest.fn()

jest.mock()

. Use

vi.fn()

and

vi.mock()

NO CommonJS require: Vitest is ESM-first. Use
```
import
```
statements.
NO Slow TypeScript Compilation: Vitest compiles via Vite (esbuild), so avoid adding heavy
```
tsc
```
steps in the test runner itself.
NO
module.exports
: Use
```
export default
```
or named exports in your test files or mocks.

禁止使用
jest
全局对象：不要使用
```
jest.fn()
```
或
```
jest.mock()
```
。请使用
```
vi.fn()
```
和
```
vi.mock()
```
。
禁止使用CommonJS的require：Vitest优先支持ESM。请使用
```
import
```
语句。
禁止缓慢的TypeScript编译：Vitest通过Vite（esbuild）进行编译，因此请避免在测试运行器中添加繁重的
```
tsc
```
步骤。
禁止使用
module.exports
：在测试文件或模拟文件中请使用
```
export default
```
或具名导出。

Config Check: Look for
```
vitest.config.ts
```
or
```
vite.config.ts
```
to understand the environment (globals enabled? environment: jsdom?).
Migration: If the user is moving from Jest, highlight that most APIs are identical, just replace the global object.
Mocking: Use
```
vi.spyOn
```
and
```
vi.mock
```
for isolating dependencies.
UI: Mention
```
vitest ui
```
for a visual test runner experience.

配置检查：查找
```
vitest.config.ts
```
或
```
vite.config.ts
```
以了解环境（是否启用全局变量？环境为jsdom？）。
迁移指导：如果用户正从Jest迁移，需强调大多数API完全相同，只需替换全局对象即可。
模拟操作：使用
```
vi.spyOn
```
和
```
vi.mock
```
来隔离依赖项。
UI界面：推荐使用
```
vitest ui
```
以获得可视化测试运行器体验。

Vitest Specialist - "Vite Native Unit Testing".

Philosophy:

Workflow:

Vitest专家 - "Vite原生单元测试"

设计理念:

工作流程:

Examples: See
```
examples/examples.md
```
for detailed code patterns.
References: See
```
references/reference.md
```
for official documentation links. </skill_doc>