Separate Runners for .NET Test Frameworks

Have you already tried multiple runners in latest TeamCity 6.0 EAP builds? If you have, there’s no need to repeat that now you can split the build procedure into steps and add as many build runners to be invoked sequentially as you need, for instance, call a NAnt script before compiling VS solutions. Having this approach implemented, we decided to review existing .NET runners in TeamCity.

As you know, TeamCity provides bundled support of NUnit and MSTest. In previous versions you could configure running such tests within MSBuild and VS.Solution build runners. That was reasonably good and handy solution for everyone to run unit tests without writing a line of script/code. Nevertheless, we removed NUnit and MSTest options from these runners. Don’t worry! You’re not going to miss them. Instead, we’ve introduced separate NUnit and MSTest build runners which you can now add as a build step to your configuration.
Several Build Runners in One Build ConfigurationNUnit Build Runner
If you previously used to run the tests by means of MSBuild and VS.Solution build runners, you probably won’t even notice the difference, because such build configurations will be just split into two build steps during upgrade.

But here goes nice news for those who combined NUnit tests with Rake runner, NAnt, or for some other reason had to pick up some convoluted way to pass test reports to TeamCity, like using TeamCity NUnit launcher from command line, or service messages, or TeamCity addin for NUnit, etc. Now you can forget about all those tricky configurations and relax. Just add one more runner.
Of course, all old approaches will still work, but will remain mostly for exceptional cases.


About Eugene Petrenko

Eugene is a developer advocate at JetBrains, software developer, speaker, and blogger. His interests include software development, distributed systems design, cloud computing, and programming languages. Eugene holds a PhD in computer science; he writes code in Kotlin, Go, Java, C/C++, Kotlin/Native, and JavaScript. A Kotlin fan for years, he started using Kotlin before 1.0 and completed his first production Kotlin app back in 2013. He is known as @jonnyzzz
This entry was posted in Features and tagged , , . Bookmark the permalink.

6 Responses to Separate Runners for .NET Test Frameworks

  1. t800t8 says:

    Will this feature available for next EAP build? I cannot find MSTest and NUnit build runner in build 15400.

  2. eugene.petrenko says:

    It will be included in the next EAP build.

  3. t800t8 says:


    When will the next EAP build available? Thanks.

  4. t800t8 says:


    Do we have separate runners for code coverage?

  5. eugene.petrenko says:

    t800t8 ,
    EAP build with those changes is out!
    We added .NET Code coverage options to NUnit runner. You can switch on code coverage for NUnit, MSBuild and VS.Solution runners.

Comments are closed.