-
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
Avoid using "true" condition replacement in "||" statements, and avoid using "false" replacement in "&&" statements #3339
Comments
Could you pinpoint a point in the code where we have access to all mutants on one file for example to see if we could check for those cases ? |
Having all mutants available for one file is too late IMO. You won't have access to the AST anymore, which is what you need. Seeing as all these get created by the same mutator, we should try to simply not make the similar mutants at all. So I would suggest looking at the mutator implementation. Please change the title of this issue, equivalent mutants are something entirely different, see https://stryker-mutator.io/docs/mutation-testing-elements/equivalent-mutants |
Is your feature request related to a problem? Please describe.
I have some code like this :
And there are 3 applied mutants :
I think it would make sense to just run one of the mutants in this case.
The text was updated successfully, but these errors were encountered: