Tuesday, July 2, 2013

Using different dataloaders in Effort

Last week I blogged about Effort, a library that helps you write unit test against your Entity Framework code. In that post I showed you how to populate the Effort in-memory database by using CSV files. Turns out that that is not the only way to populate the Effort database.

Effort provides multiple built-in data loaders:

  • EntityDataLoader: fetch data from an existing database by utilizing an existing Entity Framework compatible ADO.NET provider.
  • CsvDataLoader: read data records from CSV files
  • CacheDataLoader: speed up the initialization process by wrapping any kind of data loader with a cache layer

And of course it is also possible to build your own data loader.

More information can be found here.

No comments: