Variable scope and precedence in Postman

Introduction

Variable scope and precedence help you understand where your variables live and which value is used when multiple variables have the same name.

When you want to store and reuse data in different parts of your Postman tests.

When you have variables with the same name but different values in different places.

When debugging why a test uses an unexpected variable value.

When organizing your tests to keep data clean and avoid conflicts.

When sharing collections and environments with teammates.

Syntax

Postman

pm.variables.get('variableName')
pm.environment.get('variableName')
pm.collectionVariables.get('variableName')
pm.globals.get('variableName')

Postman variables have scopes: local (pm.variables), environment, collection, and global.

When resolving a variable with {{variableName}}, Postman checks scopes in this order: local → environment → collection → global.

Examples

Set and get a local variable in the current request or script.

Postman

pm.variables.set('userId', '123')
console.log(pm.variables.get('userId'))

Set and get an environment variable that is shared across requests in the same environment.

Postman

pm.environment.set('userId', '456')
console.log(pm.environment.get('userId'))

Set and get a collection variable that is shared across all requests in the collection.

Postman

pm.collectionVariables.set('userId', '789')
console.log(pm.collectionVariables.get('userId'))

Set and get a global variable that is available in all collections and environments.

Postman

pm.globals.set('userId', '000')
console.log(pm.globals.get('userId'))

Sample Program

This script sets a variable named 'var' in all scopes with different values. When we get 'var' using pm.variables.get(), it returns the local scope value because local has the highest precedence.

Postman

// Set variables in different scopes
pm.globals.set('var', 'global')
pm.collectionVariables.set('var', 'collection')
pm.environment.set('var', 'environment')
pm.variables.set('var', 'local')

// Get variable without specifying scope
console.log(pm.variables.get('var'))

Important Notes

Local variables exist only during the request or script execution.

Environment variables change when you switch environments in Postman.

Collection and global variables persist until you change or delete them.

Summary

Postman variables have scopes: local, environment, collection, and global.

When accessing a variable, Postman uses the value from the highest precedence scope available.

Understanding scope helps avoid confusion and bugs in your tests.

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