Add testcontainers support in the Remote adapter

TestContainers^1 becomes popular in these days.

When deploying to a running server using remote adapter, we have to prepare a server for it. Nowdays most of the application can be running in docker container.

Add support to combine @TestsContainers and @Container, and Arquillian @Deployment, and make sure application server is started and ready for remote deployment.

[hantsy]

@kiview Yeah, all Jakarta EE compatible application server, such as Payara, WildFly, Open Liberty provide docker images.

When using a remote adapter, we have to prepare a running application server before running the tests. The test itself will package the test classes(defined by @Deployment) into an archive(jar or war, ear) and deploy into the running server, then run the test against the deployed test application.

What we want is simplify the progress, and let testcontainers to prepare the running server(and maybe other dependent services, such as database, redis, mq broker, etc).

Currently if we use @Testcontainers/@Container and Arquillian @Deployment, Arquillian engine do not know the existence of testcontainers container.

[kiview]

I’d also be happy to chime in if any input or advice from the Testcontainers side of things is helpful 🙂 Do I understand it correctly that the integration of Arquillian with Testcontainers would allow doing @SpringBootTest style in-process transparent-box tests for Jakarta applications? In the past, I only used Jakarta in conjunction with Testcontainers for out-of-process opaque-box testing, where the Jakarta app itself is launched as a container.