http://glu.ttono.us/articles/2006/08/30/mocks-for-speed en-us 40 <p>I&#8217;m starting to come around on the subject of using mock objects as opposed to just letting the code run. Here&#8217;s why:</p> <div class="typocode"><pre><code class="typocode_default ">Loaded suite UnitTests Started ..................................................... ..................................................... ..................................................... ..................................................... Finished in 0.070892 seconds. 212 tests, 250 assertions, 0 failures, 0 errors Loaded suite IntegrationTests Started ................... Finished in 0.046002 seconds. 19 tests, 24 assertions, 0 failures, 0 errors Loaded suite AcceptanceTests Started ............... Finished in 0.007645 seconds.</code></pre></div> <p>This is from the tests that are bundled with <a href="http://mocha.rubyforge.com">Mocha</a>, a mocking library. </p> <p>Look at those numbers! Look at just the unit tests. 212 tests, 250 assertions, 0.070892 seconds. Hot damn. Imagine your Rails tests running like that.</p> Wed, 30 Aug 2006 15:36:00 -0400 urn:uuid:c060d880-7688-40bf-9722-57c20ba82dd9 kev http://glu.ttono.us/articles/2006/08/30/mocks-for-speed Ruby testing