CODEWITHSUNDEEP
c#nunit
w0051977
w0051977

Reputation: 15817

How do I distinguish between Unit Tests and Integration Tests inside a test class?

My question is similar to this one: Junit: splitting integration test and Unit tests. However, my question regards NUnit instead of: JUnit. What is the best way to distinguish between Unit Tests and Integration Tests inside a test class? I was hoping to be able to do something like this:

[TestFixture]
    public class MyFixture
    {
        [IntegrationTest]
        [Test]
        public void MyTest1()
        {
        }

        [UnitTest]
        [Test]
        public void MyTest1()
        {
        }
    }

Is there a way to do this with NUnit? Is there a better way to dot this?

Upvotes: 5

Views: 2811

Answers (4)

Charlie
Charlie

Reputation: 13746

This answer shares some details with a few other answers, but I'd like to put the question in a slightly different perspective.

The design of TestFixtures is such that every test gets the same setup. To use TestFixtures correctly, you should divide your tests in such a way that all the tests with the same setup end up in the same test class. This is how almost every xunit framework is designed to be used and you always get better results when you use software as it is designed to be used.

Since Integration and Unit tests are not likely to share the same setup, this would naturally lead to putting them in a separate class. By doing that, you can group all integration tests under a namespace that makes them easy to run independently.

Even better, as another answer suggests, put them in a separate assembly. This works much better with most CI builds, since failure of an integration test may be more easily distinguished from failure of an integration test. Also, use of a separate assembly eliminates all the complication of using categories or special attributes.

Upvotes: 1

ianrathbone
ianrathbone

Reputation: 2362

Do not have them in the same class, either split them down into folders within your test assembly or split them into two separate test assemblies.

In the long run this will be far easier to manage especially if you use tools like NCrunch.

Upvotes: 0

TrueWill
TrueWill

Reputation: 25573

Personally I've found it better to keep them in separate assemblies. You can use a convention, such as name.Integration.Tests and name.Tests (or whatever your team prefers).

Either assemblies or attributes work fine for CI servers like TeamCity. The pain with the attribute approach tends to show up in IDE test runners. I want to be able to quickly run only my unit tests. With separate assemblies, it's easy - select the appropriate test project and run tests.

Upvotes: 9

LoflinA
LoflinA

Reputation: 350

The Category Attribute might help you do this.

https://github.com/nunit/docs/wiki/Category-Attribute

namespace NUnit.Tests
{
  using System;
  using NUnit.Framework;

  [TestFixture]
  public class SuccessTests
  {
    [Test]
    [Category("Unit")]
    public void VeryLongTest()
    { /* ... */ }
}

Upvotes: 1

Related Questions