0 of 1 steps0%
The Collection Runner executes your collection once per row in the data file. Each row becomes one iteration, and variables from that row resolve in your request and scripts for that iteration only.
1
Run your collection with a local data file
You'll attach the CSV from Step 2 and run three iterations — one movie ID per row.
- Save
movies.csvfrom Step 2 to your computer (Unix line endings; one header row plus three data rows). - In the sidebar, expand Collections and select Movies API — Data Driven.
- Open the Collection Runner for Movies API — Data Driven. Use either entry point:
- In the left sidebar, select the collection, click ⋯ (View more actions) → Run
- With the collection tab open, click Run on the right side of the tab bar — immediately to the left of the Share button
- In the run setup, choose Functional, then Local.
- Click the Iteration data dropdown → Datafiles tab → Select from computer and choose
movies.csv. - Open the Data tab in the runner — the preview appears automatically. Confirm columns
movieIdandexpectedTitlewith three data rows. - Confirm Data Files is selected in the environment selector — it should still be active from Step 3. Change it only if something else is selected.
- Click the Run Order tab, then click Start run and wait for the run to finish.
Expected outcome: 3 iterations, 1 request per iteration, 6 tests passed (2 tests × 3 rows). Each iteration should show 200 OK and green tests.
Where else data files work
| Local file | Uploaded to workspace | |
|---|---|---|
| Manual Collection Runner | Yes | Yes |
| Scheduled Collection Runner | Yes (local only) | No |
| Monitors | Upload in monitor config | N/A |
| Postman CLI / Newman | Local via -d | No |
Tip: After a manual run you can click Save to Workspace to upload the file for reuse (max 5 MB, manual runs only). Scheduled runs, monitors, and the CLI do not support workspace-uploaded files — use a local file or graduate to a dataset in the next module.