Comments on: High performance database rollback in automated tests with SQL Server

By: Graeme

Graeme — Wed, 26 May 2010 18:11:23 +0000

I guess the only answer is “it depends”, but I have found it to gives better performance than any other method. I use very small amounts of data in the test db though.

By: Marcus Malmgren

Marcus Malmgren — Wed, 26 May 2010 18:06:50 +0000

Is it fast enough to run the tests against a real DBMS?

By: Graeme

Graeme — Tue, 25 May 2010 17:05:22 +0000

If the tests fail on the build server then that is a feature. It notifies you that your schema is out of sync with your tests (and quite possibly your application code as well).

By: Marcus Malmgren

Marcus Malmgren — Tue, 25 May 2010 16:01:28 +0000

Great! But: This sounds more like integration tests than unit test. Its hard to include these tests in continous integration because if the database schema changes, the tests will fail on the build server. Of course you can manage scripts and run them on the build server before executing the tests, but it makes it more difficult. I really like EF but i miss the data access test possibilities in NHibernate.

By: Alex

Alex — Wed, 07 Apr 2010 19:09:25 +0000

This is quite good, I was wondering if there’s a good way of doing this. Recently I’ve been working on a large-ish Silverlight/RIA services/EF app and the unit tests ended up as integration tests; I wrote a couple stored procedures that cleaned up and restored test data but couldn’t possibly run them after each test method - they were reasonably fast but not that fast. I’ll definitely give this a go.

By: Unit testing an Entity Framework DAL part 2: Rolling back the test database | Graeme Hill on .NET development

Sat, 23 Jan 2010 17:27:20 +0000

[...] (Jan 23, 2010): I have made a new post explaining a method that I think is better than any of those described [...]