-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Jest test runner #3363
Comments
Adding @octref to have a look at your jest test runner. |
Great, thanks for looking into it! Let me know If the test runner falls short in any way. I'd be happy to make improvements! |
I look forward to your PR. This will help microsoft/vscode-test#23 and microsoft/vscode-test#37 |
Great, I will get started on this. |
@octref - I'm also discussing this package with the Jest team, so can we hold off on merging this to make sure everything is clear? See jestjs/jest#9542. |
@octref - Both PRs are ready for review.
Since that could be a common source of confusion, I've renamed the package to Please let me know if you have any questions. |
Closing until the upstream PRs are merged. We can reopen this PR is Jest support is added to the test runner. |
mocha
is the only documented VS Code test runner for extensions.Would you be willing to accept a PR documenting how to use
jest
as a test runner?I recently released an npm package jest-runner-vscode that simplifies this process, and I'd be happy to open a PR to document this. The package is currently in use by my VS Code extension: shifty.
The text was updated successfully, but these errors were encountered: