http://blog.segment7.net/articles/2007/02/12/notes-on-heckle en-us 40 The Blog <blockquote cite="http://blog.zenspider.com/archives/2007/02/notes_on_heckle.html">When I started heckle I was hoping for somehing better than rcov that would tell you that your code is poorly tested&#8230; 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 <span class="caps">MUT</span> (method under test) would help, but really it wouldn&#8217;t help enough. [...] <p>Suggestions? How would you differentiate between &#8220;well tested&#8221; and &#8220;tightly coupled crap&#8221;?</blockquote></p> <p style="text-align: right">&mdash;<a href="http://blog.zenspider.com/archives/2007/02/notes_on_heckle.html">Notes on Heckle</a> via <a href="http://blog.zenspider.com/">Polishing Ruby</a> <p>I&#8217;m puzzled by this too. How can we detect well-tested vs tightly-coupled (and poorly tested) code automatically?</p> Mon, 12 Feb 2007 14:32:17 -0800 urn:uuid:52a8718c-bd43-418b-b0c8-6d16a44f963b drbrain@segment7.net (Eric Hodel) http://blog.segment7.net/articles/2007/02/12/notes-on-heckle Testing