-
Notifications
You must be signed in to change notification settings - Fork 182
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
Mutate expression bodied methods to empty body #2798
Comments
This issue might be a duplicate of #134 (sorry I only checked for opened issues). I will read in detail its content 👀 |
From what I understood, ternary operators are properly handled thanks to #17 (which #134 is marked duplicate of, not sure why because issues were not exactly the same even though kinda related). I can provide more information if necessary, or even a simple project with both syntaxes 🙏 |
Yes, can you please provide more explicit expectations and/or source code/samples? That would help us provide more accurate answer.
Hope this helps. |
Thanks for the feedback ! I'm preparing a sample 👍 |
I can reproduce this issue even with a simple Have a great day 😁 |
Describe the bug
No statement removal mutant is being generated for expression-bodied methods (
=> [...]
instead of{ [...] }
)Logs
expression-body.zip
statement-body.zip
Expected behavior
I was expecting both method syntaxes to behave similarly for mutant detection/generation.
We use this expression-bodied syntax a lot for one-liner (props, methods, etc.) so this bug (or feature?) is quite important for us.
The workaround would be to force statement body everywhere in our solution, or at least for project under tests.
Desktop (please complete the following information):
Additional context
Love mutation testing, love the tool, kudos !
The text was updated successfully, but these errors were encountered: