dotnet-testcontainers VS FluentDocker

So what I usually do is: • Unit test underlying (public) services and application ‘core’ • Integration test (or w/e you call it) an entire functionality flow, by sending in ‘real’ requests on one end, and locally mocking/stubbing the application ‘edges’ that supply the response data. WireMock for requests to external services, H2 or Testcontainers for database.

I'd use testcontainers to spin up an instance of Progress and run against the actual thing. That way you get the benefit of testing against the actual database, but also that you don't have to set up a bunch of stuff locally.

Not every db support array as primitive, if you want to write integration tests and you have access to docker I suggest you testcontainers.

There is a rope which can help with this task: https://github.com/HofmeisterAn/dotnet-testcontainers

Dotnet.Testcontainers also comes with some built-in classes that wraps various services, one of these classes actually wraps a SQL Server Docker container and there are few more that covers the most common databases e.g.

You should also check out Docker, especially TestContainers. That way you can spin up databases (and other dependencies) on the fly and do operations on them. This means that you don't need to "fake" a database, as you will have access to a new one.

I have a blog post on setting up docker in your integration tests. Want to refactor it to use fluent docker eventually but works well for now.

I would just stick to integration tests here. The good news is you're using docker already, why not spin up a docker container of the database in your tests? Fluent Docker is a great tool for this.