Data file integration (CSV, JSON) in Postman - Test Execution Trace

Test Overview

This test runs a Postman collection using a CSV data file to send multiple requests with different user data. It verifies that the API responds with status 200 for each user.

Test Code - Postman

Postman

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

Execution Trace - 8 Steps

Step	Action	System State	Assertion	Result
1	Test collection run starts with CSV data file containing multiple user records	Postman Runner opens and loads CSV file with user data rows	—	PASS
2	Postman sends first request using first row data from CSV (e.g., userId=1, name='Alice')	Request URL and body populated with first user data	—	PASS
3	Postman receives response for first request	Response status 200 and valid JSON body received	Check response status is 200	PASS
4	Postman runs test script to assert status code 200	Test script executed in Postman sandbox	pm.test('Status code is 200', function () { pm.response.to.have.status(200); });	PASS
5	Postman sends second request using second row data from CSV (e.g., userId=2, name='Bob')	Request URL and body populated with second user data	—	PASS
6	Postman receives response for second request	Response status 200 and valid JSON body received	Check response status is 200	PASS
7	Postman runs test script to assert status code 200 for second request	Test script executed in Postman sandbox	pm.test('Status code is 200', function () { pm.response.to.have.status(200); });	PASS
8	Postman completes all requests from CSV data file	All rows processed, test results collected	All requests returned status 200	PASS

Failure Scenario

Failing Condition: API returns status other than 200 for any user data row

Execution Trace Quiz - 3 Questions

What does Postman use the CSV data file for in this test?

A To run the same request multiple times with different data

B To store test scripts

C To save response bodies

D To configure Postman settings

Key Result

Using data files in Postman allows running the same test with many inputs easily, improving test coverage and saving time.

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()