Home/ Questions/Q 99227
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T00:20:50+00:00

I want to write unit tests with NUnit that hit the database. I’d like

  • 0

I want to write unit tests with NUnit that hit the database. I’d like to have the database in a consistent state for each test. I thought transactions would allow me to ‘undo’ each test so I searched around and found several articles from 2004-05 on the topic:

These seem to resolve around implementing a custom attribute for NUnit which builds in the ability to rollback DB operations after each test executes.

That’s great but…

  1. Does this functionality exists somewhere in NUnit natively?
  2. Has this technique been improved upon in the last 4 years?
  3. Is this still the best way to test database-related code?

Edit: it’s not that I want to test my DAL specifically, it’s more that I want to test pieces of my code that interact with the database. For these tests to be ‘no-touch’ and repeatable, it’d be awesome if I could reset the database after each one.

Further, I want to ease this into an existing project that has no testing place at the moment. For that reason, I can’t practically script up a database and data from scratch for each test.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. NUnit now has a [Rollback] attribute, but I prefer to do it a different way. I use the TransactionScope class. There are a couple of ways to use it.

    [Test] public void YourTest()  {     using (TransactionScope scope = new TransactionScope())     {         // your test code here     } }

    Since you didn’t tell the TransactionScope to commit it will rollback automatically. It works even if an assertion fails or some other exception is thrown.

    The other way is to use the [SetUp] to create the TransactionScope and [TearDown] to call Dispose on it. It cuts out some code duplication, but accomplishes the same thing.

    [TestFixture] public class YourFixture {     private TransactionScope scope;      [SetUp]     public void SetUp()     {         scope = new TransactionScope();     }      [TearDown]     public void TearDown()     {         scope.Dispose();     }       [Test]     public void YourTest()      {         // your test code here     } }

    This is as safe as the using statement in an individual test because NUnit will guarantee that TearDown is called.

    Having said all that I do think that tests that hit the database are not really unit tests. I still write them, but I think of them as integration tests. I still see them as providing value. One place I use them often is in testing LINQ to SQL code. I don’t use the designer. I hand write the DTO’s and attributes. I’ve been known to get it wrong. The integration tests help catch my mistake.

    • 0