Using the Collection Runner
The Collection Runner allows you to run sets of requests in a specified sequence. The Collection Runner will log your request test results, and your scripts can pass data between requests as well as altering the request workflow.
You can run collections against specific environments, and can pass data files into a run. Collection runs allow you to automate your API testing, and you can schedule runs using monitors. You can integrate collection runs to your CI/CD pipeline using Postman's CLI Newman.
You can run a collection in Postman, using Newman, or with a monitor.
- Starting a collection run
- Running your collections
- Sharing collection runs
- Automating collection runs
- Next steps
To run a collection, open a collection and click Run on the overview tab.
You can also click Runner at the bottom right of Postman and drag a collection over from Collections or History on the left.
By default your requests will run in the sequence they are listed in the collection, but you can click to the left of each one and drag to move it if you need to change the order of execution. You can also deselect an individual request by unchecking its box.
You can alter the flow of execution from your request scripts using
setNextRequestto create workflows.
If you want your collection to run against an environment, make the environment active by selecting it from the drop-down list at the top right of Postman, or from Environments on the left.
You can optionally choose config parameters for your collection run:
- The number of iterations for your collection run. You can also run collections multiple times against different data sets to build workflows.
- An interval delay (milliseconds) between each request.
- A data file for the collection run.
- Saving responses to the log will allow you to review them but can affect performance.
- Persisting variables will mean that any variables updated by the run will remain changed after it. If you do not persist variables, changes will not be saved after the run completes. Note that persisting variables in the collection run will update the current value only. If you have variables set to automatically persist in your Postman settings, each variable initial value will update to the current value after a run.
- Saving cookies means that any values affected by requests during the run will remain after it completes.
With your config complete, click Run (collection name) to execute it. Postman will display your request executions and test results in realtime. To the right you will see a number for each iteration—click to select one. You will see an overview for each request, including its passed or failed tests—you can filter on each using the Passed and Failed tabs at the top.
Click a request name to access more data on what happened when it executed.
If any tests in a request script fail during the collection run, it will be listed as failed—it will be listed as passed if all tests inside it pass.
If you check Save responses when you start a collection run, you will see the responses in the run results.
For additional details such as viewing log statements, open the Console from the bottom left of Postman.
You can export test results and view the Run Summary using the buttons at the top right.
The summary also lists a column for each iteration of your collection run so that you can see test output for the whole run at a glance.
To navigate back click Run Results.
You can share the run results for a collection, by exporting them from the Collection Runner so that other people can analyze them.
To export a collection run, open it in the Runner (using History on the left if you don't still have the run open). Click Export Results at the top right to download the run. Choose a location to save your downloaded collection run.
In addition to using the Collection Runner in Postman, you can use collection runs in conjunction with other utilities in order to build automation into your API projects.
- The Postman command line interface Newman allows you to run collections and build them into your development pipeline, responding to test outcomes to maintain your API performance.
- Adding a monitor to your collection lets you schedule collection runs and stay informed of any issues.
You can use scripts to build workflows specifying conditional sequences for running the requests in your collections.