Each of the existing binary stores implementation has their own, dedicated, unit test. Since the BinaryStore is a generic interface, ideally we should have only 1 set of tests and via different Maven profiles, run those tests on different implementations.

The approach is similar to the existing "database" property approach, only a bit more generic:

• we can define a profile, triggered by a property, for each of the different types of binary stores, having the FileSystemBinaryStore as default
• each profile would define a property (e.g. binaryStoreRepositoryConfig) which points to a file path that can be loaded (accessible) by the class loader of the generic binary test.
• each profile can add its own test dependencies. For MongoDB for example, we can use Embedded Mongo DB

The benefits of this approach would be:

• it would simply development effort of adding binary stores (no extra tests needed)
• we could extend it to other cases if we needed to (e.g. query tests with various configurations)