Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

docs: add vitest intro to typescript/testing #5336

Open
wants to merge 2 commits into
base: isidorn/testing
Choose a base branch
from
Open

docs: add vitest intro to typescript/testing #5336

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7190649
docs: add vitest intro
zxch3n May 13, 2022
b456ee8
Update typescript-testing.md
zxch3n May 20, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions docs/typescript/images/testing/vitest.gif
View file
Open in desktop
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
7 changes: 6 additions & 1 deletion docs/typescript/typescript-testing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,4 +8,9 @@ Visual Studio Code supports testing TypeScript through it's testing framework. Y

## Jest

## Vitest
## Vitest


[Vitest](https://vitest.dev/) is an ESM-first, modern unit-test framework powered by Vite. It works out of the box for TypeScript/Node.js projects. You can learn how to get started and read about its features in [the Vitest guide](https://vitest.dev/guide/). To enhance your VS Code experience, you can install [the official VS Code extension](https://marketplace.visualstudio.com/items?itemName=ZixuanChen.vitest-explorer).

![A screenshot of using Vitest extension inside VS Code](./images/testing/vitest.gif)
zxch3n marked this conversation as resolved.
Show resolved Hide resolved