···11+---
22+title: Command Line Interface | Guide
33+---
44+15# Command Line Interface
2637## Commands
+4
docs/guide/comparisons.md
···11+---
22+title: Comparisons with Other Test Runners | Guide
33+---
44+15# Comparisons with Other Test Runners
2637## Jest
+4
docs/guide/coverage.md
···11+---
22+title: Coverage | Guide
33+---
44+15# Coverage
2637Vitest supports Native code coverage via [`c8`](https://github.com/bcoe/c8). `c8` is an optional peer dependency, to use the coverage feature you will need to install it first by:
···11+---
22+title: Extending Matchers | Guide
33+---
44+15# Extending Matchers
2637Since Vitest is compatible with both Chai and Jest, you can use either `chai.use` API or `expect.extend`, whichever you prefer.
+1
docs/guide/features.md
···11---
22+title: Features | Guide
23outline: deep
34---
45
+4
docs/guide/filtering.md
···11+---
22+title: Tests Filtering | Guide
33+---
44+15# Tests Filtering
2637Filtering, timeouts, concurrent for suite and tests
+4
docs/guide/ide.md
···11+---
22+title: IDE Integrations | Guide
33+---
44+15# IDE Integrations
2637## VS Code <sup><code>Official</code></sup>
+4
docs/guide/in-source.md
···11+---
22+title: In-source testing | Guide
33+---
44+15# In-source testing
2637Vitest also provides a way to run tests with in your source code along with the implementation, similar to [Rust's module tests](https://doc.rust-lang.org/book/ch11-03-test-organization.html#the-tests-module-and-cfgtest).
+5-1
docs/guide/index.md
···11+---
22+title: Getting Started | Guide
33+---
44+15# Getting Started
2637## Overview
···103107- [cz-git](https://github.com/Zhengqbbb/cz-git)
104108105109<!--
106106-For contributors:
110110+For contributors:
107111We no longer accept new entries to this list a this moment.
108112Thanks for choosing Vitest!
109113-->
+4
docs/guide/migration.md
···11+---
22+title: Migration Guide | Guide
33+---
44+15# Migration Guide
2637## Migrating from Jest
+6-1
docs/guide/mocking.md
···11+---
22+title: Mocking | Guide
33+---
44+15# Mocking
66+27When writing tests it's only a matter of time before you need to create "fake" version of an internal—or external—service. This is commonly referred to as **mocking**. Vitest provides utility functions to help you out through its **vi** helper. You can `import { vi } from 'vitest'` or access it **globally** (when [global configuration](/config/#globals) is **enabled**).
3849::: warning
···518523```ts
519524vi.stubGlobal('__VERSION__', '1.0.0')
520525expect(__VERSION__).toBe('1.0.0')
521521-```526526+```
+4
docs/guide/snapshot.md
···11+---
22+title: Snapshot | Guide
33+---
44+15# Snapshot
2637Snapshot tests are a very useful tool whenever you want to make sure the output of your functions not change unexpectedly.
+4
docs/guide/test-context.md
···11+---
22+title: Test Context | Guide
33+---
44+15# Test Context
2637Inspired by [Playwright Fixtures](https://playwright.dev/docs/test-fixtures), Vitest's test context allows you to define utils, states, and fixtures that can be used in your tests.
+4
docs/guide/ui.md
···11+---
22+title: Vitest UI | Guide
33+---
44+15# Vitest UI
2637Powered by Vite, Vitest also has a dev server under the hood when running the tests. This allows Vitest to provide a beautiful UI to view and interact with your tests. The Vitest UI is optional, you can install it by:
+4
docs/guide/using-plugins.md
···11+---
22+title: Using Plugins | Guide
33+---
44+15# Using Plugins
2637Vitest can be extended using plugins...