Newman in CI/CD pipelines in Postman - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to run a Postman collection using Newman.

Postman

newman run [1]

Drag options to blanks, or click blank then click option'

Apostman

Brun

Ccollection.json

Dtest

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'run' or 'postman' instead of the collection file name.

Not specifying any file after 'newman run'.

The newman run command requires the Postman collection file as an argument to execute the tests.

2fill in blank

medium

Complete the code to specify an environment file in Newman command.

Postman

newman run collection.json --env [1]

Drag options to blanks, or click blank then click option'

Aenv

Benvironment

Cenv.json

Denvironment.json

Attempts:

3 left

💡 Hint

Common Mistakes

Omitting the file extension.

Using a wrong file name without .json.

The --env option expects the environment file name, usually with a .json extension.

3fill in blank

hard

Fix the error in the Newman command to generate a JUnit report.

Postman

newman run collection.json --reporters [1]

Drag options to blanks, or click blank then click option'

Ajunit

BJUnit

CJUnitReport

Djunitreport

Attempts:

3 left

💡 Hint

Common Mistakes

Using uppercase or camel case reporter names.

Using incorrect reporter names that Newman does not recognize.

The correct reporter name for JUnit format in Newman is lowercase junit.

4fill in blank

hard

Fill both blanks to run Newman with a collection and save the report to a file.

Postman

newman run [1] --reporters cli,json --reporter-json-export [2]

Drag options to blanks, or click blank then click option'

Acollection.json

Breport.json

Coutput.json

Dresults.json

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up collection and report file names.

Using file names without extensions.

You need to specify the collection file first, then provide a file name to save the JSON report.

5fill in blank

hard

Fill all three blanks to run Newman with collection, environment, and set a timeout.

Postman

newman run [1] --env [2] --timeout [3]

Drag options to blanks, or click blank then click option'

Acollection.json

Benv.json

C5000

Denvironment.json

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong file names or missing extensions.

Setting timeout without a numeric value.

The command runs the collection file with the environment file and sets the timeout in milliseconds.

Practice

1. What is the main purpose of using Newman in a CI/CD pipeline?

easy

A. To write new API tests inside Postman

B. To run Postman API tests automatically from the command line

C. To deploy applications to production servers

D. To monitor server performance in real-time

Solution

1. Step 1: Understand Newman's role

   Newman is a command-line tool designed to run Postman API tests outside the Postman app.

2. Step 2: Connect to CI/CD pipeline use

   In CI/CD pipelines, Newman automates running these tests to check API health during builds or deployments.

3. Final Answer:

   To run Postman API tests automatically from the command line -> Option B

4. Quick Check:

   Newman runs tests in CI/CD = C [OK]

Hint: Newman runs Postman tests from command line in pipelines [OK]

Common Mistakes:

• Confusing Newman with deployment tools
• Thinking Newman writes tests instead of running them
• Assuming Newman monitors servers

2. Which of the following is the correct basic syntax to run a Postman collection using Newman?

easy

A. newman run collection.json

B. newman execute collection.json

C. newman start collection.json

D. newman test collection.json

Solution

1. Step 1: Recall Newman command structure

   The correct command to run a collection is 'newman run' followed by the collection file.

2. Step 2: Verify options

   Options like 'execute', 'start', or 'test' are not valid Newman commands.

3. Final Answer:

   newman run collection.json -> Option A

4. Quick Check:

   Correct Newman run syntax = D [OK]

Hint: Use 'newman run' to execute collections [OK]

Common Mistakes:

• Using 'execute' or 'start' instead of 'run'
• Omitting the 'run' keyword
• Confusing Newman commands with other tools

3. What will be the output when running this command in a CI pipeline?

newman run mycollection.json --reporters cli,json --reporter-json-export result.json

medium

A. Runs tests and outputs results only in CLI, no file created

B. Runs tests and saves results only in XML format

C. Runs tests but fails due to invalid reporter options

D. Runs tests, shows CLI output, and saves JSON report to result.json

Solution

1. Step 1: Analyze reporter options

   The command uses '--reporters cli,json' to show results in CLI and JSON format.

2. Step 2: Check JSON export flag

   '--reporter-json-export result.json' saves the JSON report to the file 'result.json'.

3. Final Answer:

   Runs tests, shows CLI output, and saves JSON report to result.json -> Option D

4. Quick Check:

   CLI + JSON report saved = B [OK]

Hint: Multiple reporters show CLI and save JSON report [OK]

Common Mistakes:

• Assuming no file is created
• Thinking JSON export is invalid syntax
• Confusing JSON with XML report format

4. You added this command in your CI pipeline:

newman run collection.json --reporters cli --reporter-json-export report.json

But the JSON report file is not created. What is the likely problem?

medium

A. The CLI reporter disables file exports

B. The collection.json file is missing

C. Missing 'json' in the --reporters option

D. Newman does not support JSON reports

Solution

1. Step 1: Check reporter options consistency

   The command uses '--reporters cli' but tries to export JSON report, which requires 'json' reporter enabled.

2. Step 2: Understand reporter behavior

   Without 'json' in '--reporters', the JSON export flag is ignored, so no file is created.

3. Final Answer:

   Missing 'json' in the --reporters option -> Option C

4. Quick Check:

   JSON export needs 'json' reporter = A [OK]

Hint: Include 'json' in --reporters to export JSON files [OK]

Common Mistakes:

• Assuming collection file missing causes no report
• Thinking CLI reporter blocks file exports
• Believing Newman can't export JSON reports

5. In a CI/CD pipeline, you want to fail the build if any Postman test fails using Newman. Which command option helps achieve this?

hard

A. --bail

B. --fail-fast

C. --exit-on-error

D. --stop-on-failure

Solution

1. Step 1: Identify Newman option for failure control

   The '--bail' option stops the run and returns a failure exit code if any test fails.

2. Step 2: Confirm other options

   Options like '--fail-fast', '--exit-on-error', and '--stop-on-failure' are not valid Newman flags.

3. Final Answer:

   --bail -> Option A

4. Quick Check:

   Fail build on test failure = --bail [OK]

Hint: Use '--bail' to stop and fail on test errors [OK]

Common Mistakes:

• Using non-existent flags like --fail-fast
• Not using any fail option, so build passes despite failures
• Confusing '--bail' with report generation options