Why Global variables in Postman? - Purpose & Use Cases

The Big Idea

What if you could change one value and fix all your tests at once?

The Scenario

Imagine you are testing an API with many requests. Each request needs the same data, like a user token or a server URL. You write this data again and again in every request.

The Problem

This manual way is slow and tiring. If the token changes, you must update it in every request. You might forget some places, causing errors and confusion.

The Solution

Global variables let you store data once and use it everywhere. Change it once, and all requests get the update automatically. This saves time and avoids mistakes.

Before vs After

✗ Before

Set token in each request header manually.

✓ After

Use a global variable {{token}} in headers for all requests.

What It Enables

Global variables make your tests faster, cleaner, and easier to maintain across many requests.

Real Life Example

When testing a login API, you store the login token as a global variable. All other API calls use this token automatically without rewriting it.

Key Takeaways

Manual data repetition is slow and error-prone.

Global variables store data once for all requests.

They simplify updates and improve test reliability.

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