feat: add experimental runner cli #235
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The context behind this is wanting a standard way to run VS Code tests, with which we can build an extension that shows VS Code tests in the test explorer. This does that. The previous APIs are there and will always be supported as an alternative way to run tests. See the readme for usage. Integration in js-debug for "debugging" is not there yet, but it will come.
Closed
|
Some feedback I have:
|
|
|
Could this be done in a separate node module that uses |
|
That could work, particularly if that "agnostic" CLI works with test-web later as well. |
|
And then electron-test and web-test would be both optional peer dependencies of it? |
|
Yep |
|
Going to close and reopen this in a new repo as Martin suggested. |
connor4312
added a commit
to microsoft/vscode-test-cli
that referenced
this pull request
Oct 11, 2023
This creates a `@vscode/test-cli` NPM module that exposes a `vscode-test` command line. This reads a configuration file, described in the readme, and runs all tests defined therein by default. Multiple configurations can be defined, in which case they are all run sequentially. See previous discussion on microsoft/vscode-test#235 This is largely the same as the version in that PR, with the addition of a reporter and addressed comments.
|
Now in microsoft/vscode-test-cli#1 I also have the extension to integrate in VS Code ready to go, which I'll share after the CLI gets published 🙂 |
connor4312
added a commit
to microsoft/vscode-test-cli
that referenced
this pull request
Oct 11, 2023
This creates a `@vscode/test-cli` NPM module that exposes a `vscode-test` command line. This reads a configuration file, described in the readme, and runs all tests defined therein by default. Multiple configurations can be defined, in which case they are all run sequentially. See previous discussion on microsoft/vscode-test#235 This is largely the same as the version in that PR, with the addition of a reporter and addressed comments.
|
Extension to run tests in VS Code 👉 https://github.com/microsoft/vscode-extension-test-runner |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The context behind this is wanting a standard way to run VS Code tests, with which we can build an extension that shows VS Code tests in the test explorer. This does that. The previous APIs are there and will always be supported as an alternative way to run tests.
See the readme for usage. Integration in js-debug for "debugging" is not there yet, but it will come.