docs(cn): update /guide

guide/advanced/pool.md

@@ -1,42 +1,40 @@
-# Custom Pool <Badge type="danger">advanced</Badge> {#custom-pool}
-
-<!-- TODO: translation -->
+# 自定义池 <Badge type="danger">高级</Badge> {#custom-pool}
 
 ::: warning
-This is an advanced, experimental and very low-level API. If you just want to [run tests](/guide/), you probably don't need this. It is primarily used by library authors.
+这是一个高级用法的实验性底层 API，主要供库作者使用。如果你只是想 [运行测试](/guide/)，通常不需要使用它。
 :::
 
-Vitest runs tests in a pool. By default, there are several pool runners:
+Vitest 在池中运行测试。默认提供以下几种池运行器：
 
-- `threads` to run tests using `node:worker_threads` (isolation is provided with a new worker context)
-- `forks` to run tests using `node:child_process` (isolation is provided with a new `child_process.fork` process)
-- `vmThreads` to run tests using `node:worker_threads` (but isolation is provided with `vm` module instead of a new worker context)
-- `browser` to run tests using browser providers
-- `typescript` to run typechecking on tests
+- `threads`：使用 `node:worker_threads` 运行测试，通过创建新的工作线程上下文实现隔离。
+- `forks`：使用 `node:child_process` 运行测试，通过 `child_process.fork` 创建新的进程实现隔离。
+- `vmThreads`：使用 `node:worker_threads` 运行测试，通过 `vm` 模块实现隔离，而不是创建新的工作线程上下文。
+- `browser`：使用浏览器 provider 运行测试。
+- `typescript`：对测试进行类型检查
 
 ::: tip
