- Introduced
@DbSetupBinderConfiguration
- Because of the way
@Nested
test instances are created,TestInstancePostProcessor::postProcessTestInstance
is called twice, once for the outer class, once for the inner class. If the outer class does not have any@DbSetupOperations
the extension will throw anIllegalArgumentException
, complaining about not finding any@DbSetupOperations
. The simple fix is to allow cases where there is no@DbSetupOperations
.
- Added debug JUL logging
- Support multiple data sources
DbSetupSource::name
DbSetupOperation::sources
- Use
ExtensionContext.Store
instead of state variables- Because JUnit Jupiter do not guarantee when extensions are instantiated or how long they are kept around
- Implemented annotations
@DbSetup
@DbSetupSource
@DbSetupOperations
@DbSetupSkipNext