-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Improve mutation tests performance by ensuring solution file isn't discovered #2589
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
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2589 +/- ##
=======================================
Coverage 96.23% 96.23%
=======================================
Files 311 311
Lines 7327 7327
Branches 1013 1013
=======================================
Hits 7051 7051
Misses 222 222
Partials 54 54
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
Nice find - feels like a bit of a footgun on the part of Stryker to do that given that it was given a specific project, but 10 minutes less runtime is a definite improvement. |
|
Thanks for your contribution @slang25 - the changes from this pull request have been published as part of version 8.6.0 📦, which is now available from NuGet.org 🚀 |
I was doing some testing locally and I've noticed that what is happening with the Cake build script is that when mutation tests are triggered, because they are launched from the root of the repo, the solution file is automatically detected which causes all tests to run.
This should limit each mutation test to only run the tests from the matching project.