Local variables in Postman - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to set a local variable named 'token' with value 'abc123'.

Postman

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

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

Atoken

BglobalToken

Cenvironment

Dcollection

Attempts:

3 left

💡 Hint

Common Mistakes

Using environment or collection instead of local variable name.

Confusing local variables with global variables.

The local variable name should be 'token' to store the value locally within the request.

2fill in blank

medium

Complete the code to get the value of a local variable named 'sessionId'.

Postman

const session = pm.variables.get('[1]');

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

Atoken

BuserId

Cauth

DsessionId

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong variable names like 'token' or 'auth'.

Trying to get environment or global variables instead of local.

To retrieve a local variable, use pm.variables.get with the exact variable name, here 'sessionId'.

3fill in blank

hard

Fix the error in the code to correctly set a local variable 'userName' with value 'Alice'.

Postman

pm.variables.[1]('userName', 'Alice');

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

Aunset

Bget

Cset

Dclear

Attempts:

3 left

💡 Hint

Common Mistakes

Using pm.variables.get instead of set for assignment.

Using unset or clear which do not assign values.

To assign a value to a local variable, use pm.variables.set method.

4fill in blank

hard

Fill both blanks to check if a local variable 'count' exists and then delete it.

Postman

if (pm.variables.[1]('count') !== undefined) {
  pm.variables.[2]('count');
}

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

Aget

Bset

Cunset

Dclear

Attempts:

3 left

💡 Hint

Common Mistakes

Using pm.variables.set instead of get for checking existence.

Using clear instead of unset to delete variable.

Use pm.variables.get to check if 'count' exists, and pm.variables.unset to delete it.

5fill in blank

hard

Fill all three blanks to create a local variable 'status' with value 'active', then retrieve it and check if it equals 'active'.

Postman

pm.variables.[1]('status', 'active');
const currentStatus = pm.variables.[2]('status');
if (currentStatus [3] 'active') {
  console.log('Status is active');
}

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

Aset

Bget

C===

D!=

Attempts:

3 left

💡 Hint

Common Mistakes

Using != instead of === for comparison.

Using get to assign or set to retrieve.

First, set the variable with pm.variables.set, then get it with pm.variables.get, and compare using === for equality.

Practice

1. What is the main purpose of local variables in Postman?

easy

A. To create global environment settings

B. To save data permanently across all requests

C. To share data between different collections

D. To store data only during a single request execution

Solution

1. Step 1: Understand local variable scope

   Local variables exist only during the execution of one request and are not saved beyond that.

2. Step 2: Compare with other variable types

   Global or environment variables persist beyond one request, unlike local variables.

3. Final Answer:

   To store data only during a single request execution -> Option D

4. Quick Check:

   Local variables = single request scope [OK]

Hint: Local variables last only during one request [OK]

Common Mistakes:

• Confusing local variables with global variables
• Thinking local variables persist across requests
• Assuming local variables share data between collections

2. Which of the following is the correct syntax to set a local variable named token with value abc123 in Postman?

easy

A. pm.local.set('token', 'abc123');

B. pm.environment.set('token', 'abc123');

C. pm.variables.set('token', 'abc123');

D. pm.globals.set('token', 'abc123');

Solution

1. Step 1: Identify the correct method for local variables

   Local variables use pm.variables.set to assign values.

2. Step 2: Check other options for correctness

   pm.environment.set and pm.globals.set set environment and global variables, not local. pm.local.set is invalid.

3. Final Answer:

   pm.variables.set('token', 'abc123'); -> Option C

4. Quick Check:

   Set local variable = pm.variables.set [OK]

Hint: Use pm.variables.set() for local variables [OK]

Common Mistakes:

• Using pm.environment.set instead of pm.variables.set
• Trying to use pm.local.set which does not exist
• Confusing global and local variable methods

3. Consider this Postman test script:

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. 8

B. 5

C. Error: Cannot add number to undefined

D. null

Solution

1. Step 1: Set initial local variable 'count'

   The first line sets 'count' to 5.

2. Step 2: Increment 'count' by 3

   The second line gets 'count' (5), adds 3, and sets it back to 8.

3. Step 3: Output the updated value

   The console.log prints the current value of 'count', which is 8.

4. Final Answer:

   8 -> Option A

5. Quick Check:

   5 + 3 = 8 [OK]

Hint: Get then set to update local variable value [OK]

Common Mistakes:

• Assuming the variable does not update
• Expecting an error due to type mismatch
• Confusing local with environment variables

4. You wrote this Postman script:

pm.variables.set('user', 'Alice');
console.log(pm.variables.get('username'));

What is the problem here?

medium

A. Variable 'username' was never set, so get returns undefined

B. Syntax error in pm.variables.set method

C. Local variables cannot be logged to console

D. pm.variables.get requires two arguments

Solution

1. Step 1: Check variable names used

   The script sets 'user' but tries to get 'username', which was never set.

2. Step 2: Understand get behavior for unset variables

   Getting an unset local variable returns undefined, no error occurs.

3. Final Answer:

   Variable 'username' was never set, so get returns undefined -> Option A

4. Quick Check:

   Unset variable get = undefined [OK]

Hint: Check variable names carefully for typos [OK]

Common Mistakes:

• Assuming syntax error when variable name mismatches
• Thinking pm.variables.get needs two arguments
• Believing console.log cannot show local variables

5. You want to store a temporary token during a request and use it in multiple tests within that request. Which approach correctly uses local variables to achieve this?

hard

A. Set the token with pm.environment.set('token', 'abc') and get it with pm.variables.get('token')

B. Set the token once with pm.variables.set('token', 'abc') and get it in tests with pm.variables.get('token')

C. Set the token with pm.variables.set('token', 'abc') but cannot access it in other tests

D. Set the token with pm.globals.set('token', 'abc') and get it with pm.variables.get('token')

Solution

1. Step 1: Understand local variable scope within one request

   Local variables set with pm.variables.set are accessible throughout the request execution, including multiple tests.

2. Step 2: Verify correct get method usage

   Use pm.variables.get to retrieve the local variable value within the same request.

3. Step 3: Check other options for scope mismatch

   Environment and global variables persist beyond one request and are not local. Also, local variables are accessible across tests in the same request.

4. Final Answer:

   Set the token once with pm.variables.set('token', 'abc') and get it in tests with pm.variables.get('token') -> Option B

5. Quick Check:

   Local variable set/get works within one request [OK]

Hint: Use pm.variables.set/get to share data within one request [OK]

Common Mistakes:

• Using environment or global variables instead of local
• Thinking local variables cannot be shared between tests in one request
• Mixing set and get methods from different scopes