Global variables in Postman - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Postman Global Variables Scope

In Postman, where are global variables accessible?

A Across all collections and requests in the current Postman workspace

B Only within the current request and its scripts

C Only within the current collection

D Only within the current environment

💡 Hint

Think about variables that are shared everywhere in Postman.

Global variables in Postman are accessible across all collections and requests within the workspace, unlike environment variables which are limited to a specific environment.

❓ Predict Output

intermediate

Output of Setting and Getting a Global Variable

What will be the output of the following Postman test script?

Postman

pm.globals.set('token', 'abc123');
const token = pm.globals.get('token');
console.log(token);

A abc123

B undefined

C null

D Error: pm.globals is not defined

💡 Hint

Consider what value is stored and then retrieved.

The script sets the global variable 'token' to 'abc123' and then retrieves it. The console.log will output 'abc123'.

❓ assertion

advanced

Correct Assertion for Global Variable Value

Which assertion correctly verifies that the global variable 'userId' equals '42' in a Postman test script?

Postman

const userId = pm.globals.get('userId');

A pm.test('User ID is 42', () => pm.expect(userId).to.eql(42));

B pm.test('User ID is 42', () => pm.expect(userId).to.be(42));

C pm.test('User ID is 42', () => pm.expect(userId).to.equal('42'));

D pm.test('User ID is 42', () => pm.expect(userId).toBe('42'));

💡 Hint

Remember the type of the value returned by pm.globals.get.

pm.globals.get returns a string, so the assertion must compare to the string '42' using .to.equal().

🔧 Debug

advanced

Debugging Global Variable Not Updating

A tester sets a global variable in the Pre-request Script using pm.globals.set('session', 'xyz'), but in the Tests script, pm.globals.get('session') returns undefined. What is the most likely cause?

A The variable was deleted before the Tests script runs

B Global variables cannot be set in Pre-request Scripts

C The Tests script runs before the Pre-request Script

D The variable name is misspelled in the Tests script

💡 Hint

Check spelling carefully in both scripts.

If the variable name is misspelled in the Tests script, pm.globals.get will return undefined because it looks for a different variable.

❓ framework

expert

Best Practice for Managing Global Variables in Postman Collections

Which approach is best to avoid conflicts and ensure maintainability when using global variables across multiple Postman collections?

A Use generic global variable names like 'token' or 'id' for all collections

B Prefix global variable names with collection-specific identifiers, e.g., 'coll1_token'

C Set and delete global variables dynamically in each request without naming conventions

D Avoid using global variables and use only environment variables instead

💡 Hint

Think about how to prevent variable name clashes.

Prefixing global variable names with collection-specific identifiers helps prevent conflicts and improves clarity when multiple collections use global variables.

Practice

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

easy

A. To store data accessible across all requests and tests

B. To store data only for the current request

C. To create temporary variables that disappear after one test

D. To define environment-specific settings

Solution

1. Step 1: Understand global variable scope

   Global variables in Postman are accessible everywhere, across all requests and tests.

2. Step 2: Compare with other variable types

   Unlike environment or local variables, global variables persist and are shared globally.

3. Final Answer:

   To store data accessible across all requests and tests -> Option A

4. Quick Check:

   Global variables = accessible everywhere [OK]

Hint: Global variables are shared everywhere in Postman [OK]

Common Mistakes:

• Confusing global variables with environment variables
• Thinking global variables are temporary
• Assuming global variables are request-specific

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

easy

A. pm.globals.add('token', 'abc123');

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

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

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

Solution

1. Step 1: Recall correct Postman global variable syntax

   The correct method to set a global variable is pm.globals.set(key, value).

2. Step 2: Identify the correct object and method

   Only pm.globals.set('token', 'abc123'); uses pm.globals.set correctly with proper quotes and parameters.

3. Final Answer:

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

4. Quick Check:

   Use pm.globals.set to set global variables [OK]

Hint: Use pm.globals.set('key', 'value') to set globals [OK]

Common Mistakes:

• Using pm.global instead of pm.globals
• Using .add instead of .set method
• Incorrect object names like pm.globalVariables

3. Consider this Postman test script:

pm.globals.set('userId', '42');
const id = pm.globals.get('userId');
console.log(id);

What will be printed in the Postman console?

medium

A. undefined

B. 42

C. userId

D. null

Solution

1. Step 1: Set global variable 'userId' to '42'

   The first line stores the string '42' in the global variable named 'userId'.

2. Step 2: Retrieve and log the global variable

   The second line gets the value of 'userId' which is '42', then logs it.

3. Final Answer:

   42 -> Option B

4. Quick Check:

   pm.globals.get('userId') returns '42' [OK]

Hint: pm.globals.get returns the stored value [OK]

Common Mistakes:

• Expecting variable name instead of value
• Confusing undefined with null
• Forgetting to set the variable before getting

4. You wrote this Postman script to set a global variable:

pm.globals.set(userId, '100');

But it throws an error. What is the problem?

medium

A. The variable name userId should be a string in quotes

B. pm.globals.set cannot set numeric values

C. pm.globals.set requires three arguments

D. Global variables cannot be set inside scripts

Solution

1. Step 1: Check the syntax of pm.globals.set

   The first argument must be a string key, so it should be quoted like 'userId'.

2. Step 2: Identify the error cause

   Without quotes, userId is treated as an undefined variable causing an error.

3. Final Answer:

   The variable name userId should be a string in quotes -> Option A

4. Quick Check:

   Keys must be strings in pm.globals.set [OK]

Hint: Always quote variable names in pm.globals.set [OK]

Common Mistakes:

• Not quoting the key name
• Thinking pm.globals.set needs more arguments
• Believing global variables can't be set in scripts

5. You want to share a session token between multiple requests in Postman using global variables. Which sequence correctly sets and retrieves the token?

// Request 1
pm.globals.set('sessionToken', 'xyz789');

// Request 2
const token = pm.globals.get('sessionToken');
console.log(token);

hard

A. You must use environment variables instead of global variables

B. You need to pass the token as a parameter, not use globals

C. pm.globals.get cannot retrieve variables set in other requests

D. This sequence correctly shares the token globally

Solution

1. Step 1: Set global variable in first request

   The first request sets 'sessionToken' globally using pm.globals.set.

2. Step 2: Retrieve global variable in second request

   The second request gets the same 'sessionToken' using pm.globals.get and logs it.

3. Final Answer:

   This sequence correctly shares the token globally -> Option D

4. Quick Check:

   Global variables share data across requests [OK]

Hint: Set in one request, get in another using pm.globals [OK]

Common Mistakes:

• Thinking globals can't share data between requests
• Confusing environment and global variables
• Trying to pass token manually instead of using variables