[READ-ONLY] Mirror of https://github.com/vitest-dev/vitest. Next generation testing framework powered by Vite. vitest.dev
test testing-tools vite
12

Configure Feed

Select the types of activity you want to include in your feed.

docs: add section title in guide pages (#1583)

authored by

Joaquín Sánchez and committed by
GitHub
(Jul 15, 2022, 12:28 AM +0800) 235cfa7e 21170eda

+68 -2
+4
docs/guide/cli.md
··· 1 + --- 2 + title: Command Line Interface | Guide 3 + --- 4 + 1 5 # Command Line Interface 2 6 3 7 ## Commands
+4
docs/guide/comparisons.md
··· 1 + --- 2 + title: Comparisons with Other Test Runners | Guide 3 + --- 4 + 1 5 # Comparisons with Other Test Runners 2 6 3 7 ## Jest
+4
docs/guide/coverage.md
··· 1 + --- 2 + title: Coverage | Guide 3 + --- 4 + 1 5 # Coverage 2 6 3 7 Vitest 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:
+4
docs/guide/debugging.md
··· 1 + --- 2 + title: Debugging | Guide 3 + --- 4 + 1 5 # Debugging 2 6 3 7 ## VSCode
+4
docs/guide/extending-matchers.md
··· 1 + --- 2 + title: Extending Matchers | Guide 3 + --- 4 + 1 5 # Extending Matchers 2 6 3 7 Since 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
··· 1 1 --- 2 + title: Features | Guide 2 3 outline: deep 3 4 --- 4 5
+4
docs/guide/filtering.md
··· 1 + --- 2 + title: Tests Filtering | Guide 3 + --- 4 + 1 5 # Tests Filtering 2 6 3 7 Filtering, timeouts, concurrent for suite and tests
+4
docs/guide/ide.md
··· 1 + --- 2 + title: IDE Integrations | Guide 3 + --- 4 + 1 5 # IDE Integrations 2 6 3 7 ## VS Code <sup><code>Official</code></sup>
+4
docs/guide/in-source.md
··· 1 + --- 2 + title: In-source testing | Guide 3 + --- 4 + 1 5 # In-source testing 2 6 3 7 Vitest 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
··· 1 + --- 2 + title: Getting Started | Guide 3 + --- 4 + 1 5 # Getting Started 2 6 3 7 ## Overview ··· 103 107 - [cz-git](https://github.com/Zhengqbbb/cz-git) 104 108 105 109 <!-- 106 - For contributors: 110 + For contributors: 107 111 We no longer accept new entries to this list a this moment. 108 112 Thanks for choosing Vitest! 109 113 -->
+4
docs/guide/migration.md
··· 1 + --- 2 + title: Migration Guide | Guide 3 + --- 4 + 1 5 # Migration Guide 2 6 3 7 ## Migrating from Jest
+6 -1
docs/guide/mocking.md
··· 1 + --- 2 + title: Mocking | Guide 3 + --- 4 + 1 5 # Mocking 6 + 2 7 When 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**). 3 8 4 9 ::: warning ··· 518 523 ```ts 519 524 vi.stubGlobal('__VERSION__', '1.0.0') 520 525 expect(__VERSION__).toBe('1.0.0') 521 - ``` 526 + ```
+4
docs/guide/snapshot.md
··· 1 + --- 2 + title: Snapshot | Guide 3 + --- 4 + 1 5 # Snapshot 2 6 3 7 Snapshot 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
··· 1 + --- 2 + title: Test Context | Guide 3 + --- 4 + 1 5 # Test Context 2 6 3 7 Inspired 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
··· 1 + --- 2 + title: Vitest UI | Guide 3 + --- 4 + 1 5 # Vitest UI 2 6 3 7 Powered 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
··· 1 + --- 2 + title: Using Plugins | Guide 3 + --- 4 + 1 5 # Using Plugins 2 6 3 7 Vitest can be extended using plugins...
+4
docs/guide/why.md
··· 1 + --- 2 + title: Why Vitest | Guide 3 + --- 4 + 1 5 # Why Vitest 2 6 3 7 :::tip NOTE