Notes on Heckle
drbrain |
When I started heckle I was hoping for somehing better than rcov that would tell you that your code is poorly tested… But code so poorly engineered that changing anything as bound to make everything fall apart looks like well tested (read: heckle-proof) code in a sense. We both think that running just the unit tests that directly test the MUT (method under test) would help, but really it wouldn’t help enough. […]
Suggestions? How would you differentiate between “well tested” and “tightly coupled crap”?
—Notes on Heckle via Polishing Ruby
I’m puzzled by this too. How can we detect well-tested vs tightly-coupled (and poorly tested) code automatically?
comment
Comments are disabled
