views:

995

answers:

2

As in the topic...

I was thinking about something like "in memory changes". On recent blogs by Jaroslaw Kowalski i have found similar approach but i was thinking about sth much simpler

+1  A: 

If the framework consists of (abstract) classes, you can create dummy concrete classes and unittest them.

Gamecat
+1  A: 

Unless you are building/modifying the framework itself, you shouldn't need to unit test it.

As for unit testing entity classes you define, I would recommend the following. 1. Create a stub implementation that uses an in memory database. Which will allow you to test class interaction. 2. Design you classes in such a way that business logic does not require the Entity Framework and unit test those directly.

Kozyarchuk