Running collections via CLI in Postman - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output of this Newman CLI command?

You run the following command to execute a Postman collection using Newman CLI:

newman run mycollection.json --reporters cli,json

What will be the result of this command?

Postman

newman run mycollection.json --reporters cli,json

A The command runs but outputs only a JSON report file without CLI output.

B The command runs but only outputs the CLI report, ignoring JSON.

C The command fails because multiple reporters cannot be specified together.

D The collection runs and outputs results in both CLI and JSON report formats.

💡 Hint

Newman supports multiple reporters separated by commas.

Newman allows specifying multiple reporters separated by commas. Here, both CLI and JSON reports will be generated and shown.

❓ assertion

intermediate

Which assertion correctly checks the HTTP status code in a Postman test script?

Inside a Postman collection test script, you want to assert that the response status code is 200. Which code snippet correctly does this?

Postman

pm.test('Status code is 200', function () {
    pm.response.to.have.status(200);
});

A pm.test('Status code is 200', function () { pm.response.to.have.status(200); });

B pm.test('Status code is 200', function () { pm.response.status === 200; });

C pm.test('Status code is 200', () => pm.response.to.have.status(200));

D pm.test('Status code is 200', function () { pm.response.statusCode(200); });

💡 Hint

Use pm.response.to.have.status with a function inside pm.test.

Option A uses the correct syntax with a function and the assertion pm.response.to.have.status(200). Option A uses arrow function with implicit return, which is valid. Option A and D are incorrect syntax.

🔧 Debug

advanced

Why does this Newman CLI command fail to run the collection?

You run this command:

newman run collection.json --env environment.json --folder

But it fails with an error. What is the cause?

Postman

newman run collection.json --env environment.json --folder

A The --folder option requires a folder name argument which is missing.

B The collection file must be named collection.postman_collection.json.

C The --env option must be specified after --folder.

D Newman does not support running collections with environment files.

💡 Hint

Check if all options have required arguments.

The --folder option requires the name of the folder inside the collection to run. Omitting the folder name causes an error.

🧠 Conceptual

advanced

What is the purpose of the --delay-request option in Newman CLI?

When running a Postman collection via Newman CLI, what does the --delay-request option do?

A It delays the start of the entire collection run by the specified milliseconds.

B It retries failed requests after the specified delay.

C It adds a delay in milliseconds between each request execution.

D It delays the generation of the report until all requests finish.

💡 Hint

Think about pacing requests to avoid server overload.

The --delay-request option adds a pause between each request in the collection, useful to avoid hitting rate limits or server overload.

❓ framework

expert

How to integrate Newman CLI with a CI/CD pipeline for automated testing?

You want to run Postman collections automatically in your CI/CD pipeline using Newman CLI. Which approach is best practice?

A Run Newman manually on the build server after deployment to production.

B Add a script in the pipeline configuration that runs 'newman run' with collection and environment files, and fail the build if tests fail.

C Use Newman only locally and upload reports manually to the CI server.

D Replace Newman with a GUI tool for CI/CD integration.

💡 Hint

Automation means no manual steps and failing builds on test failures.

The best practice is to add Newman commands in the pipeline scripts to run tests automatically and fail builds if tests fail, ensuring quality gates.