test: migrate jest-runner-vscode to @vscode/test-cli
#580
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
ybiquitous
force-pushed
the
migrate-jest-runner-vscode-to-vscode-test-cli
branch
from
c0bc000 to
bfbf8c8
Compare
ybiquitous
changed the title
jest-runner-vscode to @vscode/test-clijest-runner-vscode to @vscode/test-cli
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.
Related to #504
jest-runner-vscodehas been inactive for a long time, while@vscode/test-cliis officially maintained by the VS Code team.See also https://code.visualstudio.com/api/working-with-extensions/testing-extension
Additionally, Mocha.js's BDD style, which is the basis of
@vscode/test-cli, is similar to Jest, so I believe the learning cost is low.