Save Some Time With The Right Testrunner

3 commentsWritten on July 1st, 2009 by
Categories: testing

If you're running your tests multiple times throughout the day, it's in your best interest to keep those testruns as fast as possible. We have a solution with 2 test projects. The first testproject contains 2700 regular tests that don't use any external resources so they should be very fast. The second testproject contains 1200 database tests (you do write tests for your queries, right?) which is a little bit slower, as is to be expected.

The problem is that with Resharper's testrunner, running the database tests actually takes less time than running the 'fast' tests. The 1200 database tests take 1m14 seconds to run. The 2700 in memory tests take 1m20 seconds to run... so that's almost 3 minutes of waiting time whenever you run the entire testsuite.

Just out of curiosity, i ran all of the tests with TestDriven.NET to see how much faster it would be... The 1200 database tests only took about 45 seconds, and the 2700 in memory tests only took 28 seconds to run. Running the entire testsuite with TestDriven.NET actually takes less than half the time it takes with Resharper's testrunner...

« Avoid Using NHibernate With NUnit 2.4.6Protecting Your Application From Remote Problems »

This entry was posted on Wednesday, July 1st, 2009 at 10:04 and is filed under testing. You can subscribe to any comments to this entry via RSS 2.0. You can leave a response, or trackback from your own site.

  • Pingback: Arjan’s World » LINKBLOG for July 1, 2009

  • Keivn Dan

    Yes, I have the same experience. Resharper TestRunner would run out of memory with large testing sets, while TestDriven.Net is not. Don’t get me wrong, Resharper is one of the best development tools. It’s good for TDD development as well with TestRunner. But for serious unit testing running, TestDriven.Net is better.

  • http://randomcode.net.nz Neal Blomfield

    Having spent some time recently trying to get the xunit resharper test runner working for custom test class commands (indicated via the RunWith attribute), I can understand how R# can be a slow test runner. If you are curious about what goes on, check out the xUnit contrib site on codeplex.

Meta

Recent Posts

Categories