The repository itself is not usually tested?

by

Repository interface belongs to domain layer. But implementation belongs to infrastructure or data access layer. This implementation is usually not tested with unit test. It uses ORM API heavily, so it is extremely hard and wasteful to test repository in isolation. This problem is not specific to repositories: Don’t mock types you don’t own.

Repository should be tested with integration tests, using real ORM. In memory database is a very popular approach to this problem.

… Because if I use a fake
implementation of my context/session I’m not doing real tests?

Even if you manage to make it (which I really doubt in NHibernate’s case) you will be wasting your time. Session/Context interface is out of your control and your test would just reiterate your guess about how the real thing will work.

Becausethe context/session itself is the repository?

No. Context/Session is implementation of UnitOfWork pattern. It is not part of your domain. This is infrastructure.

The repository pattern with EF or NH is like a wrapper only?

Repository is important domain concept, it is not just a ‘wrapper’. Just like your application is not a ‘wrapper’ over the database. I think that DDD repository interface definition should be based on Ubiquitous Language as much as possible and should not include any ORM related words or types.

More Related Contents:

  1. Fake DbContext of Entity Framework 4.1 to Test
  2. Introducing FOREIGN KEY constraint may cause cycles or multiple cascade paths – why?
  3. Like Operator in Entity Framework?
  4. How can I query for null values in entity framework?
  5. NHibernate ISession Flush: Where and when to use it, and why?
  6. Making Entity Class Closed for Changes
  7. Logging, Aspect Oriented Programming, and Dependency Injection – Trying to make sense of it all
  8. .NET Entity Framework and transactions
  9. Get Database Table Name from Entity Framework MetaData
  10. Can you use Microsoft Entity Framework with Oracle? [closed]
  11. “Items collection must be empty before using ItemsSource.”
  12. Undo changes in entity framework entities
  13. Update primary key value using entity framework
  14. ASP.NET MVC: Is Controller created for every request?
  15. Injecting data to a WCF service
  16. Why is the Visual Studio 2015/2017/2019 Test Runner not discovering my xUnit v2 tests
  17. Is is possible to check if an object is already attached to a data context in Entity Framework?
  18. Generate POCO classes in different project to the project with Entity Framework model
  19. Unit testing a multithreaded application?
  20. How to work with Enums in Entity Framework?
  21. What are Navigation Properties in Entity Framework for?
  22. LINQ to Entities does not recognize the method Int32 get_Item(Int32)
  23. How to set default value for POCO’s in EF CF?
  24. How to map table splitting in EF Code First?
  25. Organizationally, where should I put common queries when using Entity Framework Code First?
  26. Entity Framework 4 Single() vs First() vs FirstOrDefault()
  27. Using entity framework on multiple databases
  28. entity framework Unable to load the specified metadata resource [duplicate]
  29. The model backing the ‘ApplicationDbContext’ context has changed since the database was created
  30. ‘ObjectContext’ vs ‘DbContext’ in Entity Framework

Leave a Comment