How should I set up my integration tests to use a test database with Entity Framework?

by

Thanks so much to @Justin and @Petro for your answers, which have helped me immensely. The solution I have come up with is a combination of the techniques you suggested. The solution described below provides a new database for each run of the tests, and a separate transaction for each test.

I added a connection string for my test database in the App.config of my Test project:

  <connectionStrings>
    <add name ="TestDatabase"
     providerName="System.Data.SqlClient"
     connectionString="Data Source=(LocalDb)\v11.0;Database=TestDatabase;Integrated Security=True"/>
  </connectionStrings>

I created a base class for my integration tests, to provide setup and teardown. Setup instantiates the context, creates the DB if it doesn’t exist yet and starts a transaction. Teardown rolls back the transaction.

public class EntityFrameworkIntegrationTest
{
    protected MyDbContext DbContext;

    protected TransactionScope TransactionScope;

    [TestInitialize]
    public void TestSetup()
    {
        DbContext = new MyDbContext(TestInit.TestDatabaseName);
        DbContext.Database.CreateIfNotExists();
        TransactionScope = new TransactionScope(TransactionScopeOption.RequiresNew);
    }

    [TestCleanup]
    public void TestCleanup()
    {
        TransactionScope.Dispose();
    }
}

Finally, I have a class that takes care of deleting the database after all the tests have run:

[TestClass]
public static class TestInit
{
    // Maps to connection string in App.config
    public const string TestDatabaseName = "TestDatabase";

    [AssemblyCleanup]
    public static void AssemblyCleanup()
    {
        Database.Delete(TestDatabaseName);
    }
}

I should add that I found this blog post about Entity Framework useful for a deeper understanding of what Entity Framework is doing under the hood / by convention.

More Related Contents:

  1. Create code first, many to many, with additional fields in association table
  2. EF codefirst : Should I initialize navigation properties?
  3. Entity Framework (EF) Code First Cascade Delete for One-to-Zero-or-One relationship
  4. Validation failed for one or more entities while saving changes to SQL Server Database using Entity Framework
  5. Filter/Search using Multiple Fields – ASP.NET MVC
  6. Does Entity Framework 4 Code First have support for identity generators like NHibernate?
  7. How to do a Bulk Insert — Linq to Entities
  8. How to declare one to one relationship using Entity Framework 4 Code First (POCO)
  9. Mapping Database Views to EF 5.0 Code First w/Migrations
  10. LINQ to Entities does not recognize the method ‘System.Web.Mvc.FileResult’
  11. When should I create a new DbContext()
  12. The operation cannot be completed because the DbContext has been disposed using MVC 4
  13. Entity vs Model vs View Model
  14. Place to put Database.SetInitializer
  15. C# Entity-Framework: How can I combine a .Find and .Include on a Model Object?
  16. EF4 Code First: how to add a relationship without adding a navigation property
  17. An error occurred while saving entities that do not expose foreign key properties for their relationships
  18. Entities VS Domain Models VS View Models
  19. Entity Framework and multiple schemas
  20. Entity Framework 4.1: Unable to cast from DbQuery to ObjectQuery
  21. How to create custom additional fields in UserProfile in MVC4
  22. Entity Framework Code First naming conventions – back to plural table names?
  23. The relationship could not be changed because one or more of the foreign-key properties is non nullable
  24. Where to convert business model to view model?
  25. Repository Pattern, POCO, and Business Entities
  26. How should I access a computed column in Entity Framework Code First?
  27. MVC 4 – Many-to-Many relation and checkboxes
  28. .NET Managing Layers Relationships
  29. Entity Framework Many to many through containing object
  30. How can set a default value constraint with Entity Framework 6 Code First?

Leave a Comment