-See [`vitest-pool-example`](https://npmx.dev/package/vitest-pool-example) for example of a custom pool runner implementation.
+自定义池运行器的实现示例，请参阅 [`vitest-pool-example`](https://npmx.dev/package/vitest-pool-example)。
 :::
 
-## Usage
+## 用法 {#usage}
 
-You can provide your own pool runner by a function that returns `PoolRunnerInitializer`.
+你可以编写一个返回 `PoolRunnerInitializer` 的函数，提供自定义池运行器。
 
 ```ts [vitest.config.ts]
 import { defineConfig } from 'vitest/config'
 import customPool from './my-custom-pool.ts'
 
 export default defineConfig({
   test: {
-    // will run every file with a custom pool by default
+    // 默认使用自定义池运行所有文件
     pool: customPool({
       customProperty: true,
     })
   },
 })
 ```
 
-If you need to run tests in different pools, use the [`projects`](/guide/projects) feature:
+如果需要在不同的 pool 中运行测试，可以使用 [`projects`](/guide/projects) 功能。
 
 ```ts [vitest.config.ts]
 import customPool from './my-custom-pool.ts'
@@ -63,7 +61,7 @@ export default defineConfig({
 
 ## API
 
-The `pool` option accepts a `PoolRunnerInitializer` that can be used for custom pool runners. The `name` property should indicate name of the custom pool runner. It should be identical with your worker's `name` property.
+要使用自定义池运行器，可以将一个 `PoolRunnerInitializer` 对象传给 pool 选项。该对象的 `name` 属性表示池运行器的名称，须与 worker 的 `name` 属性一致。
 
 ```ts [my-custom-pool.ts]
 import type { PoolRunnerInitializer } from 'vitest/node'
@@ -90,23 +88,23 @@ class CustomPoolWorker implements PoolWorker {
   }
 
   send(message: WorkerRequest): void {
-    // Provide way to send your worker a message
+    // 向 worker 发送消息
   }
 
   on(event: string, callback: (arg: any) => void): void {
-    // Provide way to listen to your workers events, e.g. message, error, exit
+    // 监听 worker 事件的方式，例如 message、error 和 exi
   }
 
   off(event: string, callback: (arg: any) => void): void {
-    // Provide way to unsubscribe `on` listeners
+    // 移除通过 `on` 注册的监听器
   }
 
   async start() {
-    // do something when the worker is started
+    // 在 worker 启动时执行操作
   }
 
   async stop() {
-    // cleanup the state
+    // 清理状态
   }
 
   deserialize(data) {
@@ -115,31 +113,31 @@ class CustomPoolWorker implements PoolWorker {
 }
 ```
 
-Your `CustomPoolRunner` will be controlling how your custom test runner worker life cycles and communication channel works. For example, your `CustomPoolRunner` could launch a `node:worker_threads` `Worker`, and provide communication via `Worker.postMessage` and `parentPort`.
+`CustomPoolRunner` 负责管理自定义测试运行器 worker 的生命周期和通信通道。例如，`CustomPoolRunner` 可以启动一个 `node:worker_threads` 的 `Worker`，并通过 `Worker.postMessage` 和 `parentPort` 进行通信。
 
-In your worker file, you can import helper utilities from `vitest/worker`:
+在 worker 文件中，你可以从 `vitest/worker` 导入工具函数
 
 ```ts [my-worker.ts]
 import { init, runBaseTests, setupEnvironment } from 'vitest/worker'
 
 init({
   post: (response) => {
-    // Provide way to send this message to CustomPoolRunner's onWorker as message event
+    // 将这条消息以 message 事件的形式传给 CustomPoolRunner 的 onWorker
   },
   on: (callback) => {
-    // Provide a way to listen CustomPoolRunner's "postMessage" calls
+    // 监听 CustomPoolRunner 的 "postMessage" 调用
   },
   off: (callback) => {
-    // Optional, provide a way to remove listeners added by "on" calls
+    // 可选，移除通过 "on" 注册的监听器
   },
   teardown: () => {
-    // Optional, provide a way to teardown worker, e.g. unsubscribe all the `on` listeners
+    // 可选：清理 worker，例如移除所有通过 `on` 注册的监听器
   },
   serialize: (value) => {
-    // Optional, provide custom serializer for `post` calls
+    // 可选：自定义 `post` 调用的序列化方式
   },
   deserialize: (value) => {
-    // Optional, provide custom deserializer for `on` callbacks
+    // 可选：自定义传给 `on` 回调的数据的反序列化方式
   },
   runTests: (state, traces) => runBaseTests('run', state, traces),
   collectTests: (state, traces) => runBaseTests('collect', state, traces),

guide/migration/jest.md

@@ -74,9 +74,7 @@ Vitest 的测试名使用 `>` 符号连接，方便区分测试与套件，而 J
 + `${describeTitle} > ${testTitle}`
 ```
 
-<!-- TODO: translation -->
-
-The same applies to [`testNamePattern`](/config/testnamepattern) (the `-t` flag): Vitest matches against the `>`-joined full name, while Jest matches the space-joined name. Update patterns that span a suite and a test accordingly, or match a single segment (`-t adds`) or use a wildcard between segments (`-t 'math.*adds'`).
+这同样适用于 [`testNamePattern`](/config/testnamepattern)（`-t` 参数）：Vitest 匹配的是以 `>` 连接的完整测试名，而 Jest 匹配的是以空格连接的测试名。因此，须相应更新跨测试套件和测试用例的匹配规则，或仅匹配单个片段 (`-t adds`)，或在片段之间使用通配符（`-t 'math.*adds'`）
 
 ```diff
 - vitest -t 'math adds'

guide/migration/mocha.md

@@ -84,9 +84,7 @@ expect(spy).to.have.been.calledWith('arg1', 'arg2')
 
 ### 完整的 Chai 风格断言支持 {#complete-chai-style-assertion-support}
 
-<!-- TODO: translation -->
-
-Vitest supports all common sinon-chai assertions:
+Vitest 支持所有常见的 sinon-chai 断言：
 
 | Sinon-Chai                | Vitest                | 详情                         |
 | ------------------------- | --------------------- | ---------------------------- |

guide/ui.md

@@ -15,9 +15,9 @@ npm i -D @vitest/ui
 <img alt="Vitest UI" img-light src="/ui-1-light.png">
 <img alt="Vitest UI" img-dark src="/ui-1-dark.png">
 
-## Live UI
+## 测试 UI 界面 {#live-ui}
 
-The Live UI runs alongside Vitest's development server and requires [watch mode](/config/watch), which is enabled by default. It stays connected to the running Vitest process, so results update as tests rerun. You can also rerun selected tests, update failed snapshots, and edit test files directly from the UI.
+测试 UI 界面与 Vitest 的开发服务器一同运行，需要启用 [watch 模式](/config/watch)（默认启用）。它会持续连接到正在运行的 Vitest 进程，在每次重新运行测试时，结果都会随之更新。你还可以直接在 UI 中重新运行选定的测试、更新失败的快照，以及编辑测试文件。
 
 接下来，你可以通过传入 `--ui` 参数来启动测试的 UI 界面：
 
@@ -26,20 +26,18 @@ vitest --ui
 ```
 
 最后，你可以访问 Vitest UI 界面，通过 <a href="http://localhost:51204/__vitest__/">`http://localhost:51204/__vitest__/`</a>
-<!-- TODO: translation -->
 
 ::: tip
-Vitest UI access is protected. If the direct URL shows an error, open the URL with a token printed by Vitest in the terminal, for example `http://localhost:51204/__vitest__/?token=...`.
+Vitest UI 设有访问保护。如果直接访问上述 URL 时出现错误，请打开 Vitest 在终端中输出的带有令牌的 URL，例如 `http://localhost:51204/__vitest__/?token=...`。
 :::
 
-## HTML Reporter
+## HTML 报告器 {#html-reporter}
 
-The HTML reporter writes test results to a static version of Vitest UI. The result views remain navigable, but the report is read-only and cannot rerun tests, update snapshots, or edit test files. It is useful for run mode, CI, and automated workflows where results are reviewed later.
+HTML 报告器会将测试结果写入静态版的 Vitest UI。你可以浏览各个结果视图，但报告是只读的，无法重新运行测试、更新快照或编辑测试文件。它适用于单次运行模式、CI 或自动化工作流中，你可以使用 HTML 报告保存测试结果，方便之后查看。
 
-Use the `html` reporter from the command line or in your Vitest configuration:
+在命令行或 Vitest 配置中使用 `html` 报告器：
 
 ::: code-group
-
 ```ts [vitest.config.ts]
 import { defineConfig } from 'vitest/config'
 
@@ -53,11 +51,10 @@ export default defineConfig({
 ```bash [CLI]
 vitest run --reporter=html
 ```
-
 :::
 
-::: tip Keep terminal output
-Configuring the HTML reporter replaces the default terminal reporter. To keep terminal output, [include Vitest's default reporters](/guide/reporters#default-configuration).
+::: tip 保留终端输出
+配置 HTML 报告器后，它会替换默认的终端报告器。如果要保留终端的输出，请同时启用 [Vitest 的默认报告器](/guide/reporters#default-configuration)。
 
 ```ts [vitest.config.ts]
 import { configDefaults, defineConfig } from 'vitest/config'
@@ -68,24 +65,23 @@ export default defineConfig({
   },
 })
 ```
-
 :::
 
-### Preview Locally
+### 本地预览 {#preview-locally}
 
-By default, the report entry is written to `.vitest/index.html`. You can configure the artifact directory with the HTML reporter's `outputDir` option.
+默认情况下，报告入口文件会写入 `.vitest/index.html`。你可以通过 HTML 报告器的 `outputDir` 配置项变更测试产物的输出目录。
 
-To preview the default output, use the [vite preview](https://vitejs.dev/guide/cli.html#vite-preview) command:
+如需预览默认输出的报告，请使用 [vite preview](https://cn.vitejs.dev/guide/cli.html#vite-preview) 命令：
 
 ```sh
 npx vite preview --outDir .vitest
 ```
 
-Open the URL printed by Vite in your browser. Alternatively, [VS Code's Integrated Browser](https://code.visualstudio.com/docs/debugtest/integrated-browser) can open `.vitest/index.html` directly without a preview server.
+可以在浏览器中打开 Vite 输出的 URL。无须启动预览服务器也可以使用 [VS Code 的集成浏览器 ](https://code.visualstudio.com/docs/debugtest/integrated-browser) 直接打开 `.vitest/index.html`。
 
-### Share as a Single File
+### 单文件分享报告 {#share-as-a-single-file}
 
-Set `singleFile` to generate a self-contained HTML report:
+将 `singleFile` 设为 true，即可生成无需依赖其他文件的 HTML 报告：
 
 ```ts [vitest.config.ts]
 export default defineConfig({
@@ -97,22 +93,22 @@ export default defineConfig({
 })
 ```
 
-When `singleFile` is enabled, Vitest inlines the UI assets, metadata, and test attachments into a single self-contained `index.html`. This makes the report easy to share, upload, or download as one artifact instead of preserving the whole output directory.
+启用 `singleFile` 后，Vitest 会将 UI 资源、元数据和测试附件内联到一个 `index.html` 文件中。这样，你就可以将报告作为单个测试产物分享、上传或下载，无须保留整个输出目录。
 
-Because everything is inlined, you can open `<outputDir>/index.html` directly in a browser with a `file://` URL. No preview server is required.
+由于所需资源都都是内联的，你可以通过 `file://` 直接在浏览器中打开 `<outputDir>/index.html`，无须启动预览服务器。
 
 ::: warning
-`singleFile` has two caveats:
+使用 `singleFile` 时，有两点需要注意：
 
-- The file can grow very large because everything is embedded inline. It can be slow to open, memory-hungry, or exceed the size limits of artifact viewers and static hosts.
-- Coverage HTML reports are not inlined yet and remain as separate files.
+- 所有内容都嵌入同一个文件，可能导致文件体积很大，打开缓慢、占用大量内存，或超出测试产物查看器和静态托管服务的文件大小限制。
+- 覆盖率 HTML 报告不会内联，仍以独立文件保存。
 
-Prefer the default multi-file report when the suite has many or large attachments, or when you need coverage included in the bundle.
+如果测试套件包含大量附件或体积较大的附件，或者需要将覆盖率报告一并打包，建议使用默认的多文件报告。
 :::
 
-### View Reports from CI
+### 查看 CI 中的报告 {#view-reports-from-ci}
 
-To view the HTML report from CI, for example in GitHub Actions, upload the output directory as an artifact:
+使用 GitHub Actions 等 CI 平台时，可以将报告的输出目录作为测试产物上传，方便后续查看：
 
 ```yaml
 - uses: actions/upload-artifact@v7
@@ -127,9 +123,9 @@ To view the HTML report from CI, for example in GitHub Actions, upload the outpu
     REPORT_URL: https://viewer.vitest.dev/?url=${{ steps.upload-report.outputs.artifact-url }}
 ```
 
-This adds the report link as a notice annotation on the workflow run. Click it to open the report in [Vitest Viewer](https://viewer.vitest.dev/) directly in the browser. You can also download the artifact manually and extract it, then run `vite preview` locally as above.
+上述配置会在工作流运行页面添加一条包含报告链接的通知。点击链接，即可通过 [Vitest Viewer](https://viewer.vitest.dev/) 直接在浏览器中查看报告。你也可以手动下载并解压测试产物，再按前面的方法在本地运行 `vite preview`。
 
-When you use `singleFile: true`, you can upload the report as a single file and view it directly from GitHub artifacts with the [`archive: false` option](https://github.com/actions/upload-artifact#upload-an-individual-file-unzipped):
+使用 `singleFile: true` 时，你可以通过 [`archive: false` 选项](https://github.com/actions/upload-artifact#upload-an-individual-file-unzipped) 将报告作为单文件上传到 GitHub，点击测试产物链接查看报告：
 
 ```yaml
 - uses: actions/upload-artifact@v7
@@ -144,13 +140,13 @@ When you use `singleFile: true`, you can upload the report as a single file and
     REPORT_URL: ${{ steps.upload-report.outputs.artifact-url }}
 ```
 
-## Coverage
+## 覆盖率 {#coverage}
 
-Vitest UI displays coverage results in both the Live UI and HTML reports. See [Vitest UI Coverage](/guide/coverage#vitest-ui) for setup and usage.
+Vitest UI 和 HTML 报告都支持显示覆盖率结果。配置和使用方法请参阅 [Vitest UI 覆盖率](/guide/coverage#vitest-ui)。
 
-## Trace View
+## 追踪视图 {#trace-view}
 
-Vitest UI replays recorded browser interactions when [`browser.traceView`](/guide/browser/trace-view) is enabled. The Live UI streams trace entries as tests run, while HTML reports preserve recorded traces for later review.
+启用 [`browser.traceView`](/guide/browser/trace-view) 后，Vitest UI 可以回放已录制的浏览器交互。Vitest UI 会实时显示在测试运行时追踪记录，HTML 报告会保存这些记录供之后查看。
 
 ## 模块图 {#module-graph}
 
@@ -241,6 +237,6 @@ Vitest UI replays recorded browser interactions when [`browser.traceView`](/guid
 
 分析列表包含自用耗时、总耗时以及相对于加载整个测试文件所花费时间的百分比。
 
-当存在至少一个文件加载时间超过 [`danger` 阈值](/config/experimental#experimental-importdurations-thresholds)（默认值：500 毫秒）时，“显示导入耗时分析” 图标将呈现红色；如果存在至少一个文件加载时间超过 [`warn`阈值](/config/experimental#experimental-importdurations-thresholds)（默认值：100 毫秒），则图标显示为橙色。
+当存在至少一个文件加载时间超过 [`danger` 阈值](/config/experimental#experimental-importdurations-thresholds)（默认值：500 毫秒）时，“显示导入耗时分析” 图标将呈现红色；如果存在至少一个文件加载时间超过 [`warn` 阈值](/config/experimental#experimental-importdurations-thresholds)（默认值：100 毫秒），则图标显示为橙色。
 
 你可以使用 [`experimental.importDurations.limit`](/config/experimental#experimental-importdurationslimit) 配置项控制显示的导入项数量上限。