[wildfly-dev] Re: Testing with Testcontainers, Arquillian and JUnit 5

"I think moving away from Docker Hub and using the Selenium drivers hosed at quay.io should be possible. Though I don’t know if the screen recording is still possible then." -> I was thinking of experimenting with the BrowserContainer class itself, maybe submit an issue/RFE proposal to the TestContainers, or maybe having a workaround with our own class, that would be 99% identical to the Testcontainer one with the exception of referencing to the quay repository. Main idea would be to promote & support Quay for image repository instead Dockerhub. "Don’t know what exactly you mean by that. Can you elaborate on that?" -> I've noticed following images are being used in Manatoko: quay.io/halconsole/hal and quay.io/halconsole/wildfly. IIUC these images (or one of the images) bundle the application server and HAL together, since our OS images don't have provide any UI. I would probably like to have some control over what images are being tested (I suppose latest EAP/WF + latest HAL). Now I don't know the custom image release cycle or who will be responsible for creating the custom images for testing. If the custom image preparation would be QE's responsibility, ideally, the image property would be customisable. That was the original concern. Thanks, Simon