Data file integration (CSV, JSON) in Postman - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output of this Postman test script when using a CSV data file?

Given this test script in Postman that runs with a CSV data file containing two rows:

pm.test('Check user ID', () => {
    pm.expect(pm.iterationData.get('userId')).to.be.oneOf(['101', '102']);
});

What will be the result after running the collection with this CSV data?

Postman

pm.test('Check user ID', () => {
    pm.expect(pm.iterationData.get('userId')).to.be.oneOf(['101', '102']);
});

A The test throws a runtime error due to invalid syntax.

B The test fails because pm.iterationData.get does not work with CSV files.

C The test passes twice, once for each userId in the CSV file.

D The test passes only once, ignoring the second CSV row.

💡 Hint

Think about how Postman runs tests for each row in a data file.

Postman runs the test script once per data row. Since the CSV has two rows with userId values '101' and '102', and the test checks if the userId is one of these, the test passes twice.

❓ assertion

intermediate

Which assertion correctly verifies a JSON data file value in Postman?

You have a JSON data file with entries like {"username": "alice"}. Which assertion in the test script correctly checks that the username is 'alice' for the current iteration?

A pm.expect(pm.iterationData.username).to.equal('alice');

B pm.expect(pm.iterationData.get('username')).to.eql('alice');

C pm.expect(pm.data.username).to.equal('alice');

D pm.expect(pm.data.get('username')).to.eql('alice');

💡 Hint

Remember the method to get data from the current iteration in Postman.

pm.iterationData.get('key') is the correct way to access data from the current iteration, regardless of CSV or JSON data files.

🔧 Debug

advanced

Why does this Postman test fail when using a JSON data file?

Consider this test script:

pm.test('Check email', () => {
    pm.expect(pm.iterationData.email).to.include('@');
});

When running with a JSON data file containing emails, the test always fails. What is the cause?

Postman

pm.test('Check email', () => {
    pm.expect(pm.iterationData.email).to.include('@');
});

A pm.iterationData is a method, so pm.iterationData.email is undefined causing the test to fail.

B The test syntax is invalid because include() is not a valid assertion method.

C The JSON data file is malformed, so pm.iterationData cannot read email.

D pm.iterationData.email is correct, but the email values do not contain '@'.

💡 Hint

Check how to properly access iteration data in Postman scripts.

pm.iterationData is a method object, not a plain object. You must use pm.iterationData.get('email') to access the value. Using pm.iterationData.email returns undefined, causing the assertion to fail.

❓ framework

advanced

How to configure Postman to run a collection with a JSON data file?

Which step correctly describes how to run a Postman collection using a JSON data file?

A In the Collection Runner, select the collection, click 'Select File', choose the JSON file, then click 'Run'.

B Import the JSON file as a new collection, then run it directly without selecting a data file.

C Attach the JSON file in the request body and run the collection normally.

D Convert the JSON file to CSV first, then use the Collection Runner to select the CSV file.

💡 Hint

Think about how Postman uses data files in the Collection Runner.

Postman Collection Runner allows you to select a data file (CSV or JSON) to run the collection multiple times with different data. You select the file in the runner before starting.

🧠 Conceptual

expert

What is the main difference in handling CSV vs JSON data files in Postman tests?

When using CSV and JSON data files in Postman Collection Runner, what is the key difference in how data is accessed in test scripts?

A CSV data must be converted to JSON before use; JSON data can be used directly.

B CSV data requires pm.iterationData.get('key'), but JSON data uses pm.data.key directly.

C CSV data is accessed by index, JSON data by key name in pm.iterationData.

D There is no difference; both use pm.iterationData.get('key') to access values.

💡 Hint

Consider the Postman API for accessing iteration data regardless of file type.

Postman abstracts data file format differences. Both CSV and JSON data files are accessed in test scripts using pm.iterationData.get('key').

Practice

1. What is the main purpose of using data files like CSV or JSON in Postman's Collection Runner?

easy

A. To run the same test multiple times with different input data

B. To create new APIs automatically

C. To change the Postman interface theme

D. To store test results permanently

Solution

1. Step 1: Understand data file role in Postman

   Data files provide different sets of input data for tests.

