Repository navigation
Monorepos and mixed frameworks
In one line: each test project in the window is found on its own (packages of a monorepo, folders of a multi-root workspace, Python services), and a project that uses two frameworks runs each test file with the right one.
| Who it is for | Teams with several packages or services, or a project moving from Jest to Vitest, or a JS front end next to Python |
| Frameworks | Jest, Vitest and pytest, in any combination; Angular workspaces (one project each, its apps and libraries inside) |
| Requirements | Monorepos and mixed frameworks: requirements |
| How it is built | Monorepos and mixed frameworks: design |
Real repositories are rarely one project with one framework. A monorepo has a package per team, each with its own config. A migration leaves Jest and Vitest side by side. A front end lives next to a Python API. Most test tools assume one root and one framework.
When you open the window, every test project is detected. None runs until you start it.
| Your layout | Projects |
|---|---|
A folder with its own test config (jest.config.*, vitest.config.*, package.json#jest, Create React App) |
One project; its config already covers its packages |
A monorepo root (pnpm-workspace.yaml, package.json#workspaces) without a test config |
One project per package that has tests |
A folder that configures pytest (pytest.ini, [tool.pytest.ini_options], a root conftest.py…) |
One project |
| A uv workspace without a pytest config at its root | One project per member that has tests, each using the workspace's shared .venv
|
Python services side by side, each with its own .venv
|
One project per service, each with its own environment |
A JS folder with a Python subfolder that configures pytest (backend/) |
Two projects |
| A multi-root workspace | Each folder by the rules above |
-
The project switcher at the top of the sidebar (
web ▾ ● running ✓120 ✗2) picks which project the tree, Results panel and status bar show. -
The editor always shows a file's own project. Open a file from another package and you see its results, and
▶ Runruns it there. - Start and Stop act on the project shown. Others keep running, and rerunning on save, in the background.
- How many run at once: 2 by default, or 1 on smaller machines (4 cores or fewer, or under 8 GB of memory). Starting one more asks you to stop one first.
A project with a Jest config and its own vitest.config.* (a migration in progress) runs each test file with exactly one framework, chosen in this order:
- The
liveTestRunner.frameworkssetting, for example{ "packages/new/**": "vitest" }. - The configs: if only one framework's config lists the file, that one.
- The file: an import from
vitestor avi.call means Vitest;@jest/globalsor ajest.call means Jest. - Otherwise the main framework (Jest), with one log line naming the setting.
An Angular workspace (angular.json) is one project: each of its apps and libraries runs with ng test <name>, and the sidebar groups the files by them.
A JS project that also configures pytest runs .py tests with pytest and the rest with Jest or Vitest. The sidebar groups files by framework, and the status bar splits the counts (Jest 12 · pytest 30).
A pnpm monorepo has web (Vitest), api (Jest) and services/billing (pytest). The switcher lists three projects. You start web and billing. Saving a file in web reruns web's tests only, and billing is untouched.
| Setting | Default | What it does |
|---|---|---|
liveTestRunner.maxRunningProjects |
auto |
How many projects can run at once (a number, or auto) |
liveTestRunner.projectRoot |
"" |
Pin the window to one folder (also Select Project Root) |
liveTestRunner.frameworks |
{} |
Glob → "jest" / "vitest": which framework runs those test files |
liveTestRunner.pythonPath |
"" |
The Python that runs pytest. Empty: the one you picked, else the project's own environment |
- A
vitestdependency or avite.config.*alone doesn't make a Jest project mixed. It needs a Vitest config of its own, or the setting. - The Python environment is found without activating anything: the project's
.venv/venv, its poetry or pipenv environment, or the Python extension's choice. A chip under Start shows which one runs, and clicking it picks another.
Source: docs/features/projects.md. This Wiki is generated from the repository; to change a page, open a pull request that edits its file in docs/.
Features
- Test runs
- Test Explorer and editor
- On-save reruns
- Results panel
- Coverage
- Debugging
- Monorepos and mixed frameworks
- AI assistants
Requirements
- Project-wide requirements
- Test runs: requirements
- Test Explorer and editor: requirements
- On-save reruns: requirements
- Results panel: requirements
- Coverage: requirements
- Debugging: requirements
- Monorepos and mixed frameworks: requirements
- AI assistants: requirements
Development
- Developer Guide
- Architecture
- Framework feature matrix
- AI context
- Feature designs
Generated from docs/. Edits made here are overwritten: change a page with a pull request.