Turning a class library project into a MSTest project (or using MBUnit, MSTest and other frameworks in one project)

I know it’s been a while. I’ve been busy talking about SyncFramework at the VSOne conference, helping a bit of at the Sync Framework forums and lot’s of studying going on. I promise I have some new longer posts coming soon.

Yesterday I wrote a unit test that I wanted other members on my team to execute this week to check for some problems. Where’s the problem you may ask? Well I personally like TestDriven.net and MBUnit whereas my colleagues rely on the testing suite in Team System. Fair enough, usually we don’t exchange that many tests (and no – I’m sorry about that myself actually – we don’t have continuous integration. But even if we did that probably wouldn’t be a major problem).

Anyhow I created my class library project and wrote my test. Worked great on my computer (don’t hit me for saying that). I then remembered that it needed to run under MSTest on the other dev machines. Fair enough, can’t be that hard. I referenced


and gave my methods additional attributes. (The top ones are MSTest, the bottom ones are MBUnit.)

public class EvaluatorTestSuite 

public void SetUp() 

public void TearDown() 

public void Evaluate_ValidEvaluationModel_ReturnsValidEvaluationResult()

Then I went to the Test menu in Team System and wanted to execute all tests in this solution. But VS told me there aren’t any. Basically I figured out the test projects must have some special attribute that make them “testable”. They are basically just class libraries but they have a special Guid in their project file. Not quite sure why Microsoft would do that, seeing as they could just check for the attributes on the classes like TestDriven.net does, but ok. This is a quick solution to turning a class library into a MSTest testable project. Open the CSproj file of the class library project and just before the first propertygroup closes insert the following line:





Those two guids make it MSTest testable. And no, I didn’t have time to figure out why there are two and what they do exactly. If anybody cares to explain, I would love to hear about it. The file should look something like this:

<?xml version="1.0" encoding="utf-8"?>
<Project ToolsVersion="3.5" DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
    <Configuration Condition=" '$(Configuration)' == '' ">Debug</Configuration>
    <Platform Condition=" '$(Platform)' == '' ">AnyCPU</Platform>
Technorati Tags: ,,

5 thoughts on “Turning a class library project into a MSTest project (or using MBUnit, MSTest and other frameworks in one project)

  1. Thank you! I was just wondering why I could not make to run a unit test in one my class library project!!


  2. I know this is nearly a year late, but, these are what the two different ProjectTypeGuid’s mean

    {3AC096D0-A1C2-E12C-1390-A8335801FDAB} means: This is a Test Project

    {FAE04EC0-301F-11D3-BF4B-00C04F79EFBC} means: This is a Windows Forms C# Project

  3. Maybe with VS2011 it will be possible to change the ‘output type’ from ‘Class Library’ to f.i. ‘MbUnit V3 Test Project’ in the Project/Properties/Application tab?

  4. Thumbs up, straight to the point – sorted me out straight away. Still don’t know why it doesn’t just pick they keywords up or have something in the ‘settings’ or ‘build’ windows.

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.