SetUp Attribute

jnm2 edited this page Jun 14, 2017 · 2 revisions

This attribute is used inside a TestFixture to provide a common set of functions that are performed just before each test method is called.

SetUp methods may be either static or instance methods and you may define more than one of them in a fixture. Normally, multiple SetUp methods are only defined at different levels of an inheritance hierarchy, as explained below.

If a SetUp method fails or throws an exception, the test is not executed and a failure or error is reported.


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

  public class SuccessTests
    [SetUp] public void Init()
    { /* ... */ }

    [TearDown] public void Cleanup()
    { /* ... */ }

    [Test] public void Add()
    { /* ... */ }


The SetUp attribute is inherited from any base class. Therefore, if a base class has defined a SetUp method, that method will be called before each test method in the derived class.

You may define a SetUp method in the base class and another in the derived class. NUnit will call base class SetUp methods before those in the derived classes.


  1. Although it is possible to define multiple SetUp methods in the same class, you should rarely do so. Unlike methods defined in separate classes in the inheritance hierarchy, the order in which they are executed is not guaranteed.

  2. SetUp methods may be async if running under .NET 4.0 or higher.

See also...

Clone this wiki locally
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Press h to open a hovercard with more details.