-
Notifications
You must be signed in to change notification settings - Fork 57
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
Excluded Mutation Operators Still Getting Run #522
Comments
This features doesn't work right now. See #517. |
@abingham Out of curiosity, how closely related are these two issues? Because if resolving one won't automatically resolve the other, perhaps this needs to be its own issue. Thanks! |
Ah, you're right, sorry for not reading closely enough. I'll look into this. |
The problem has to do with a mistake in how the filter operator is implemented. The
It is required. Cosmic Ray doesn't run any filters on its own, and requires users to run them externally. We used to try to manage all of the filtering internally, and - while it's definitely technically possible - it was more trouble than it was worth. |
@abingham Also, thanks for the workaround while we wait for this issue to get resolved. 🙂 |
Correct. CR used to run certain kinds of filtering as part of the init phase, and it would read the filtering criteria from the config in the same way that e.g. |
This should be fixed in 8.3.3. |
@abingham
Just to make it more uniform with |
I have excluded the following mutation operators in my Cosmic Ray configuration file:
I also reran
init
before running mutation tests.However, when I ran an HTML report, the mutation operators were still getting run:
NOTE: I tried a second time, this time running
cr-filter-operators mutation_test_session.sqlite
(which I assume isn't needed because the configuration file already has all the filters) after runninginit
and it didn't solve the problem.The text was updated successfully, but these errors were encountered: