G6 · Collection Runner + Newman in CI: Newman is an engine that **runs a Postman collection from the command line** — it plays the exact same role in Postman as `mvn test` runnin
Newman is an engine that **runs a Postman collection from the command line** — it plays the exact same role in Postman as `mvn test` running ALL tests in a Maven project from the command line. `Collection Runner` runs the collection manually from the Postman INTERFACE, while `newman run collection.json` runs the SAME collection on a CI server (GitHub Actions) WITHOUT a human. So why is this the "final" step — why move to CI after setting up G1-G5 by hand in Postman? Because a manually run test collection can be forgotten/skipped; a collection wired into CI runs AUTOMATICALLY on EVERY push — when a regression appears in the code you wrote in GROUP B-D, it gets CAUGHT before anyone "forgets to test". **For a deep Newman/CI setup guide → see the `/postman` page.**
🎬 From a Manual Run to an Automatic CI Run
Manual "Run Collection"
Every push triggers it
Regression is caught
The tester runs the collection manually by pressing "Run Collection" in Postman — a step that can be forgotten.
The same collection becomes RUNNABLE from the command line with `newman run`.
This command is wired into a CI pipeline (GitHub Actions) — now EVERY push triggers it automatically.
The lesson — if a developer accidentally introduces a regression into the code from GROUP B-D, it is CI that CATCHES it, not a human.
The Order for Moving a Collection into CI
Export the collection/environment…
Download as .json files from Postman, add them to the repo.
Verify the newman run collection.json -e environment.json command locally.
Add the same command to a GitHub Actions workflow, run it on every push.