Automate API Tests with Postman Newman on Cloud

Generates Newman CLI commands, shell scripts, and Jenkins pipeline configurations for running Postman collections in automated or local environments - distinct from generating configs for other CI platforms, which is a companion skill. It first gathers six parameters: collection source (file path, URL, or Postman API UID), environment (file or inline variables), which reporters are needed, fail behavior (--bail versus running all tests), whether the run is a single pass or data-driven with iteration data, and the target (local shell, Jenkins, or both). It then generates Newman commands for four scenarios: a basic local run with HTML reporting, a run pulled directly from the Postman API by collection UID with an API key, a data-driven run against a CSV with a set iteration count, and a run using inline --env-var overrides instead of an environment file. A reusable shell script wraps the command with set -e, a timestamped report directory, and explicit exit-code handling that echoes pass/fail and points to the report file. For Jenkins it generates either a declarative Jenkinsfile (install stage, test stage, and a post block that publishes the HTML report via publishHTML and JUnit results via junit, always-run regardless of pass/fail) or a scripted Jenkinsfile with try/catch/finally around the Newman invocation, plus a variant showing environment-variable and Jenkins-credential injection instead of a checked-in environment file. A reporter reference covers all four Newman reporters - cli (built-in terminal output), junit (built-in, XML for CI test panels), htmlextra (installed separately via newman-reporter-htmlextra, rich HTML report), and json (built-in, raw results) - combinable as --reporters cli,htmlextra,junit. A quick-reference table covers the common flags: --bail to stop on first failure, --timeout-request/--delay-request for timing control, --iteration-count for repeated runs, --folder to scope to one folder, --env-var for inline variables, --suppress-exit-code to always exit 0, --verbose for full request/response detail, and --color off for clean log output. Output is tailored to what's needed: the ready-to-paste command, the shell script, the Jenkinsfile, setup notes (Node.js 14+ required, install commands), and where report files land. After delivering, it offers to hand off to a companion API Documentation skill using the generated output as input.

newman run collection.json \
  --environment environment.json \
  --reporters cli,htmlextra \
  --reporter-htmlextra-export reports/report.html \
  --bail

Use it whenever a user wants to run Postman collections from the command line, generate a Newman CLI invocation, build a reusable shell script around Newman, or set up a Jenkins pipeline specifically for API tests. For other CI platforms (GitHub Actions, GitLab CI, Azure DevOps, CircleCI), a companion CI/CD integration skill covers those directly instead of hand-adapting a Jenkins config.

Input is a collection source, environment, reporter needs, fail behavior, iteration/data-driven requirements, and target environment (shell, Jenkins, or both). Output is a ready Newman CLI command, an executable shell script with exit-code handling, and/or a declarative or scripted Jenkinsfile with report publishing.

Generates configs around the Newman CLI (npm install -g newman, optionally newman-reporter-htmlextra) for local shell and Jenkins environments, and hands off to a companion API Documentation skill on request.

API teams who already have a Newman-runnable Postman collection and want a correct CLI command, a reusable shell script, or a Jenkins pipeline with proper reporting and exit-code handling, without hand-assembling the flags and pipeline boilerplate themselves.