| Actually this is a really good talking point that's often the start of many interesting "discussions": Namely, what happens when you're done with the test-code-repeat cycle for a system under test and you want to make it more architecturally sound / OO / etc. You typically might end up doing a refactor in which you extract classes from the original system under test and colocating common functionality into new class(es). In this way you still have the same coverage as before... But you're actually testing multiple classes as a unit. Some folks would argue you need to split the tests out. Otherwise would say "the coverage is there, what's the point?". Unless I need to do something, I'm not going to do it. In playing with pitest, it looks like the refactorings might introduce some fuzzing that needs to be considered in the original (and refactored) SUT depending on how much conditional logic you're moving around. Arghh. There goes my evening. Will be playing with this after work now :) |