Continuous Testing for Visual Studio

Continuous Testing for Visual Studio simplifies your TDD workflow by removing the tedious manual step of running tests. Features like Smart Test Run Prioritization enable you to get as immediate feedback as possible.

Continuous Testing 2.0 Buy Professional Download for VS2010 Download for VS 2008

Features

Continuous Testing runs your unit tests automatically after each build, removing a manual step from your TDD workflow.

It integrates test results into the Visual Studio error list, allowing you to conveniently navigate to the line of code that caused a particular test to fail.

Continuous Testing works with MSTest, NUnit, and XUnit.

Professional Features

Smart Test Run Prioritization orders your test so that you are given feedback as immediately as possible, by tracking your test runs and prioritizing the most recently failing tests and most often failing tests first.

You can tell Continuous Testing to abort a test run as soon as a test has failed, drastically speeding up your workflow for large and/or resource intensive test sets. This simple option makes a huge difference in real world, day to day work.

Getting started

After installing Continuous Testing, your tests will run automatically after each successful build. Any failing tests will show up as errors in your error list. Our introductory screencast demonstrates a build cycle with Continuous Testing when a test fails.

As seen in the screencast, Continuous Testing integrates fully with Visual Studio, and the error list provides a conventional and easy way to navigate to the line of code that caused the test to fail.

Error List with errors from Continuous Testing

Supported versions and test frameworks

Continuous Testing currently supports the following test frameworks:

  • MSTest (Microsoft Test Framework) 9.0 and 10.0 (VS 2008 and VS 2010)
  • NUnit v2.5 or later
  • XUnit v1.5 or later

Continuous Testing currently supports the following versions of Visual Studio (click to download):

Settings

Settings for Continuous Testing can be altered through the Tools > Options > Test Tools > Continuous Testing dialog:

Continuous Testing Dialog

  • Paths to the test runners used by Continuous Testing can be altered through this dialog. If you encounter problems running tests, verify that the paths to the executables used by Continuous Testing are correct. The default paths are auto-detected on first run.
  • Execution timeout can be altered. Try increasing the timeout if Continuous Testing fails to complete test runs.
  • Continuous Testing can be disabled by unchecking the “Run unit tests on successful build” check box.
  • Tracing can be enabled by checking the “Test run trace file” check box and providing a writable path to a trace file. You should trace your runs if you experience problems and want to debug and/or report them.

Support, feedback and bug reports

Professional users receive priority support and will be responded to within 24 hours. Please provide your registered user name when contacting us for priority support.

If you experience problems with Continuous Testing for Visual Studio, please report the issue by e-mailing continuoustesting at this domain. Please include the following:

  • A detailed description of the circumstances under which the error or problem occured
  • Preferably a sample solution which reproduces the problem on your machine
  • Installation date, Visual Studio version, and other relevant details
  • A trace file from the test run

You can also follow @ContinuousTest and @havardstranden on Twitter and make contact there.