You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
As pointed out in #3812 it would be cool if we could get a suggestion if an unused directive with a unknown Mutator has a close match to an existing Mutator.
Describe the solution you'd like
Let's keep the same example as in the original issue.
Perhaps we can check if the unknown Mutator partly matches with an existing one and/or implement some sort of fuzziness when typo's are made. This way we can create suggestions for the user, instead of just warning them what directives where not used.
Example for the CLI:
[Ignored] Equality
sum.js:2:1
- // Stryker disable next-line Equality: Hard to test+ // Stryker disable next-line EqualityOperator: Hard to test
Or use a ~ and/or make the addition another colour (yellow e.g.), since we are not entirely sure this suggestion is correct.
This way the HTML view, and other reporters, can also benefit from this and show the same suggestions. You might even be able to share code between mutation-testing-elements (or mutation-testing-metrics) and Stryker.
Html could show something like this when you click on the ignored mutator:
(I've just edited the HTML on a local page for example purposes)
I'm sorry for the misunderstanding, but I thought it would be cool to enable bg coloring for mutant diffs, the way the HTML report does it. I did some experiments, and this was the best result I got:
Is your feature request related to a problem? Please describe.
As pointed out in #3812 it would be cool if we could get a suggestion if an unused directive with a unknown Mutator has a close match to an existing Mutator.
Describe the solution you'd like
Let's keep the same example as in the original issue.
Perhaps we can check if the unknown Mutator partly matches with an existing one and/or implement some sort of fuzziness when typo's are made. This way we can create suggestions for the user, instead of just warning them what directives where not used.
Example for the CLI:
Or use a
~
and/or make the addition another colour (yellow e.g.), since we are not entirely sure this suggestion is correct.This way the HTML view, and other reporters, can also benefit from this and show the same suggestions. You might even be able to share code between mutation-testing-elements (or mutation-testing-metrics) and Stryker.
Html could show something like this when you click on the ignored mutator:
(I've just edited the HTML on a local page for example purposes)
Describe alternatives you've considered
-
Additional context
Might depend on #3813
The text was updated successfully, but these errors were encountered: