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
Newman Version (can be found via newman -v): postman/newman:latest
OS details (type, version, and architecture): Ubuntu 22.04.4 LTS
Are you using Newman as a library, or via the CLI? As a docker image
Did you encounter this recently, or has this bug always been there: recently
Expected behavior:
For e2e testing, I'm running a postman/newman:latest image with testcontainers. When I execute the test with JUnit, the container doesn't start and raises the following exception:
2024-07-09 18:54:01,718 ERROR [tc.postman/newman:latest] (main) Log output from the failed container:
error: unknown option '--global-var base_uri=localhost:8081'
What seems to happen is that the option "--global-var" isn't recognized as valid. Running the same command as the one in JUnit but using command line (docker run), works as expected.
Three test are executed by mvn verify: an unit, an integration and an e2e one. The first two works as expected, the third one fails with the mentioned exception. The script run.sh executes exactly the same command as the e2e test but using the docker run shell command and, this time, everything works as expected.
So, my conclusion is that the same newman command works when executed via the shell but fails while executed via postman/newman image in testcontainers.
Could anyone please help to fix this issue ?
Many thank in advance.
The text was updated successfully, but these errors were encountered:
newman -v
): postman/newman:latestFor e2e testing, I'm running a
postman/newman:latest
image withtestcontainers
. When I execute the test with JUnit, the container doesn't start and raises the following exception:What seems to happen is that the option "--global-var" isn't recognized as valid. Running the same command as the one in JUnit but using command line (
docker run
), works as expected.Steps to reproduce the problem:
Three test are executed by
mvn verify
: an unit, an integration and an e2e one. The first two works as expected, the third one fails with the mentioned exception. The scriptrun.sh
executes exactly the same command as the e2e test but using thedocker run
shell command and, this time, everything works as expected.So, my conclusion is that the same
newman
command works when executed via the shell but fails while executed viapostman/newman
image intestcontainers
.Could anyone please help to fix this issue ?
Many thank in advance.
The text was updated successfully, but these errors were encountered: