How does Microsoft's Entity Framework inhibit test driven development? [closed]

Question

MS's entity framework is considered among developers in the agile community to inhibit test driven development. It was famously attacked by an influential group of .Net developers for not being a true reflection of the principles of the agile movement.

What are the main drawbacks that an agile developer faces when using the entity framework?

Answer 1

It's because it has no mocks - it encourages you to base your app around objects that directly ping the database, with no way to simulate it. One of the primary tenets of agile development is that tests are fast, so that running them is painless and you can continually be testing your code, but with EF, your objects always ping a database and you have to do horrible hacks to get around the generated code that EF makes for you for tests.