[#43] Replace CI Services for Test Containers and move to JUnit 5 #44
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request does two things:
To that end, several adjustments have been made to the pom files to comply with the new JUnit version and Test Containers.
All test classes have thus been adjusted to use the new import statements, removing all public keywords (as they are no longer necessary) and replaced "expected exceptions" for
assertThrows
. Test containers on the other end have only been added to theSpringAMQPIntegrationTest
andRabbitMQBenchmark
classes.Furthermore, the auto-configuration tests have been made up to date, by using an
ApplicationContextRunner
(as this allows for easier control over the used context and properties). This has led to the removal of the two older test classes in favour for a singleAMQPAutoConfigurationTest
class.Whenever applicable, warnings have been resolved and JavaDoc has been included.
This pull request resolves #43