Importing and exporting collections in Postman - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Postman Collection Export Formats

Which export format in Postman preserves all request details including scripts, tests, and collection variables for sharing or backup?

A Export as a plain text file listing request names

B Export as a CSV file containing request URLs only

C Export as a JSON file using the Collection v2.1 format

D Export as an HTML report of test results

💡 Hint

Think about which format keeps the full structure and metadata of your requests.

The Collection v2.1 JSON format exports all details including requests, scripts, and variables, making it ideal for sharing or backup. CSV and plain text formats lose important data, and HTML exports are for reports, not collections.

❓ Predict Output

intermediate

Result of Importing an Invalid Collection File

What will Postman display if you try to import a collection file with invalid JSON syntax?

A The collection imports partially with missing requests

B An error message indicating 'Invalid JSON format' and import fails

C Postman silently ignores errors and imports the file

D Postman converts the file to a valid format automatically

💡 Hint

Consider how Postman handles files that do not follow JSON rules.

Postman validates the JSON syntax during import. If the file is invalid, it shows an error and does not import the collection.

❓ assertion

advanced

Verifying Exported Collection Contains Collection Variables

After exporting a collection, which assertion confirms that collection variables are included in the exported JSON file?

Postman

const exported = JSON.parse(exportedCollectionJson);
const hasEnvVars = exported.variable && exported.variable.length > 0;

A Assert that <code>hasEnvVars</code> is true

B Assert that <code>exported.requests.length</code> is zero

C Assert that <code>exported.info.name</code> is undefined

D Assert that <code>exported.variable</code> is null

💡 Hint

Check if the variable property exists and has items.

The variable property in the exported collection JSON holds collection variables. If it exists and has length > 0, collection variables are included.

🔧 Debug

advanced

Troubleshooting Collection Import Failure

You try to import a Postman collection but receive an error 'Collection schema version not supported'. What is the most likely cause?

A The collection file is missing the <code>info</code> object

B The collection contains too many requests

C The file was exported from a different API testing tool

D The collection JSON uses an outdated or unsupported schema version

💡 Hint

Think about compatibility between Postman versions and collection formats.

Postman requires collections to follow supported schema versions (e.g., v2.1). Using an outdated or unsupported version causes import errors.

❓ framework

expert

Automating Collection Export with Newman CLI

Which Newman CLI command exports a collection run report in JSON format after executing tests?

A newman run collection.json -r json --reporter-json-export=report.json

B newman export collection.json --format json

C newman run collection.json --export-json report.json

D newman report collection.json --json report.json

💡 Hint

Look for the correct syntax to run a collection and export a JSON report using Newman.

The -r json option specifies the JSON reporter, and --reporter-json-export sets the output file for the report.