Skip to main content
12 events
when toggle format what by license comment
S May 21, 2021 at 9:52 history suggested TurboLion CC BY-SA 4.0
Update link (CodePlex will shutdown on July 1, 2021)
May 20, 2021 at 12:04 review Suggested edits
S May 21, 2021 at 9:52
Jun 27, 2019 at 0:20 comment added Sudhanshu Mishra To the point of testing, EF Core has come a long way with out of the box In-Memory and In-Memory with Sqlite providers to enable unit testing. Bring in docker when you need integration testing to run tests on a containerised database.
May 30, 2015 at 6:58 comment added Alireza Loosing related entity navigation is bad and is counter OOP, but you'll have more control on what's being queried.
Mar 6, 2014 at 0:29 comment added Chris Pratt EF's testability has improved greatly in version 6. You may now fully mock DbContext. Regardless, you could always mock DbSet, and that's the meat of Entity Framework, anyways. DbContext is little more than a class to house your DbSet properties (repositories) in one location (unit of work), especially in a unit testing context, where all the database initialization and connection stuff is not wanted or needed anyways.
Dec 3, 2013 at 4:36 comment added Daniel Little You can still have unit tests without wrapping the EF Context (which is already a repository). You should be unit testing your domain / services not database queries (they're integration tests).
Mar 27, 2013 at 16:45 history edited luksan CC BY-SA 3.0
added 747 characters in body
Feb 19, 2013 at 6:06 comment added Sleeper Smith Any architecture article without mentioning unit test are automatically sent to the trash bin for me. One of the point of repository pattern is to gain some test-ability.
Dec 31, 2012 at 22:53 history edited luksan CC BY-SA 3.0
added 81 characters in body
Dec 31, 2012 at 19:25 history edited luksan CC BY-SA 3.0
deleted 3 characters in body
Dec 31, 2012 at 18:34 review First posts
Dec 31, 2012 at 18:37
Dec 31, 2012 at 18:17 history answered luksan CC BY-SA 3.0