Respawn VS Brighter

ImMemoryDb isnt recommended for testing as it doesnt behave as a real database. Save yourself trouble and use a real database paired with Respawn.

I come from a .NET background and in the .NET environment I used to seed the database with the necessary data on each test and then clean the database at the end of the test using the Respawn library.

This was our initial approach (using sqlite) but our migrations take a while to run and this resulted in slow tests. Using Respawn to clean the db significantly improved test performance (https://github.com/jbogard/Respawn)

Have you used something like Respwan https://github.com/jbogard/Respawn instead of creating and cleaning or deleting database every time? Not sure if it would help you. But I thought it might make your workflow little simpler. Respawn lets to restore db to a restore point.

NUnit, FluentAssertions, Moq & Respawn

You will need a separate test database purely for integration tests. You will need to reset the state of the DB every time using something like https://github.com/jbogard/Respawn. I always use the (localdb)\mssqllocal SQL instance that comes as standard with VS for dev and integration test databases.

I believe that brighter (https://www.goparamore.io/) can use the database for persistence.

Consider the CQRS pattern as a replacement to repository/service. Because it's not that complicated, I ended up rolling my own implementation (ICommand, ICommandHandler, ICommandDispatcher, equivalents for Query, and then some DI to tie them together.) There are quite a few Nuget CQRS packages and lots of example implementations on the web. I also just heard about Brighter and Darker but I haven't had a chance to try them out yet. Sounds pretty interesting.

Here is one that tests the write of a message to a database, and here is one where he creates a concrete stub to simulate an exception.

Brighter/Darker https://www.goparamore.io/

There are some other libraries to implement this, even from scratch, but at this time I'm using the same Mediatr library, implementing IRquest and IRequestHandler interfaces.