Variable assignment in flows in Postman - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to assign a variable named userId with the value 12345 in Postman script.

Postman

pm.variables.set('userId', [1]);

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

A"userId"

B12345

C'12345'

DuserId

Attempts:

3 left

💡 Hint

Common Mistakes

Forgetting quotes around the string value.

Using variable name instead of value.

In Postman scripts, to assign a string value to a variable, you must put the value in quotes. So '12345' is correct.

2fill in blank

medium

Complete the code to retrieve the variable sessionToken from Postman environment variables.

Postman

const token = pm.environment.get([1]);

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

AsessionToken

B'sessionToken'

C"token"

Dtoken

Attempts:

3 left

💡 Hint

Common Mistakes

Not using quotes around the variable name.

Using a different variable name.

When getting a variable in Postman, the variable name must be a string, so it needs quotes.

3fill in blank

hard

Fix the error in the code to correctly set a global variable count to 10.

Postman

pm.globals.set('count', [1]);

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

A10

B"count"

C'10'

Dcount

Attempts:

3 left

💡 Hint

Common Mistakes

Putting numbers inside quotes making them strings.

Using variable name instead of value.

Global variables can hold numbers directly without quotes. Using 10 sets the number correctly.

4fill in blank

hard

Fill both blanks to create a local variable status with value active and then retrieve it.

Postman

pm.variables.set([1], [2]);
const currentStatus = pm.variables.get('status');

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

A'status'

B'active'

Cstatus

Dactive

Attempts:

3 left

💡 Hint

Common Mistakes

Not using quotes for variable name or value.

Using variable names without quotes.

Variable names and string values must be in quotes. So 'status' and 'active' are correct.

5fill in blank

hard

Fill all three blanks to set an environment variable userRole to admin, then get it and check if it equals admin.

Postman

pm.environment.set([1], [2]);
const role = pm.environment.get('userRole');
pm.test('Role is admin', () => pm.expect(role).to.eql([3]));

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

A'userRole'

B'admin'

C"admin"

Dadmin

Attempts:

3 left

💡 Hint

Common Mistakes

Not quoting variable names or values.

Using unquoted values in the test assertion.

Variable names and string values must be quoted. For the test assertion, double quotes or single quotes work, here double quotes are used.

Practice

1. What does pm.variables.set('token', 'abc123') do in a Postman test script?

easy

A. It saves the value 'abc123' to a variable named 'token' for later use.

B. It retrieves the value of the variable 'token'.

C. It deletes the variable named 'token'.

D. It sends 'abc123' as a request header named 'token'.

Solution

1. Step 1: Understand the method pm.variables.set

   This method assigns a value to a variable in Postman scripts.

2. Step 2: Analyze the parameters

   The first parameter is the variable name 'token', the second is the value 'abc123' to store.

3. Final Answer:

   It saves the value 'abc123' to a variable named 'token' for later use. -> Option A

4. Quick Check:

   pm.variables.set saves data [OK]

Hint: Set stores data; get retrieves it [OK]

Common Mistakes:

• Confusing set with get method
• Thinking set deletes variables
• Assuming set sends data in requests

2. Which of the following is the correct syntax to assign a variable named 'userId' with value 42 in a Postman test script?

easy

A. pm.variables.get('userId', 42);

B. pm.variables.store('userId', 42);

C. pm.variables.assign('userId' = 42);

D. pm.variables.set('userId', 42);

Solution

1. Step 1: Recall the correct method for assigning variables

   The method to assign a variable is pm.variables.set(name, value).

2. Step 2: Check each option's syntax

   pm.variables.set('userId', 42); uses pm.variables.set('userId', 42); which is correct syntax.

3. Final Answer:

   pm.variables.set('userId', 42); -> Option D

4. Quick Check:

   Use pm.variables.set to assign [OK]

Hint: Set method assigns variables with (name, value) [OK]

Common Mistakes:

• Using get instead of set to assign
• Incorrect method names like assign or store
• Wrong parameter syntax with equals sign

3. Consider this Postman test script snippet:

pm.variables.set('count', 5);
pm.variables.set('count', pm.variables.get('count') + 3);
console.log(pm.variables.get('count'));

What will be printed in the console?

medium

A. 5

B. 8

C. Error

D. undefined

Solution

1. Step 1: Analyze the first assignment

   The variable 'count' is set to 5 initially.

2. Step 2: Analyze the second assignment

   It gets the current 'count' value (5), adds 3, and sets 'count' to 8.

3. Step 3: Check the console.log output

   It prints the updated value of 'count', which is 8.

4. Final Answer:

   8 -> Option B

5. Quick Check:

   5 + 3 = 8 [OK]

Hint: Get current value, add, then set updated value [OK]

Common Mistakes:

• Assuming the first value stays unchanged
• Thinking get returns undefined
• Confusing set and get usage

4. You wrote this Postman test script:

pm.variables.set('status', 'active')
pm.variables.get('status')

But the test fails because the variable 'status' is undefined. What is the likely cause?

medium

A. Variables set in one request are not available in another without environment or global scope.

B. pm.variables.get returns undefined if set is not awaited.

C. Missing semicolon after set statement causes failure.

D. Variable names cannot be strings.

Solution

1. Step 1: Understand variable scopes in Postman

   Variables set with pm.variables.set are local to the current request script and do not persist across requests.

2. Step 2: Identify why 'status' is undefined

   If you try to get 'status' in a different request without using environment or global variables, it will be undefined.

3. Final Answer:

   Variables set in one request are not available in another without environment or global scope. -> Option A

4. Quick Check:

   Local variables don't persist across requests [OK]

Hint: Use environment/global variables for cross-request data [OK]

Common Mistakes:

• Thinking semicolons affect variable persistence
• Believing get waits for set automatically
• Assuming variable names can't be strings

5. You want to save a user token from a response JSON and reuse it in the next request. Which flow correctly assigns and retrieves the token using Postman variables?

hard

A. In first request test script: pm.variables.set('token', pm.response.json().token);In next request pre-request script: const token = pm.environment.get('token');

B. In first request test script: pm.variables.set('token', pm.response.json().token);In next request pre-request script: const token = pm.variables.get('token');

C. In first request test script: pm.environment.set('token', pm.response.json().token);In next request pre-request script: const token = pm.environment.get('token');

D. In first request test script: pm.environment.set('token', pm.response.json().token);In next request pre-request script: const token = pm.variables.get('token');

Solution

1. Step 1: Identify variable scope for cross-request use

   To reuse data across requests, environment variables must be used, not local variables.

2. Step 2: Match correct set and get methods

   In first request test script: pm.environment.set('token', pm.response.json().token);
   In next request pre-request script: const token = pm.environment.get('token'); uses pm.environment.set and pm.environment.get, which correctly share data between requests.

3. Final Answer:

   Use environment variables to save and retrieve token across requests. -> Option C

4. Quick Check:

   Environment variables persist across requests [OK]

Hint: Use environment variables for data between requests [OK]

Common Mistakes:

• Using pm.variables for cross-request data
• Mixing environment and local variable methods
• Not retrieving variables in the correct scope