testcase VS gnomock

One of them focuses on time manipulation for testing purposes: - Freeze time to a specific point. - Travel back to a specific time, but allow time to continue moving forward. - Scale time by a given scaling factor will cause the time to move at an accelerated pace. - No dependencies other than the stdlib - Nested calls to timecop.Travel is supported - Works with any regular Go projects

Fault Inject Package Repo URL

If you like test-driven design, check out my testing framework. https://pkg.go.dev/github.com/adamluzsi/testcase https://github.com/adamluzsi/testcase

refs: - https://github.com/adamluzsi/testcase/releases/tag/v0.71.0 - https://github.com/minimaxir/big-list-of-naughty-strings

In the testcase testing framework, I mostly used github.com/stretchr/testify for the assertions, and everywhere where I work with the testing framework. Most of the time, I barely use the full potential of testify, just some basic assertations like Contains and Equal. I decided to ship these basic assertions within the testing framework, so when I don't need heavy lifting with a full-fledged assertion library, I don't need to import one.

https://github.com/orlangure/gnomock does this pretty well, but I liked your solution too, it is neat.

gnomock https://github.com/orlangure/gnomock - like testcontainers

Try gnomock (https://github.com/orlangure/gnomock). It creates a mongodb container with a random port which you can use from your go tests. See project readme for an example (it uses postgres but it is very similar to mongodb).

You could check out Gnomock (https://github.com/orlangure/gnomock). It offers a different approach than what you asked, but maybe it'll suit your use case. It allows to easily setup a real DB like postgres in a docker container and then delete ot when tests are done.