Hello, as of 3.7.x, all the test infrastructure code that we had was converted to use the test-infra modules.
This brings several benefits for in terms of maintenance for the test code: - we can share more easily, among the sub-projects, the code handling the test infrastructure. For example: setting up and running message brokers, databases, cloud simulation containers, etc. - we "outsource" the management of the resources to JUnit 5 and let it handle the lifecycle, setup, etc ... thus simplifying the test code. - we can separate the interface from implementation. This allows us and colleagues running and testing the Camel code to run integration and interoperability tests more easily. For example, it makes it possible to run the same tests against remote instances of the said infrastructure. This is very handy for AWS tests, for example, where we can switch to run the tests from Localstack containers to an actual AWS instance by simply adjusting the test parameters. It still uses testcontainers under the hood, but it is abstracted from the test code. As result of this migration, the code in the following components has become unused within Camel: - camel-testcontainers - camel-testcontainers-junit5 - camel-testcontainers-spring - camel-testcontainers-spring-junit5 I'd like to propose deprecating these components, starting with 3.8 and then removing them before we release the next LTS. Therefore, I'd like to gather feedback from the community about usage of those modules, thoughts on the idea and if any roadblock remains. Kind regards -- Otavio R. Piske http://orpiske.net
