Can nunit be configured to drop the app domain per fixture (or per test)

Question

In testing singleton classes we need the single instance to "go away" after each test. Is there a way to configure nunit to recreate the test app domain after each test, or at least after each fixture?

If the singleton's setup is so complex that it needs to be tested every time you call it, can you bottle up the creation logic into a method and then test that method instead? — roufamatic, Feb 25 '10 at 17:59

score 6 · Answer 1 · answered Mar 20 '10 at 22:00

You could provide the means to renew the singleton instance when testing via a conditional method.

//  CUT
public sealed class Singleton{

    private static Singleton _instance = new Singleton();

    private Singleton()
    {
         //  construct.
    }

    public static Singleton Instance{
        get{
            return _instance;
        }
    }

    [Conditional ("DEBUG")]
    public static void FreshInstance (){
          _instance = new Singleton();
    }
}


//  NUnit
[TestFixture]
public class SingletonTests{

    [SetUp]
    public void SetUp(){
        Singleton.FreshInstance();
    }
}

zastrowm · Answer 2 · 2019-11-12T23:33:05.557

3

I needed to do the the exact same thing, so I created a library which basically takes the current test and re-executes it in a new AppDomain. It's a nuget package called NUnit.ApplicationDomain and is open source.

Example Code:

[Test, RunInApplicationDomain]
public void Method()
{
  Console.WriteLine("I'm in a different AppDomain")
}

Related StackOverflow Answer

edited Nov 12 '19 at 23:33

answered Jun 22 '13 at 04:11

zastrowm

8,017
3
43
63

Any alternative for .net core ? – tchelidze Dec 18 '19 at 14:17

score 0 · Answer 3 · edited May 11 '18 at 06:15

I guess I'm missing something here Ralph. Just for my own benefit, can you explain why adding methods with the following attributes to your Test Class that drop and recreate your instances wouldn't work for you?

Adding these attributes for methods should make them run before / after each test.

[SetUp]

[TearDown]

Adding these attributes for methods should make them run before / after the fixture.

[TestFixtureSetUp]

[TestFixtureTearDown]

Is there a reason why using methods with these attributes couldn't create and destroy your domain between tests?

Can nunit be configured to drop the app domain per fixture (or per test)

3 Answers3