Variable scope and precedence in Postman - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Variable Scope in Postman

In Postman, variables can exist at different scopes: Global, Collection, Environment, and Local (within a request). Which variable scope has the highest precedence when resolving a variable name during a request execution?

A Global variables

B Environment variables

C Collection variables

D Local variables

💡 Hint

Think about which variable is closest to the request itself.

Local variables defined within a request have the highest precedence because they are the closest to the request execution context. Postman resolves variables starting from local, then collection, environment, and finally global.

❓ Predict Output

intermediate

Output of Variable Resolution in Postman Script

Given the following Postman pre-request script and variable scopes, what will be the value of pm.variables.get('token') during the request execution?

Global variable token = "global123"

Environment variable token = "env456"

Collection variable token = "col789"

Pre-request script:

Postman

pm.variables.set('token', 'local000');
console.log(pm.variables.get('token'));

A "local000"

B "env456"

C "col789"

D "global123"

💡 Hint

Variables set in the script override other scopes.

Setting a variable with pm.variables.set creates a local variable for the request, which has the highest precedence. Therefore, pm.variables.get('token') returns "local000".

❓ assertion

advanced

Correct Assertion for Variable Value in Postman Test

You want to assert that the variable userId used in your request is the environment variable value, not a local or global one. Which assertion correctly verifies this in the test script?

A pm.test('userId is environment variable', () => pm.expect(pm.variables.get('userId')).to.eql(pm.environment.get('userId')));

B pm.test('userId is environment variable', () => pm.expect(pm.variables.get('userId')).to.eql(pm.global.get('userId')));

C pm.test('userId is environment variable', () => pm.expect(pm.environment.get('userId')).to.eql(pm.variables.get('userId')));

D pm.test('userId is environment variable', () => pm.expect(pm.environment.get('userId')).to.eql(pm.global.get('userId')));

💡 Hint

Remember that pm.variables.get() returns the variable value with precedence applied.

pm.variables.get('userId') returns the variable value considering all scopes with precedence. To verify it matches the environment variable, you compare pm.variables.get('userId') to pm.environment.get('userId'). Option A does this correctly.

🔧 Debug

advanced

Debugging Variable Precedence Issue in Postman

You have a collection variable apiKey set to "colKey" and an environment variable apiKey set to "envKey". Your request script uses pm.variables.get('apiKey') but always returns "colKey" instead of "envKey". What is the most likely reason?

A Local variables override all, so a local variable named "apiKey" must exist with value "colKey".

B Environment variables have higher precedence than collection variables, so "envKey" should be returned but there's a bug.

C Collection variables have higher precedence than environment variables, so "colKey" is returned.

D Global variables override both collection and environment variables, causing "colKey" to appear.

💡 Hint

Check the Postman variable precedence order.

Postman resolves variables in this order: local, collection, environment, global. Since collection variables have higher precedence than environment variables, pm.variables.get('apiKey') returns the collection variable value "colKey".

❓ framework

expert

Order of Variable Resolution in Postman

Arrange the following Postman variable scopes in the order Postman uses to resolve a variable name, from highest precedence to lowest.

A 1, 2, 3, 4

B 4, 3, 2, 1

C 3, 4, 2, 1

D 2, 3, 4, 1

💡 Hint

Think about which variables are closest to the request execution context.

Postman resolves variables starting from local (set in scripts), then collection, environment, and finally global variables. This order ensures the most specific variable is used.