Documentation¶
Everything about Jest Runner for VS Code in detail: how to install and use it, what it reads from each test framework, every setting, and how the extension works inside. The short overview is the README on GitHub. Also as a website with search: https://firsttris.github.io/vscode-jest-runner/

User Guide¶
| Getting Started | Install, open a project, run your first test, enable the Test Explorer |
| Running & Debugging Tests | CodeLens, Test Explorer, context menus, commands, keyboard shortcuts, watch mode, snapshots, coverage |
| Supported Test Frameworks | Jest, Vitest, Playwright, Rstest, Bun, Deno, Node.js: how each is detected, which config options are read, how coverage and debugging work |
| Settings Reference | Every jestrunner.* setting with defaults and examples |
| Recipes | Create React App, nvm, ESM, monorepos, several configs, Windows shells, custom commands |
| Troubleshooting & FAQ | Tests not found, wrong framework, debug logs, known limits of the config parser |
Internals¶
| Architecture | The big picture: three entry points, the detection pipeline, command building, process execution, result matching |
| Test Detection | How a file is classified as a test of one framework, the caches, config path resolution |
| Config File Parsing | The static AST parser for jest.config.*, vitest.config.*, playwright.config.*, rstest.config.*, deno.json |
| Test File Parsing | How describe, it, test, it.each and Deno.test become a test tree with positions |
| Command Building & Execution | Framework adapters, argument strategies, the terminal path, the spawn path, Windows handling |
| Reporters & Result Matching | The structured output protocol, the injected reporters, JSON, JUnit and TAP fallbacks, matching results to test items |
| Test Explorer | Discovery, the test item tree, file and config watchers, run profiles |
| Debugging | How the debug configuration is assembled for each framework |
| Coverage | Istanbul JSON and LCOV, coverage directory detection, mapping to the VS Code coverage API |
| Module Reference | Every source file in one table: what it does and who uses it |
| Development & Release | Build, test, lint, debug the extension, CI, release process, project conventions |