Why Setting variables in scripts in Postman? - Purpose & Use Cases

The Big Idea

Discover how a simple script trick can save you hours of tedious copying and prevent frustrating test failures!

The Scenario

Imagine testing an API where you must reuse values like tokens or IDs across many requests. Manually copying and pasting these values each time is like writing down a phone number on sticky notes and losing them everywhere.

The Problem

Manually updating values is slow and easy to mess up. You might paste the wrong token or forget to update an ID, causing tests to fail without clear reasons. It's like trying to remember multiple passwords without a manager--stressful and error-prone.

The Solution

Setting variables in scripts lets you store and reuse values automatically. Your script can save a token once and use it everywhere, like having a smart assistant who remembers and fills in details for you perfectly every time.

Before vs After

✗ Before

pm.environment.set('token', 'abc123');
pm.environment.set('userId', '789');

✓ After

pm.environment.set('token', pm.response.json().token);
pm.environment.set('userId', pm.response.json().user.id);

What It Enables

This makes your tests faster, more reliable, and easier to maintain by automating value sharing across requests.

Real Life Example

When testing a login API, you can save the returned token in a variable and use it automatically in all following requests without typing it again.

Key Takeaways

Manual copying of values is slow and error-prone.

Scripts can store variables to reuse values automatically.

This improves test speed, accuracy, and maintenance.

Practice

1. What is the purpose of using pm.variables.set in Postman scripts?

easy

A. To store a value in a local variable for later use within the same request

B. To send a request to the server

C. To delete a variable from the environment

D. To log information to the console

Solution

1. Step 1: Understand the function of pm.variables.set

   This function stores a value in a local variable that can be used later in the same request or script.

2. Step 2: Differentiate from other actions

   Sending requests, deleting variables, or logging are done by other methods, not pm.variables.set.

3. Final Answer:

   To store a value in a local variable for later use within the same request -> Option A

4. Quick Check:

   pm.variables.set stores local variables [OK]

Hint: Remember: set means save value locally in script [OK]

Common Mistakes:

• Confusing variable setting with sending requests
• Thinking it deletes variables
• Assuming it logs output

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

easy

A. pm.variables.set['token', 'abc123'];

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

C. pm.variables.set('token' = 'abc123');

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

Solution

1. Step 1: Check the correct method signature

   The correct syntax uses pm.variables.set('variableName', 'value'); with the variable name as a string and value as the second argument.

2. Step 2: Identify syntax errors in other options

   pm.variables.set(token, 'abc123'); misses quotes around the variable name. pm.variables.set('token' = 'abc123'); uses an invalid assignment inside the method. pm.variables.set['token', 'abc123']; uses incorrect bracket notation.

3. Final Answer:

   pm.variables.set('token', 'abc123'); -> Option D

4. Quick Check:

   Use quotes for variable name in pm.variables.set [OK]

Hint: Variable names must be strings in quotes [OK]

Common Mistakes:

• Omitting quotes around variable names
• Using assignment inside set method
• Using wrong brackets for method call

3. Consider this Postman test script snippet:

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

What will be printed in the Postman console?

medium

A. 42

B. undefined

C. '42'

D. null

Solution

1. Step 1: Understand variable setting and getting

   The script sets 'userId' to the number 42, then retrieves it with pm.variables.get.

2. Step 2: Check the console output

   The retrieved value is 42 (a number), so console.log(id); prints 42 without quotes.

3. Final Answer:

   42 -> Option A

4. Quick Check:

   Set and get return the same stored value [OK]

Hint: Get returns exactly what was set, including type [OK]

Common Mistakes:

• Assuming get returns string always
• Expecting undefined if variable not set
• Confusing quotes in console output

4. You wrote this Postman script:

pm.variables.set('session', 'abc');
pm.variables.get('session');

But the variable session is not accessible in later requests. What is the likely problem?

medium

A. You must call pm.variables.save() to save variables

B. You should use pm.environment.set to make it accessible across requests

C. Variable names cannot be strings

D. You need to restart Postman to apply changes

Solution

1. Step 1: Understand variable scopes in Postman

   pm.variables.set sets a local variable only for the current script execution, not across requests.

2. Step 2: Use environment variables for persistence

   To keep variables accessible across requests, use pm.environment.set instead.

3. Final Answer:

   You should use pm.environment.set to make it accessible across requests -> Option B

4. Quick Check:

   Local variables are temporary; environment variables persist [OK]

Hint: Use environment.set for cross-request variables [OK]

Common Mistakes:

• Expecting pm.variables.set to persist across requests
• Thinking a save method is needed
• Believing variable names can't be strings

5. You want to set a variable authToken in a Pre-request Script that depends on the response of a previous request stored in pm.response.json(). Which approach correctly sets authToken for use in the next request?

hard

A. Use pm.variables.set('authToken', pm.response.json().token); in the Pre-request Script

B. Use pm.environment.set('authToken', pm.response.json().token); in the Pre-request Script

C. Use pm.environment.set('authToken', pm.response.json().token); in the Tests script of the previous request

D. Use pm.variables.set('authToken', pm.response.json().token); in the Tests script of the previous request

Solution

1. Step 1: Identify when response data is available

   The response data from pm.response.json() is only available in the Tests script after the request completes, not in the Pre-request Script.

2. Step 2: Set variable for next request

   To use authToken in the next request, set it as an environment variable in the Tests script of the current request using pm.environment.set.

3. Step 3: Why not local variables?

   Local variables set with pm.variables.set do not persist across requests, so they won't be available in the next request.

4. Final Answer:

   Use pm.environment.set('authToken', pm.response.json().token); in the Tests script of the previous request -> Option C

5. Quick Check:

   Set environment variables in Tests to share data between requests [OK]

Hint: Set environment vars in Tests script to share between requests [OK]

Common Mistakes:

• Trying to access response in Pre-request Script
• Using pm.variables.set for cross-request data
• Setting variables in wrong script phase