You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please try out the CLI as well as the extension that provides integration into the VS Code UI. If you own an extension, you can adopt it there, or just work from the helloworld-test-sample.
Add some tests, or have some test in an extension
Add a .vscode-test.js file to the workspace as the documentation suggestions (you can also use .cjs or .mjs)
Try the different options available in defineConfiguration, see that they work
Try out the different CLI options (npx @vscode/test-cli --help should work)
Install the extension and make sure it works like you would expect
Note that it operates only on compiled files, so test decorations are not updated until the project is compiled
It should rerun discovery in response to changes in the vscode-test config file
It should show any discovery errors that happen appropriately
Refs: #189680
Complexity: 5
Create Issue
This iteration we worked on a test runner for VS Code extensions. Here is the documentation for it:
https://github.com/microsoft/vscode-docs/blob/vnext/api/working-with-extensions/testing-extension.md#quick-setup-the-test-cli. Please note the samples have not yet been updated; you can add it manually using the documented steps to an existing extension.
Please try out the CLI as well as the extension that provides integration into the VS Code UI. If you own an extension, you can adopt it there, or just work from the helloworld-test-sample.
.vscode-test.js
file to the workspace as the documentation suggestions (you can also use.cjs
or.mjs
)defineConfiguration
, see that they worknpx @vscode/test-cli --help
should work)The text was updated successfully, but these errors were encountered: