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
PITest will currently complain about surviving mutations for functions that are not tested at all. This prohibits to enforce a 100% mutation coverage without tediously excluding untested methods. This is useful as forcing a 100% mutation coverage combined with the outlined feature forces every test to be of the best quality instead of forcing the user to write unit tests for every method which is not the goal and/or usage area of pitest (at least how I see it).
I would need the given flag for the maven plugin at least.
The text was updated successfully, but these errors were encountered:
roookeee
changed the title
Add an override to not track mutations for untested lines
Add an override to not track mutations for untested lines/functions
Jun 21, 2019
roookeee
changed the title
Add an override to not track mutations for untested lines/functions
Add an override to not track mutations for untested functions
Jun 21, 2019
As I read it its a bit different: I want every tested line to a have at least the given mutation coverage. Lines that are not covered at all by any test should not be included which is the case at the moment. I can only achieve 80% mutation coverage if I have only tested 80% of my application which is a bit misleading
PITest will currently complain about surviving mutations for functions that are not tested at all. This prohibits to enforce a 100% mutation coverage without tediously excluding untested methods. This is useful as forcing a 100% mutation coverage combined with the outlined feature forces every test to be of the best quality instead of forcing the user to write unit tests for every method which is not the goal and/or usage area of pitest (at least how I see it).
I would need the given flag for the maven plugin at least.
The text was updated successfully, but these errors were encountered: