Currently both JUnit 5 extensions @MagnoliaTest and @MagnoliaRepositoryTest do not support customisations. Their previous counterparts (MgnlTestCase and RepositoryTestCase) provided various hooks for e.g. injecting custom repository configurations files, custom properties, module registry, repository manager, etc.

With this ticket we should identify which of these customisations we also need for the new extensions and how we can provide them. Possible approaches include:

• adding attributes to the test annotations
• using @RegisterExtension for more complicated cases where parameters are only available at runtime
• for even more elaborate cases test writers could use and evolve RepositoryConfiguration directly and might even derive further specific extensions when necessary / useful