I have different collections on a branch that runs on jenkins, I won’t be able to access the server where jenkins is set up, so I won’t be able to alter the newman script on jenkins.
So far I’ve had to declare a new script per collection because I use an specfic iterationData per collection (I’m using the router logic) like this
newman run “postman-automation/tests/collection1” --iteration-data “postman-automation/testsRoutes/collection1-routes.json”
newman run “postman-automation/tests/collection2” --iteration-data “postman-automation/testsRoutes/collection2-routes.json”
I need to know if there’s a more scalable solution where I just set up the newman script where the tests are and the iteration data is, without having to specify which iterationData belongs to which collection on the newman script, that’s why I was wondering if it can be done from the collection:
to have something more like:
newman run “postman-automation/tests/" --iteration-data "postman-automation/testsRoutes/”