-
Notifications
You must be signed in to change notification settings - Fork 45
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
Support jest-circus #2575
Comments
Right now Wallaby doesn't support jest-circus with manual config, having said that Wallaby automatic configuration for your project should just work. Automatic configuration is how we recommend to run Jest with Wallaby. Internally automatic configuration will use jest-jasmine2, but once we add integration with jest-circus, it'll be using it when required, without you having to do anything. Anyway, the internal test runner should not affect how Jest/Wallaby runs your tests and using jest-jasmine2 should be perfectly fine (and to provide the same results as jest-circus). Is there any specific reason you want to use specifically jest-circus with Wallaby? |
Thanks. Jest-circus will be a default test runner in the next major version jestjs/jest#6295. Also, jest-jasmine2 has some goofy issues with test setup so I have been exploring jest-circus (jestjs/jest#6527). I will continue using jest-jasmine2. It is possible to configure jest with a custom test runner so maybe I can suggest reporting an more descriptive error when a custom test runner is used? |
Thanks for your response.
Wallaby automatic configuration for your project should just work even you configure |
We have now added support for jest-circus runner. |
Issue description or question
I'm trying to use the jest-circus test runner but I receive an error. Wallaby is referencing jasmine which does not exist.
I have created a sample repo.
Wallaby diagnostics report
The text was updated successfully, but these errors were encountered: