Running Postman Tests with Newman

Newman is Postman’s command-line collection runner — it lets you run API tests in CI/CD pipelines, schedule executions, and generate reports without opening Postman.

Why Use Newman?

  • Automates API testing — runs Postman collections without manual effort.
  • Integrates with CI/CD — works with Jenkins, GitHub Actions, Azure DevOps.
  • Supports reporting — generates CLI, JSON, HTML, and JUnit reports.
  • Batch execution — runs multiple requests together.

Interview Tip:
"In a CI/CD pipeline, we use Newman in Jenkins to execute API tests after each deployment. If any test fails, the pipeline stops — which prevents broken APIs from progressing."

Running Postman Tests from the Command Line

You run Postman tests from the terminal using Newman. It executes an exported collection (and environment) with a simple CLI command and can generate reports in CLI, JSON, JUnit, and HTML formats.

Advertisement

The general pattern is to:

  • Export the collection from Postman.
  • Export the environment from Postman.
  • Run them with Newman.
  • Specify the collection file, environment file, and desired reporter.

Integrating Postman with Jenkins (CI/CD)

Integrating Postman with Jenkins automates API testing in a CI/CD pipeline, ensuring APIs function correctly after every build.

Why Integrate with Jenkins?

  • Ensures API stability — runs tests on every build.
  • Provides test reports — CLI, JSON, or JUnit reports.
  • Improves the CI/CD workflow — helps detect issues early.

How It Works

Install Newman on the Jenkins server, export the Postman collection and environment, and configure a Jenkins job to run the collection via Newman.

Interview Tip:
"In a banking application, after every deployment, Jenkins ran API tests (like transaction validation). If any API failed, the pipeline stopped the release — catching issues before they reached production."

Debugging Postman Scripts

Debugging in Postman uses console logs and built-in tools.

Postman Console

Open it via:

View → Show Postman Console (or Ctrl + Alt + C)

Add console.log() inside your scripts to print values such as:

  • API response
  • Status code

Pause Execution

Use:

 
postman.setNextRequest(null);
 

This stops the run at a specific point for debugging.

Inspect Requests and Responses

The Postman Console shows:

  • The actual request sent
  • The response received

This helps troubleshoot failures more effectively.

Error Handling in Scripts

Wrap script logic in a try-catch block so that if a script fails, you catch the error and print it instead of letting the whole run break silently.

 
try {
   let data = pm.response.json();
   // assertions using data...
} catch (err) {
   console.log("Script error:", err);
}
 

This makes test failures easier to diagnose and keeps the run informative.

FAQs

What is Newman?

Postman’s command-line collection runner is used to run API tests in CI/CD pipelines and generate CLI/JSON/HTML/JUnit reports without opening Postman.

How do you run Postman tests from the command line?

Export the collection and environment, then run them with Newman, specifying the collection, environment, and a reporter for output.

How do you integrate Postman with Jenkins?

Install Newman on the Jenkins server, export the collection/environment, and configure a Jenkins job to run the collection via Newman on each build.

How do you debug Postman scripts?

Use the Postman Console with console.log(), pause with postman.setNextRequest(null), and inspect the actual requests and responses.

How do you handle errors in Postman scripts?

Use try-catch blocks to catch and log errors so failures are visible and easier to diagnose.

Why run API tests in CI/CD?

To run tests automatically on every build/deployment, catch issues early, and stop the pipeline before broken APIs reach production.