@jbackus3 Seeing every place the test suite allows old code to change is powerful. Each mutation = potential bug you wouldn't catch
-
-
Replying to @mifreewil
@mifreewil I think with time it results in you writing better code and tests, so there isn't much additional work1 reply 0 retweets 0 likes -
-
Replying to @mifreewil
@mifreewil Well it depends. Usually I have to write tests that weren't there and should be.2 replies 0 retweets 0 likes -
Replying to @backus
@jbackus3@mifreewil For legacy code you can before refactoring kill all mutations via tests / code reduction.1 reply 0 retweets 2 likes -
Replying to @_m_b_j_
@jbackus3@mifreewil If all tests go through a mostly unaltered public API you can than use them as refactoring-anchor.1 reply 0 retweets 2 likes -
Replying to @_m_b_j_
@_m_b_j_@mifreewil mbj beat me to this point. IMO big productivity drop means either technical debt, bad tests, or not caring about quality1 reply 0 retweets 1 like
@_m_b_j_ @mifreewil Note mutant allows you to say "only test code that change since [COMMIT]." This means debt doesn't affect unrelated code
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.