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
  • Please provide more context. Perhaps a language tag, link to what "entity framework" is, etc... Commented Nov 28, 2008 at 23:23

2 Answers 2

2

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

Sign up to request clarification or add additional context in comments.

Comments

2

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.

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.