2. Step 2: Connect data files to Collection Runner

   Collection Runner uses these files to repeat tests with varied inputs.

3. Final Answer:

   To run the same test multiple times with different input data -> Option A

4. Quick Check:

   Data files = multiple test runs [OK]

Hint: Data files feed tests with many inputs [OK]

Common Mistakes:

• Thinking data files create APIs
• Confusing data files with UI settings
• Assuming data files store results

2. Which of the following is the correct way to reference a CSV data file variable named username in a Postman test script?

easy

A. pm.variables.get('username')

B. pm.data.username

C. pm.iterationData.get('username')

D. pm.request.body.username

Solution

1. Step 1: Identify how Postman accesses data file variables

   Postman uses pm.iterationData.get('variableName') to get data from CSV or JSON files.

2. Step 2: Match the correct syntax for username

   The correct method is pm.iterationData.get('username').

3. Final Answer:

   pm.iterationData.get('username') -> Option C

4. Quick Check:

   Use pm.iterationData.get() for data file variables [OK]

Hint: Use pm.iterationData.get('var') for CSV/JSON data [OK]

Common Mistakes:

• Using pm.variables.get() which accesses environment variables
• Trying to access data as object properties
• Confusing request body with data file variables

3. Given this CSV data file content:

email,password
[e-mail],pass123
[e-mail],pass456

And this test script snippet:

const email = pm.iterationData.get('email');
const password = pm.iterationData.get('password');
pm.test('Check email format', () => {
  pm.expect(email).to.include('@');
});

What will be the result of running the Collection Runner with this data file?

medium

A. Both iterations pass the test

B. Both iterations fail the test

C. First iteration passes, second fails

D. Test throws a syntax error

Solution

1. Step 1: Analyze CSV data values

   Both emails contain '@' symbol: '[e-mail]' and '[e-mail]'.

2. Step 2: Check test condition for each iteration

   The test checks if email includes '@', which is true for both rows.

3. Final Answer:

   Both iterations pass the test -> Option A

4. Quick Check:

   Email includes '@' = true for all data [OK]

Hint: Check data values against test condition carefully [OK]

Common Mistakes:

• Assuming test fails without checking data
• Confusing syntax error with logic error
• Ignoring multiple iterations in Collection Runner

4. You have a JSON data file with this content:

[
  {"user": "alice", "age": 30},
  {"user": "bob", "age": "twenty-five"}
]

When running tests that expect age to be a number, you get unexpected failures. What is the most likely cause?

medium

A. The JSON file is not properly formatted

B. The second age value is a string, not a number

C. Postman cannot read JSON files

D. The test script is missing pm.iterationData.get()

Solution

1. Step 1: Inspect JSON data values

   The first age is 30 (number), second is "twenty-five" (string).

2. Step 2: Understand test expectation

   Tests expect age to be a number, but second value is text, causing failure.

3. Final Answer:

   The second age value is a string, not a number -> Option B

4. Quick Check:

   Data type mismatch causes test failure [OK]

Hint: Check data types in JSON carefully [OK]

Common Mistakes:

• Assuming JSON format is invalid
• Blaming Postman for reading JSON
• Ignoring data type differences

5. You want to run a Postman test that uses a JSON data file with nested objects like:

[
  {"user": {"name": "John", "id": 101}, "active": true},
  {"user": {"name": "Jane", "id": 102}, "active": false}
]

Which is the correct way to access the name property inside the test script?

hard

A. pm.iterationData.get('user').get('name')

B. pm.iterationData['user']['name']

C. pm.iterationData.get('user.name')

D. pm.iterationData.get('user').name

Solution

1. Step 1: Understand how Postman accesses nested JSON data

   Postman requires getting the parent object first with pm.iterationData.get('user'), then access nested properties using JavaScript dot notation.

2. Step 2: Identify correct syntax for nested property

   Using pm.iterationData.get('user').name correctly accesses the nested name.

3. Final Answer:

   pm.iterationData.get('user').name -> Option D

4. Quick Check:

   Get parent object first, then .name [OK]

Hint: Get parent object first, then .name [OK]

Common Mistakes:

• Trying to access nested objects as JS objects directly
• Using .get() on returned object
• Using bracket notation inside pm.iterationData.get()