Q: Miss the deploying

[torsten-liermann]

Hi,

How are the deployments defined in the test deployed, or how does Arquillian receive the corresponding metadata? Or is there still a gap in the implementation here?

I don't know much about it yet, but it seems that the logic for deploying an archive into the test container still needs to be implemented.

Thx.

[jasondlee]

The goal, thus far, is not necessarily starting a container to which tests will be deployed, but to start containers that are needed for testing. For example, for WildFly, we're using this to start containers for the OpenTelemetry Collector and Jaeger so that we can test our OpenTelemetry and Micrometer support, which was our primary/initial goal for the library. Being able to deploy tests to these managed containers, then, isn't what we were aiming for, but I don't see why it couldn't be done. It would, though, require some more integration work, probably much like (probably augmenting or even replacing) the container-specific extensions.

[torsten-liermann]

Thanks for the hint. I'm currently looking at the trunk of WildFly. So far, I'm still lacking the knowledge of Arquillian to implement "deploy" and "undeploy." If I get the motivation, I will probably gather some initial ideas from the Arquillian implementations.

[jamezp]

I don't think we want to use this to deploy applications. Arquillian itself already does that. The WildFly Arquillian container will handle the deploying/undeploying of applications.

[torsten-liermann]

That works for me. I initially categorized the discussions on the topic of Testcontainers the way I use them in the context of Spring Boot and didn’t think much further about it. The application of this implementation by WildFly 34.0.0 is enlightening. Thanks so far.