-
Notifications
You must be signed in to change notification settings - Fork 250
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 Mocha 8 #2274
Comments
Hi 👋 @Prophet32j Could you try v3.3 of Stryker? We officially support mocha 8 since 3.3: I'm missing |
I just updated to stryker v3.3.1 and it gives me:
The peer-dependency of mocha-framework indeed still refers to mocha < 8:
While mocha-runner allows mocha < 9:
|
This is what I had, and my tests would not pass any mutations, even though
I know my tests account for them.
|
Ok. I have figured out why my tests would not run. Stryker doesn't like const matchRelationships = require('../../src/er-studio/match-relationships') vs const matchRelationships = require('@src/er-studio/match-relationships') For any tests that would use the aliased module reference, those tests would either time out or all mutants would live. If there's no ability to load aliased modules, there should be some sort of NOTICE on the README to inform developers of that limitation. Either that or I didn't correctly inform Stryker of aliased modules, but I fail to find any documentation on that. |
Yeah, module aliassing does not play nice with Stryker. Allowing Stryker to mutate your code in-place will solve this issue, see #2163 .
I'm not an expert on this subject. What is
True, we're missing more extensive documentation, or FAQ for this. Please feel free to add it! I think the stryker-handbook might be the place for this documentation https://github.com/stryker-mutator/stryker-handbook/tree/master/stryker |
I'm trying to get Stryker 4.1.2 running on a limited set of our unit tests. The Terminal output instruments the tests, starts the test run then produces an error that Here is a screenshot from stryker.log: This is my stryker.conf.json: I am able to kick off all our unit tests using I'm pretty new to this kind of thing so please let me know what other info you need and I'll get it! |
@profplum700 could you please try again with the new |
Thanks for the heads up. I won't be able to test it out as I've moved onto other work but I've made a note of it for the future. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Mocha 8 is since supported. |
Question
Are there plans to support Mocha 8?
I think I have issues with Mocha 8/Stryker 3.2.4 together. My code is well covered with boundaries and conditionals. All mutants survive. Even on module imports being String-literaled. I'm guessing this is a Mocha 8 issue since my other project with Mocha 7 and Stryker 2.5 working.
Stryker environment
Additional context
The text was updated successfully, but these errors were encountered: