-
Notifications
You must be signed in to change notification settings - Fork 175
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
Ability to disable mutant, that end up with timeout #2905
Comments
We wouldn't know it's a timeout until after testing, so how can we disable the mutant from testing? Instead of disable all you can specify the type of mutator to disable here. |
i would interpret |
This is not true, timeouts are counted as killed when calculating the mutation score. So why would you want to exclude timeouts from the report?
How would any mutant be generated here? Maybe I'm not following correctly. |
@CzBuCHi : what is exactly the problem you are trying to solve here? |
probably my own confusion ( after reading @richardwerkman answer ) - i considered timeouts as bad & need to be fixed (its not green :/) but i think this can still be applied to uncovered parts of code:
because in this case stryker will complain about uncovered parts of code ... (idk right now it that one is red or yellow) |
Stryker comments can be used for uncovered parts of the code, so this is already possible. |
Is your feature request related to a problem? Please describe.
I have this code:
when stryker removes
list.RemoveAt(0);
it will result in surviving mutant due to timeout ...Describe the solution you'd like
Ability to use 'timeout' keyword when disabling mutators via comments:
Describe alternatives you've considered
im currently using
// Stryker disable once all
but that feels wrong because some mutant may still squeeze in there ...Additional context
Same thing applies to uncovered parts of code:
The text was updated successfully, but these errors were encountered: