Hello, I think it's probably too early to deprecate testcontainers modules, because test-infra modules are probably less easy to use currently.
I would leave them without deprecation for the moment. But lets wait for more feedback. Il giorno mar 5 gen 2021 alle ore 10:36 Claus Ibsen <claus.ib...@gmail.com> ha scritto: > Hi Otavia > > Great work. > > Can you maybe tell a bit about what if an end user have used > camel-testcontainers-junit5 to do his/her own container testing with > Camel (for example to use their own container image, or for example a > database container or something). How would they do that today with > the test infra? > > > On Tue, Jan 5, 2021 at 9:37 AM Otavio Rodolfo Piske > <angusyo...@gmail.com> wrote: > > > > 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 > > > > -- > Claus Ibsen > ----------------- > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 >
