This project has moved. For the latest updates, please go here.

How would I configure Effort Testing Tool to mock Entity Framework's DbContext withOut the actual SQL Server Database up and running?

Dec 31, 2014 at 5:46 AM
Our team's application development involves using Effort Testing Tool to mock our Entity Framework's DbContext. However, it seems that Effort Testing Tool needs to be see the actual SQL Server Database that the application uses in order to mock our Entity Framework's DbContext which seems to going against proper Unit Testing principles.

The reason being that in order to unit test our application code by mocking anything related to Database connectivity ( for example Entity Framework's DbContext), we should Never need a Database to be up and running.

How would I configure Effort Testing Tool to mock Entity Framework's DbContext withOut the actual SQL Server Database up and running?
Coordinator
Jan 5, 2015 at 10:56 PM
Edited Jan 5, 2015 at 11:03 PM
As the overview of this project states ("create data driven tests that can run without the presence of the external database") you are absolutely not required to have database connectivity. I am using this tool in production systems conveniently because of this fact.

What exactly did make you experience the opposite? Can you provide me a sample code that will communicate with the external database?