-
Notifications
You must be signed in to change notification settings - Fork 145
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
Regression in jasmine 5: settings bleed over to next Jasmine
instance
#207
Comments
Can you try the npm-multiple-runs branch e.g. |
💚 Seems to work: stryker-mutator/stryker-js#4190 |
TY. I'll try to get that released later this week. |
This is released in 5.0.1. Note that the bug is still present if you do |
Since Jasmine 5, settings seem to bleed over in the next
Jasmine
instance. See this example:Expected:
Actual:
See reproduction repo:
jasmine-issue.zip
node run-jasmine.js
reproduces it.Downgrading jasmine fixes the issue:
Background info: StrykerJS relies on the jasmine API to run mutation testing. Although we generally only create 1 instance of jasmine, we still want to rely in settings not bleeding over to the next instance.
The text was updated successfully, but these errors were encountered: