TestFixtureSetUp and TestFixtureTearDown

MbUnit now supports TestFixtureSetUp and TestFixtuteTearDown attribute to mark methods to be executed at the beginning of a fixture test case execution and at the end.

[TestFixture]
public class Fixture
{
    [TestFixtureSetUp]
    public void TestFixtureSetUp()
    {...}

    ...

    [TestFixturteTearDown]
    public void TestFixtureTearDown()
    {...}
}

• Both method are optional and are allowed once per class,
• If TestFixtureSetUp invocation fails, no test case are executed and they are all marked as failures,
• TestFixtureTearDown is always invoked,
• If TestFixtureTearDown fails, all the test cases are marked as failure
• TestFixtureSetUp and TestFixtureTearDown are executed on the same instance. This is not ensured for the other methods,
• Output in those methods are recorded in the reports

AssemblyCleanUp, SetUp and TearDown

MbUnit also support test assembly setup and teardown. Those methods should be enclosed in a class that is feeded to the AssemblyCleanUpAttribute (Assembly attribute, thanks Omer), They must be public and static. The setup method must be tagged with SetUpAttribute, and the teardown method with TearDownAttribute:

[assembly: AssemblyCleanUp(typeof(AssemblyCleaner))]
...
public class AssemblyCleaner
{
    [SetUp]
    public static void SetUp()
    {
        Console.WriteLine("Setting up {0}", typeof(AssemblyCleanUp).Assembly.FullName);
    }
    [TearDown]
    public static void TearDown()
    {
        Console.WriteLine("Cleaning up {0}", typeof(AssemblyCleanUp).Assembly.FullName);
    }
}

• Only one class with AssemblyCleanUp per assembly is authorized,
• Both methods are optional,
• If SetUp fails, no tests are run and they are all marked as failure,
• TearDown is always executed.
• If TearDown fails, all the tests are marked as failure