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.

Practice

1. What is the main purpose of importing a collection in Postman?

easy

A. To add existing API tests into Postman for use

B. To delete all current tests in Postman

C. To export tests to a JSON file

D. To create a new API from scratch

Solution

1. Step 1: Understand importing collections

   Importing collections means bringing existing API tests into Postman so you can use or modify them.

2. Step 2: Differentiate from exporting and creating

   Exporting saves tests out of Postman, and creating new APIs is different from importing.

3. Final Answer:

   To add existing API tests into Postman for use -> Option A

4. Quick Check:

   Import = Add existing tests [OK]

Hint: Import means bringing tests in, not creating or deleting [OK]

Common Mistakes:

• Confusing import with export
• Thinking import deletes tests
• Assuming import creates new APIs

2. Which file format is used when exporting a collection from Postman?

easy

A. .xml

B. .csv

C. .json

D. .txt

Solution

1. Step 1: Identify export file format

   Postman exports collections as JSON files, which store structured data about API tests.

2. Step 2: Exclude other formats

   XML, TXT, and CSV are not used by Postman for exporting collections.

3. Final Answer:

   .json -> Option C

4. Quick Check:

   Exported collections use JSON files [OK]

Hint: Postman collections export as JSON files only [OK]

Common Mistakes:

• Choosing XML or CSV instead of JSON
• Confusing export format with import options
• Assuming text files are used

3. You exported a collection from Postman and shared the JSON file. Your teammate imports it but sees no requests. What is the likely cause?

medium

A. Postman does not support importing JSON files

B. The JSON file was empty or corrupted

C. The teammate did not restart Postman after import

D. The collection was exported in XML format

Solution

1. Step 1: Check file integrity

   If the imported collection shows no requests, the JSON file might be empty or corrupted, causing no data to load.

2. Step 2: Verify import support and format

   Postman supports JSON imports, and restarting is not required. Exporting in XML is not possible, so that is invalid.

3. Final Answer:

   The JSON file was empty or corrupted -> Option B

4. Quick Check:

   Empty/corrupt JSON causes no requests on import [OK]

Hint: Empty or broken JSON files cause empty imports [OK]

Common Mistakes:

• Thinking Postman can't import JSON
• Assuming restart is needed after import
• Believing XML export is possible

4. You tried to export a collection but the export button is disabled. What should you check to fix this?

medium

A. Ensure a collection is selected in Postman

B. Restart your computer immediately

C. Change the export file format to XML

D. Uninstall and reinstall Postman

Solution

1. Step 1: Verify collection selection

   The export button is disabled if no collection is selected. Selecting a collection enables export.

2. Step 2: Exclude unnecessary actions

   Restarting, changing to XML (unsupported), or reinstalling are not needed to enable export.

3. Final Answer:

   Ensure a collection is selected in Postman -> Option A

4. Quick Check:

   Export button needs a selected collection [OK]

Hint: Select a collection first to enable export button [OK]

Common Mistakes:

• Trying unsupported XML format
• Restarting unnecessarily
• Reinstalling Postman without checking selection

5. You want to share a set of API tests with a teammate who uses Postman. Which steps correctly describe exporting and importing the collection?

hard

A. Copy the collection URL, teammate pastes it in browser to import

B. Export the collection as CSV, send the file, teammate imports CSV in Postman

C. Export the collection as XML, send the file, teammate imports XML in Postman

D. Export the collection as JSON, send the file, teammate imports JSON in Postman

Solution

1. Step 1: Export collection as JSON

   Postman exports collections only as JSON files for sharing or backup.

2. Step 2: Teammate imports JSON file

   The teammate imports the JSON file into their Postman app to get the same tests.

3. Final Answer:

   Export the collection as JSON, send the file, teammate imports JSON in Postman -> Option D

4. Quick Check:

   Export and import use JSON files [OK]

Hint: Always export/import collections as JSON files [OK]

Common Mistakes:

• Using CSV or XML formats
• Thinking URL copy imports collections
• Skipping export step