I'm using Effort to unit test a database. What I'm seeing is that as the database grows in size each unit test takes longer.
Over the last few weeks we've seen a rise from an average time per test from about a quarter of a second to several seconds.
Most of the tests are pretty simple (get this record from the database or update this record).
There have been quite sharp jumps in the test durations which correspond to the times when I added tables and or fields to the entities. There doesn't appear to be a noticeable effect as new csv files are added to the tests or as additional lines
are added, which implies to me that the bulk of the time for the tests are taken up with the creation of the schema rather than the loading of the CSV, though I've made no attempt to profile.
The database currently has around 30 tables with all bar 5 or so defined classes.
The csv files have in total 10K of data in them.
With 200 unit tests (and rising), for each to take seconds is becoming a matter for concern.
Any suggestion (or investigations) most welcome.