Debug tests are really slow

[samihuutoniemi]

We have a few hundred unit tests testing our backend, testing a lot of EF Core 6 code. Until recently, we used EntityFrameworkCore.AutoFixture to solve this. But we changed to EntityFrameworkCore.Testing as it can handle raw SQL. And all tests work great now.

The in-memory database is seeded in a method that inserts quite a lot of data into quite many tables. It works and is really quick when the tests are run. It's only executed once. Running only a single test takes around 12 seconds including seeding db.

But when debugging a single test, it takes about 42 seconds. Clocking the method seeding the database, I can see that part takes ~30 seconds.

So the question is: Is there anything that can be done to make debugging faster? This was not a problem in the other library.

[rgvlee]

EntityFrameworkCore.Testing is for the most part a proxy for a database, the MS in-memory provider by default. Generally it's pretty quick, though creating a mock can be an intensive process. If you have a large EDM and you're seeding a lot of different sets/repositories, the mock will take longer to build.

I would need more info; version (EFCore and EFCore Testing); how many sets (and dependencies of) are being seeded for the test; do you have a minimum reproducible sample that I can use to reproduce your symptoms.

Thanks Lee

[rgvlee]

Closing due to inactivity.
The library uses a just in time approach to creating the proxy/mock. The more db sets you seed, the more work that has to be done. There is a cost to creating the proxy/mock.
Unless you specifically need the features of the library - being able to mock relational operations - then there are faster alternatives such as the in memory provider direct.