Variable scope and precedence in Postman - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to access the global variable in Postman test script.

Postman

pm.globals.set('token', 'abc123');
const tokenValue = pm.[1].get('token');

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

Aenvironment

Bglobals

Cvariables

DcollectionVariables

Attempts:

3 left

💡 Hint

Common Mistakes

Using pm.environment.get instead of pm.globals.get

Trying to access variables without pm object

The pm.globals object is used to access global variables in Postman scripts.

2fill in blank

medium

Complete the code to set an environment variable in Postman test script.

Postman

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

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

Aenvironment

Bglobals

Cvariables

DcollectionVariables

Attempts:

3 left

💡 Hint

Common Mistakes

Using pm.globals.set instead of pm.environment.set

Using pm.variables.set which sets local variables

Environment variables are set using pm.environment.set() in Postman scripts.

3fill in blank

hard

Fix the error in the code to correctly get a collection variable in Postman test script.

Postman

const apiKey = pm.[1].get('api_key');

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

AcollectionVariables

Benvironment

Cglobals

Dvariables

Attempts:

3 left

💡 Hint

Common Mistakes

Using pm.environment.get for collection variables

Using pm.globals.get for collection variables

Collection variables are accessed with pm.collectionVariables.get() in Postman.

4fill in blank

hard

Fill both blanks to correctly set and then get a local variable in Postman test script.

Postman

pm.variables.[1]('sessionId', 'sess_789');
const session = pm.variables.[2]('sessionId');

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

Aset

Bget

Cunset

Dclear

Attempts:

3 left

💡 Hint

Common Mistakes

Using pm.variables.unset to set a variable

Using pm.variables.clear to get a variable

Local variables in Postman are set with pm.variables.set() and accessed with pm.variables.get().

5fill in blank

hard

Fill all three blanks to create a test that checks if the environment variable 'status' equals 'active'.

Postman

const status = pm.[1].get('status');
pm.test('Status is active', function () {
  pm.expect(status).to.[2]([3]);
});

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

Aenvironment

Bequal

C'active'

Dglobals

Attempts:

3 left

💡 Hint

Common Mistakes

Using pm.globals.get instead of pm.environment.get

Using pm.expect().to.be instead of pm.expect().to.equal

Not quoting the string 'active'

The environment variable 'status' is accessed with pm.environment.get(). The test uses pm.expect().to.equal() to check the value against the string 'active'.

Practice

1. In Postman, which variable scope has the highest precedence when accessing a variable value?

easy

A. Global variables

B. Environment variables

C. Collection variables

D. Local variables

Solution

1. Step 1: Understand Postman variable scopes

   Postman has multiple variable scopes: local, environment, collection, and global.

2. Step 2: Identify precedence order

   Local variables override environment, collection, and global variables when accessing a variable.

3. Final Answer:

   Local variables -> Option D

4. Quick Check:

   Highest precedence = Local variables [OK]

Hint: Local variables always override others in Postman [OK]

Common Mistakes:

• Confusing environment variables as highest
• Thinking global variables override local
• Ignoring local scope existence

2. Which of the following is the correct way to set a local variable in a Postman test script?

easy

A. pm.variables.set('varName', 'value');

B. pm.environment.set('varName', 'value');

C. pm.collectionVariables.set('varName', 'value');

D. pm.globals.set('varName', 'value');

Solution

1. Step 1: Recall methods to set variables in Postman

   Local variables are set using pm.variables.set(). Environment, collection, and global variables use their respective methods.

2. Step 2: Match method to local variable scope

   pm.variables.set() sets a local variable for the current request or script.

3. Final Answer:

   pm.variables.set('varName', 'value'); -> Option A

4. Quick Check:

   Local variable set method = pm.variables.set() [OK]

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

Common Mistakes:

• Using pm.environment.set() for local variables
• Confusing collection and global variable setters
• Forgetting to use pm.variables for local scope

3. Given these variables set in Postman:
pm.environment.set('token', 'envToken');
pm.collectionVariables.set('token', 'colToken');
pm.variables.set('token', 'localToken');
What will pm.variables.get('token') return?

medium

A. 'envToken'

B. 'localToken'

C. 'colToken'

D. null

Solution

1. Step 1: Identify variable scopes and values

   Environment variable 'token' = 'envToken', collection variable 'token' = 'colToken', local variable 'token' = 'localToken'.

2. Step 2: Understand variable precedence when getting value

   pm.variables.get() returns the local variable value if set, ignoring environment and collection variables.

3. Final Answer:

   'localToken' -> Option B

4. Quick Check:

   Local variable value returned by pm.variables.get() [OK]

Hint: pm.variables.get() returns local variable if exists [OK]

Common Mistakes:

• Assuming environment variable is returned
• Confusing collection variable with local
• Expecting null if multiple scopes exist

4. You wrote this Postman test script:

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

But the console logs 'Alice' instead of 'Bob'. What is the issue?

medium

A. pm.environment.set() overwrites local variables

B. pm.variables.set() does not set local variables

C. pm.variables.get() should be used to get local variable

D. pm.environment.get() always reads environment variable ignoring local

Solution

1. Step 1: Analyze variable setting and getting methods

   pm.environment.set() sets environment variable; pm.variables.set() sets local variable. But pm.environment.get() reads environment variable only.

2. Step 2: Identify correct method to get local variable

   To get local variable, use pm.variables.get(), not pm.environment.get().

3. Final Answer:

   pm.variables.get() should be used to get local variable -> Option C

4. Quick Check:

   Use matching get method for variable scope [OK]

Hint: Use pm.variables.get() to read local variables [OK]

Common Mistakes:

• Using pm.environment.get() to read local variables
• Assuming set method affects all scopes
• Expecting pm.variables.set() to overwrite environment

5. You have a global variable 'count' set to '5'. In a collection run, you set a collection variable 'count' to '10'. In a pre-request script, you set a local variable 'count' to '15'. Which value will be used if your test script calls pm.variables.get('count') and why?

hard

A. '15' because local variables have highest precedence

B. '5' because global variables have highest precedence

C. '10' because collection variables override local variables

D. null because variable names conflict

Solution

1. Step 1: Review variable scopes and precedence

   Global variable 'count' = '5', collection variable 'count' = '10', local variable 'count' = '15'. Local variables override collection and global.

2. Step 2: Determine which value pm.variables.get() returns

   pm.variables.get() returns the local variable value if it exists, ignoring collection and global variables.

3. Final Answer:

   '15' because local variables have highest precedence -> Option A

4. Quick Check:

   Local variable value returned by pm.variables.get() [OK]

Hint: Local variables override collection and global variables [OK]

Common Mistakes:

• Thinking global variables override local
• Assuming collection variables override local
• Believing variable conflicts cause null