Click here to Skip to main content
65,938 articles
CodeProject is changing. Read more.
Articles / DevOps / testing

xUnit.Net – Running the tests (TestCategory)

0.00/5 (No votes)
29 Jan 2011CPOL 14.4K  
A solution for converting MSTest TestCategory attribute to an equivalent implementation in xUnit.Net

In my previous post, I showed an example about converting an MSTest class to xUnit.Net, and now I want to provide a solution for converting the MSTest TestCategory attribute to an equivalent implementation in xUnit.Net.

MSTest allows us to run the test that belongs to a specific category. Let’s see a solution on how this can be accomplished in xUnit.Net.

C#
using Xunit;
using Xunit.Extensions;

namespace xUnitCustomizations
{
    [CustomTestClassCommand]
    public class TestClass
    {
        [Fact, TestCategory("Unit")]
        public void FastTest()
        {
            Debug.WriteLine("fast test executed");
            Assert.True(true);
        }

        [Fact, TestCategory("Integration")]
        public void SlowTest()
        {
            Thread.Sleep(5000);
            Debug.WriteLine("slow test executed");
            Assert.True(true);
        }
    }
}

The CustomTestClassCommandAttribute attribute is used to indicate that a custom test runner will be used:

C#
public class CustomTestClassCommandAttribute : RunWithAttribute
{
    public CustomTestClassCommandAttribute() : base(typeof(CustomTestClassCommand)) { }
}

CustomTestClassCommand is the class that implements ITestClassCommand and acts as the runner for the test fixture.

C#
public class CustomTestClassCommand : ITestClassCommand
{
    // Delegate most of the work to the existing TestClassCommand class so that we
    // can preserve any existing behavior (like supporting IUseFixture<T>).
    readonly TestClassCommand cmd = new TestClassCommand();
    Random randomizer = new Random();

    #region ITestClassCommand Members
    public object ObjectUnderTest
    {
        get { return cmd.ObjectUnderTest; }
    }

    public ITypeInfo TypeUnderTest
    {
        get { return cmd.TypeUnderTest; }
        set { cmd.TypeUnderTest = value; }
    }

    public int ChooseNextTest(ICollection<IMethodInfo> testsLeftToRun)
    {
        return randomizer.Next(testsLeftToRun.Count);
    }

    public Exception ClassFinish()
    {
        return cmd.ClassFinish();
    }

    public Exception ClassStart()
    {
        return cmd.ClassStart();
    }

    public IEnumerable<ITestCommand> EnumerateTestCommands(IMethodInfo testMethod)
    {
        return cmd.EnumerateTestCommands(testMethod);
    }

    public bool IsTestMethod(IMethodInfo testMethod)
    {
        return cmd.IsTestMethod(testMethod);
    }

    public IEnumerable<IMethodInfo> EnumerateTestMethods()
    {
        string category;

        foreach (IMethodInfo method in cmd.EnumerateTestMethods())
        {
            category = string.Empty;
            foreach (IAttributeInfo attr in method.GetCustomAttributes(
                           typeof(TestCategoryAttribute)))
                category = attr.GetPropertyValue<string>("Value");

            if (category.ToLower().Contains("unit"))
            // We can make this configurable
                yield return method;
        }
    }
    #endregion
}

The method public IEnumerable<IMethodInfo> EnumerateTestMethods() filters the tests methods by TestCategory's attribute Value; note that we can make this configurable so we can configure our CI server to run the unit test as soon as there are changes in the repository to provide quick feedback and schedule (e.g., once a day) the execution slower to like an integration or Web UI test.

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)