Mhazad's Blog

January 5, 2010

Database Driven Unit Testing Using VSTS

Filed under: ASP.NET, Software Testing, Visual Studio — Mahmudul Haque Azad @ 7:14 am

The primary concern about Database driven Unit testing is to maintain the test database intact. To elaborate suppose we have an add method that adds customer information in the database and we have a get method that actually returns a list of customer from database.

So we will have to different Unit test method for AddCustomer() and GetCustomer().

Now in order to pass the GetCustomer() method as a test case we have decided that it will return exactly 3 records and we have setup our test database in such a way to meet our test criterion.

The problem will be raised if we test the AddCustomer() method before GetCustomer() Method as AddCustomer() method will add one customer and our GetCustomer() Method will return 4 records that will fail its test case.

In order to overcome such situation we can use the power of TransactionScope Object.

In order to use this you must include System.Transactions in the Unit Test Project references and add System.Transactions in the reference section.

In the class generated by VSTS  Unit Test wizard you can see one region commented like below.

#region Additional test attributes


//You can use the following additional attributes as you write your tests:


//Use ClassInitialize to run code before running the first test in the class


//public static void MyClassInitialize(TestContext testContext)




//Use ClassCleanup to run code after all tests in a class have run


//public static void MyClassCleanup()




//Use TestInitialize to run code before running each test


//public void MyTestInitialize()




//Use TestCleanup to run code after each test has run


//public void MyTestCleanup()





From here just uncomment MyTestInitialize() and MyTestCleanup() method.

Now Declare one global variable of TransactionScope Object write the body of the methods like below

TransactionScope ts;

///Use TestInitialize to run code before

///running each test


void MyTestInitialize()


ts = new


///Use TestCleanup to run code after

///each test has run


void MyTestCleanup()




After this before executing any Unit Test method MyTestInitialize() method will be called where a new instances of TransactionScope will be created and and after executing the Unit test method the object will be disposed which will ultimately rollback all the changes committed by the Unit test Method keeping our test database intact.

Happy Testing!



  1. That’s a great article, thanks for sharing..

    One small doubt, How can we use it with Windows Application, as Transaction Scope is not available ..


    Comment by Panki — January 18, 2010 @ 1:04 pm

    • Just add System.Transactions in your project reference and add this in your code “using System.Transactions;”

      Comment by Mahmudul Haque Azad — January 19, 2010 @ 4:33 am

RSS feed for comments on this post. TrackBack URI

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

Create a free website or blog at

%d bloggers like this: