Jimfs VS failsafe

Java has in-memory file systems that are essentially geared for this exact use case, eg jimfs[0]. You create your filesystem and any files you need when your tests are starting up, and your classes talk to them rather than the “real” ones. Maybe a similar project exists for the C++ ecosystem?

[0] https://github.com/google/jimfs

Recently been using JIMFS. Made my tests much faster and cleaner!

I use Google's JIMFS "Just In Memory Filesystem" https://github.com/google/jimfs in my unit tests and have been very happy. No need to clean something up that disappears as soon as the test is over. Let's you create unix or windows style filesystems and I've used it to test a disk space healthcheck because you can set a limit to the size of the filesystem it creates. Very flexible and easy to use.

A couple of libraries implement these features on the JVM. In this post, we will look at Microprofile Fault Tolerance, Failsafe and Resilience4J.

There are some nice libraries out there that shoot for having zero dependencies (e.g. Methanol, Failsafe) and posts about why it is a good idea for libraries to aim for zero dependencies (jOOQ blog post from 2016).

https://failsafe.dev

If you still want to keep the retry, have a look at failsafe or resilience4j.

I like Failsafe personally. Nice clear API.