vscode-test-explorer
Advanced tools
This extension provides an extensible user interface for running your tests in VS Code. It can be used with any testing framework if there is a corresponding Test Adapter extension.
Other extensions can get full access to the Test Adapters by acting as Test Controllers.
The Test Explorer can also be used in VS Live Share sessions by installing the Test Explorer Live Share extension.
This extension will be automatically installed when you install one of the Test Adapters, so there is usually no need to install this extension manually.
In version 1.59, VS Code added an official API and UI for running tests, which provides all the functionality of this extension and more. Therefore this extension is now deprecated. I will keep maintaining it so it will remain usable but I don't plan to add any major new features to it.
You can keep using this extension as before, but you now also have the option to use VS Code's native testing UI
instead by setting testExplorer.useNativeTesting to true in your VS Code settings.
If you plan to write a new testing extension for VS Code, I recommend you use the native testing API as it's more flexible and has more features than this extension's Test Adapter API. Here's the official guide for the native testing API.
If you're maintaining an extension that uses the Test Adapter API, here is a short guide how to migrate your Test Adapter to the native API.
The migration isn't strictly necessary because this extension will remain usable and your users can switch to the native testing UI using the
testExplorer.useNativeTesting setting anyway, but you might find the additional flexibility of the native testing API useful in the future.
Currently the following Test Adapters are available:
If there is no Test Adapter for your favorite testing framework yet, you can easily create your own.
Currently the following Test Controllers are available:
Do you have a new idea for interacting with the Test Adapters? You can easily get full access to all Test Adapters in your own extension by implementing your own controller.
The following configuration properties are available:
| Property | Description |
|---|---|
testExplorer.onStart | Retire or reset all test states whenever a test run is started |
testExplorer.onReload | Retire or reset all test states whenever the test tree is reloaded |
testExplorer.codeLens | Show a CodeLens above each test or suite for running or debugging the tests |
testExplorer.gutterDecoration | Show the state of each test in the editor using Gutter Decorations |
testExplorer.errorDecoration | Show error messages from test failures as decorations in the editor |
testExplorer.errorDecorationHover | Provide hover messages for the error decorations in the editor |
testExplorer.sort | Sort the tests and suites by label or location. If this is not set (or set to null), they will be shown in the order that they were received from the adapter |
testExplorer.showCollapseButton | Show a button for collapsing the nodes of the test tree |
testExplorer.showExpandButton | Show a button for expanding the top nodes of the test tree, recursively for the given number of levels |
testExplorer.showOnRun | Switch to the Test Explorer view whenever a test run is started |
testExplorer.addToEditorContextMenu | Add menu items for running and debugging the tests in the current file to the editor context menu |
testExplorer.mergeSuites | Merge suites with the same label and parent |
testExplorer.hideEmptyLog | Hide the output channel used to show a test's log when the user clicks on a test whose log is empty |
testExplorer.hideWhen | Hide the Test Explorer when no test adapters have been registered or when no tests have been found by the registered adapters. The default is to never hide the Test Explorer (some test adapters only work with this default setting). |
testExplorer.useNativeTesting | Disable the Test Explorer UI and use VSCode's native Testing UI instead |
Further configuration options are provided by the Test Adapters.
The following commands are available in VS Code's command palette, use the ID to add them to your keyboard shortcuts:
| ID | Command |
|---|---|
test-explorer.reload | Reload tests |
test-explorer.run-all | Run all tests |
test-explorer.run-file | Run tests in current file |
test-explorer.run-test-at-cursor | Run the test at the current cursor position |
test-explorer.rerun | Repeat the last test run |
test-explorer.debug-test-at-cursor | Debug the test at the current cursor position |
test-explorer.redebug | Repeat the last test run in the debugger |
test-explorer.cancel | Cancel running tests |
FAQs
Run your tests in the Sidebar of Visual Studio Code
We found that vscode-test-explorer demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.
Security News
Axios compromise traced to social engineering, showing how attacks on maintainers can bypass controls and expose the broader software supply chain.
Security News
Node.js has paused its bug bounty program after funding ended, removing payouts for vulnerability reports but keeping its security process unchanged.
