Continuous Testing for Visual Studio

Continuous Testing for Visual Studio continuously runs your unit tests after each build. This simplifies your TDD workflow by removing the tedious manual step of running tests. It also enforces test running, and reveals regressions as fast as is possible.

Continuous Testing is available for Visual Studio 2008 and Visual Studio 2010.

Continuous Testing for Visual Studio

Error list integration

Continuous Testing integrates fully with Visual Studio, and reports failing tests as errors in the error list, providing an easy way to navigate to the line of code that failed.

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 (NEW!)

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.

Feedback

Feedback is greatly appreciated. If you experience problems with Continuous Testing for Visual Studio, please report the issue through our issue tracker. 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.