Top AI Repos — open-source AI, indexed and scored
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
VS Code extension for Vitest
| Date | Stars |
|---|---|
| 2026-07-24 | 919 |
| 2026-07-25 | 919 |
| 2026-07-28 | 919 |
| 2026-07-30 | 919 |
| 2026-08-06 | 919 |
Today
— stars today
This week
— stars this week
This month
— stars this month
Momentum
35.0
growth rate 0.00%/day
<p align="center">
<a title="Learn more about Vitest extension for Visual Studio Code" href="https://github.com/vitest-dev/vscode">
<picture>
<source media="(prefers-color-scheme: dark)" srcset="./img/cover-light.png">
<source media="(prefers-color-scheme: light)" srcset="./img/cover-dark.png">
<img alt="Vitest extension for Visual Studio Code logo" width="50%" src="./img/cover-dark.png">
</picture></a>
</p>
<h1 align="center">Vitest extension for Visual Studio Code. Available on <a href="https://marketplace.visualstudio.com/items?itemName=vitest.explorer">Visual Studio Marketplace</a>.</h1>
## Features
- **Run**, **debug**, and **watch** Vitest tests in Visual Studio Code.
- **Coverage** support
- **Inline console.log display**: Console logs appear inline in the editor next to the code that produced them
- **Imports duration**: Displays the execution time for each import during continuous test runs.
## Requirements
- Visual Studio Code version >= 1.77.0
- Vitest version >= v1.4.0
- Node.js version >= 18.0.0 (follows Vitest)
- Coverage requires Visual Studio Code >= 1.88.0
## Usage
You can manage tests both from the Testing view and directly within your test files.
Vitest uses vscode's `TestController` API to provide a unified testing experience. You can read the official guide on how to run tests in the [VSCode Documentation](https://code.visualstudio.com/docs/editor/testing).
### In the Testing View
You can access the extension from the Testing view in the Visual Studio Code sidebar.
The toolbar at the top provides various commands to manage test execution:
- **Refresh Tests**: To reload your test suite, reflecting any new changes.
- **Run All Tests**: To start testing all cases that are currently visible.
- **Debug Tests**: To begin a debugging session for the tests.
- **Run Tests with Coverage**: To start testing all cases that are currently visible, while also collecting code coverage information.
- **Continuous Run/Stop Continuous Run**: To toggle the watch mode for running tests on file changes.
- **Show Output**: To display detailed logs from test executions.
- **Miscellaneous Settings**: To customize the Testing view, such as sorting and grouping tests.
> 💡 Hovering, or right clicking a folder, test file, test suite, or a test will reveal more actions.
The filter bar allows you to narrow down the tests displayed, focusing on specific tests by name, exclusion patterns, or tags.
Icons next to each test indicate their status—passed (checkmark), failed (cross), skipped (arrow), queued (yellow icon), or not executed (dot).
### In the Test File
When viewing a test file, you'll notice test icons in the gutter next to each test case:
- **Run a Single Test:** Click the test icon next to a test case to run that specific test.
- **More Options:** Right-click the test icon to open a context menu with additional options:
- `Run Test`: Execute the selected test case.
- `Debug Test`: Start a debugging session for the selected test case.
- `Run with coverage`: Execute the selected test case while also collecting code coverage information.
- `Reveal in Test Explorer`: Locate and highlight the test in the centralized Testing view.
- `Breakpoint Settings`: Set breakpoints to pause execution during debugging. You can add a standard breakpoint, a conditional breakpoint, a logpoint, or a triggered breakpoint.
## Configuration
You can identify if your config is loaded by the extension with `process.env.VITEST_VSCODE` and change the configuration accordingly.
### Workspace Configurations
These options are resolved relative to the [workspace file](https://code.visualstudio.com/docs/editor/workspaces#_multiroot-workspaces) if there is one. If you have a single folder open in Visual Studio Code, paths will be resolved relative to that folder. If there are multExcerpt of 13,091 characters
Read on GitHubWould you bet a product on this? Bounded 0–100 and slow moving.
matched fp:cd3e62e10a2cd2f5, topic:testing
