| name | newman-cicd-integration |
| description | Generates CI pipeline YAML/Groovy that installs Newman, runs Postman collections with JUnit/HTML reporters, and publishes artifacts on GitHub Actions, GitLab CI, Jenkins, Azure DevOps, or CircleCI. Use when moving Newman/Postman API tests into CI. Not for authoring Postman collections, local newman run without a pipeline, or Playwright/browser E2E. |
| version | 1.0.1 |
| risk | unknown |
| source | https://github.com/LambdaTest/agent-skills/tree/main/api-skill/newman/newman-cicd-helper |
| source_repo | LambdaTest/agent-skills |
| source_type | community |
| date_added | 2026-07-01T00:00:00.000Z |
| license | MIT |
| license_source | https://github.com/LambdaTest/agent-skills/blob/main/LICENSE |
Newman CI/CD Integration Generator
Overview
This skill generates complete, copy-paste-ready CI/CD pipeline configurations that install Newman and run Postman collections as part of automated builds. It supports GitHub Actions, GitLab CI, Jenkins (Declarative Pipeline), Azure DevOps, and CircleCI. Each generated config includes Newman installation, test execution with JUnit and HTML reporters, artifact publishing, and secret injection patterns specific to the target platform.
When to Use
Use this skill when the user needs to:
- Run Newman in a CI pipeline for automated API testing
- Integrate Postman collections into automated builds
- Set up API tests in GitHub Actions, GitLab CI, Jenkins, Azure DevOps, or CircleCI
- Generate pipeline configs that publish Newman test results to CI dashboards
- Migrate manual Newman runs into a CI/CD workflow
Trigger keywords: Newman CI, Newman pipeline, Postman CI/CD, API testing pipeline, Newman GitHub Actions, Newman GitLab, Newman Jenkins, Newman Azure DevOps, Newman CircleCI, automated API tests, Postman collection automation.
Prerequisites
- Node.js 18+ available in the CI runner image (or installable via the platform's setup action/task).
- Newman installed globally (
npm install -g newman).
- newman-reporter-htmlextra installed globally (
npm install -g newman-reporter-htmlextra) if HTML reports are needed.
- Postman collection JSON file stored in the repository (e.g.,
./collections/my-api.json) or accessible via a Postman API URL.
- Environment JSON file stored in the repository (e.g.,
./environments/staging.json) with non-secret values. Sensitive values must be injected via CI secrets — never committed to the repo.
- CI secrets configured on the target platform for any credentials the collection requires (e.g.,
API_KEY, BASE_URL).
Recommended repository structure
/
├── collections/
│ └── my-api.json
├── environments/
│ ├── staging.json
│ └── prod.json
└── results/ ← gitignored, created by Newman at runtime
Add results/ to .gitignore:
results/
Procedure
Step 1 — Collect requirements from the user
Before generating any config, confirm the following with the user:
