Effort stands for Entity Framework Fake ObjectContext Realization Tool. It is a powerful tool that enables a convenient way to create automated tests for Entity Framework based applications.
- It is basically an ADO.NET provider that executes all the data operations on a lightweight in-process main memory database instead of a traditional external database.
- It provides some intuitive helper methods too that make really easy to use this provider with existing ObjectContext or DbContext classes.
- A simple addition to existing code might be enough to create data-driven tests that can run without the presence of the external database.
The following code returns all the categories stored in the database.
A simple modification is enough to make Entity Framework use a fake in-memory database.
The term Transient refers to the lifecycle of the underlying in-memory database.
The owner ObjectContext (technically the DbConnection) will be using a unique database instance. If the context/connection is disposed, than the database will be disposed too.
You could set the initial state of the database with Entity Framework, but Effort provides data loaders to do this more easily. The following example fetches the initial data from a real database.
You can entirely dismiss the need for the external database by exporting your data tables into local CSV files.
Effort provides a tool to export all your tables easily to CSV files and use the CSV data loader.
The best way to contribute is by spreading the word about the library:
- Blog it
- Comment it
- Fork it
- Star it
- Share it
- A HUGE THANKS for your help.