You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This question might be too specifc, but I'm wondering if anyone has managed to successfully run containerized @QuarkusIntegration tests in a GitLab CI/CD pipeline. (Probably any CI tool will do).
I've recently played around with integration testing and after a lot of trial and error I managed to run the tests against a container locally.
The command I'm using is mvn clean verify -DskipITs=false -Dquarkus.container-image.build=true which builds the image and runs the tests against it.
The test is done with RestAssured and they make API calls to Quarkus REST endpoints. When I do run the same command in a pipeline it seems to build the image and run the container just fine. Then the test tries to do the API call to localhost:8081/some-path and gets CONNECTION REFUSED.
My gut feeling is that the calls should be made somewhere else than localhost but I'm at a loss to where and how.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
This question might be too specifc, but I'm wondering if anyone has managed to successfully run containerized @QuarkusIntegration tests in a GitLab CI/CD pipeline. (Probably any CI tool will do).
I've recently played around with integration testing and after a lot of trial and error I managed to run the tests against a container locally.
The command I'm using is
mvn clean verify -DskipITs=false -Dquarkus.container-image.build=true
which builds the image and runs the tests against it.The test is done with RestAssured and they make API calls to Quarkus REST endpoints. When I do run the same command in a pipeline it seems to build the image and run the container just fine. Then the test tries to do the API call to
localhost:8081/some-path
and gets CONNECTION REFUSED.My gut feeling is that the calls should be made somewhere else than
localhost
but I'm at a loss to where and how.Beta Was this translation helpful? Give feedback.
All reactions