Entity Framework 5 performance improvements for testable applications

    Earlier this year I wrote a series of posts about how to automate Entity Framework(EF) testing but since then a lot of things happened: EF 5 was released, it was made open source and Microsoft has published an in-depth article about performance tweaks for older versions of EF and performance improvements in EF 5. Following these events I can now expand my previous post and address an important performance consideration around the EF testable interface that I described earlier.

Automate Entity Framework 4.x mocking using T4 templates - part 2

  In my previous post I described how to use T4 templates to customize the Entity Framework(EF) code generation in order to introduce EF testability. My test code sample showed a very simple way to inject data and test the business logic without using a physical database. However the code that injects the test data could do with a bit of automation itself.

Automate Entity Framework 4.x mocking using T4 templates - part 1

  Every time I read about a new Entity Framework (EF) release I am hoping to find better support for mocking the physical database. I would like an in memory data provider for Entity Framework - thank you very much. It should enable seamless unit testing with a lot of benefits: fast tests, zero environment configuration, no database setup and tear down, happy less grumpy developers. Until this happens the story of building a testable software product with EF will involve some degree of pain.