Is NUnit required anymore? Typemock can do what it does

Hi

The Isolator and NUnit should be used side by side.
NUnit is a test runner - it only runs tests that are decorated with NUnit attributes.
The Isolator is a framework that handles faking objects, it can not run unit tests.

Hope it helps, please let me know if you have more questions.

Hi,

Does that mean my test code would need NUnit attributes?

What I am confused on is NUnit and Typemock both provide similar functionality. In my actual test code, do I need to use both APIs at any time?

Imagine I am writing a test class for a method which gets data from a database and processes it. In typical like this (or advanced cases), do I need the API of NUnit as well as Typemock?

Thanks

Hi

Yes, you'll need the nunit attributes in order to run the tests.
You should create a separate assembly for your unit tests and add references for nunit and Isolator assemblies.

The Nunit runner will run tests in public classes that are marked with TestFixture attribute and public test methods that are marked with Test attribute.

Nunit API provides you the Assert class which includes many methods that let you assert at the end of the test that you got the expected results.

Consider the (simplified) example below.
This is your production code:

public class ClassUnderTest
{
    public int MethodUnderTest(ClassToFake classToFake)
    {
        if (classToFake.MethodToFake() >= 100)
        {
            // do some logic ...
            return 101;
        }

        // do some logic ...
        return 0;
    }
}

public class ClassToFake
{
    public int MethodToFake()
    {
        return 1;
    }
}

This is your unit tests code in separate tests assembly:

[TestFixture] // nunit attribute
public class TestClass
{
    [Test] // nunit attribute
    public void TestMethod()
    {
        // Isolator API.
        ClassToFake fake = Isolate.Fake.Instance<ClassToFake>();
        // Isolator API.
        Isolate.WhenCalled(() => fake.MethodToFake()).WillReturn(100);

        // Call the code under test.
        ClassUnderTest classUnderTest = new ClassUnderTest();
        int actual = classUnderTest.MethodUnderTest(fake);

        // NUnit API. Assert the expected results
        Assert.AreEqual(101, actual);
    }        
}

Hope it clears things up.