Use the Collection Runner from the Postman VS Code extension

With the Postman VS Code extension, you can use the Collection Runner to manually run a collection's or folder's requests in a specific sequence. This enables you to test an API's functionality or performance. You can also automate collection runs in your CI/CD with the Postman CLI or Newman.

By default, your requests run in the sequence they're listed in the collection. If you need to change the run, select and drag a request to its new location in the sequence. You can also remove an individual request from the run by clearing the checkbox next to its name. You can optionally use post-response scripts to pass data between requests and alter the request workflow. Learn how to customize a collection run with post-response scripts.

To learn more about manual collection runs in Postman, see Test your API using the Collection Runner.

Configure a collection run

To manually run requests in a collection or folder, do the following:

  1. Select a collection or folder with requests you want to run in sequence.

  2. Click Run icon Run to configure the collection run.

  3. If you want your collection to run with an environment, select it using the environment selector at the upper right. You can also click Create New to create a new environment. Learn how to manage environments in the VS Code extension.

  4. Choose any configuration options:

    • Iterations - The number of iterations for your collection run. You can also run collections multiple times with different data sets to build workflows.

    • Delay - An interval delay in milliseconds between each request.

    • Data - You can import a data file and use its values in the collection run. The data file must be in CSV or JSON format. Learn more about formatting a data file.

    • Persist responses for a session - Log the response headers and bodies so you can review them after running the collection. For large collections, persisting responses may affect performance.

    • Advanced settings

      • Stop run if an error occurs - By default, the collection run stops if an exception is encountered within a script or if there's a problem sending a request. Clear this checkbox if you want the collection run to continue after an error occurs.
      • Keep variable values - Persist the variables used in the run, so any variables updated by the run will remain changed after it completes. If you don't persist variables, changes aren't saved after the run completes. Note that persisting variables in the collection run will update the current value (local) only.
      • Run collection without using stored cookies - If your requests use cookies, you can optionally deactivate them for a collection run.
      • Save cookies after collection run - Save the cookies used in this session to the cookie manager. Any values changed by requests during the run will remain after it completes.
  5. To run the collection with your completed configuration, click Run (collection name).

Your Postman plan gives you a limited number of collection runs you can use each month. This limit applies to collections you run manually. A collection run with multiple iterations counts as a single run.

Debug run results

When running collections manually, Postman displays the results of your request runs and test results in real time. To learn more about what happened during the collection run, you can:

  • Select a request to view more details about it, including the response, headers, and request.
  • Select the name of a request to open it in a new tab.
  • Select the Passed, Failed, or Skipped tabs to filter the results by test status. To show all requests, select the All Tests tab. If any tests in a request script fail during a collection run, the whole request fails.
  • Click View all runs to view the run history for your collection.
  • Click Run icon Run Again to run the collection again using the same settings.
  • Click Add icon New Run to configure a new run for the collection. Make changes to any settings, and then select Run (collection name) to run the collection again.

Learn more about debugging run results in Postman.

View run history

You can also view the run history for your collection, including collections you ran using the Collection Runner and the Postman CLI.

Select a collection or folder, then select the Runs tab. You can filter your run history by the number of collection runs to view, users who ran the collection, the test status of the collection runs, and the source of the collection run.

To return to the results of the collection run, hover over a collection run and click Report icon View Report.

Learn more about viewing run history in Postman.

Last modified: 2025/07/25