Environment switching in Postman

Introduction

Environment switching helps you run the same tests with different settings easily. It saves time and avoids mistakes when testing in multiple places.

Testing the same API on development, staging, and production servers.

Running tests with different user credentials or tokens.

Switching between different database connections during testing.

Testing features that behave differently based on environment variables.

Sharing tests with teammates who use different setups.

Syntax

Postman

1. Create environments in Postman with variables (e.g., baseUrl).
2. Use {{variableName}} in your requests (e.g., {{baseUrl}}/api/users).
3. Select the environment from the dropdown before running tests.

Use double curly braces {{}} to insert environment variables in URLs, headers, or body.

Switching environments changes variable values without editing requests.

Examples

This sends the request to the development server using the baseUrl variable.

Postman

Environment variables:
baseUrl = https://dev.example.com

Request URL:
{{baseUrl}}/api/login

Switching environment to production changes the baseUrl automatically.

Postman

Environment variables:
baseUrl = https://prod.example.com

Request URL:
{{baseUrl}}/api/login

Authorization header uses the token from the selected environment.

Postman

Using token variable:
accessToken = abc123

Header:
Authorization: Bearer {{accessToken}}

Sample Program

This test checks if the API status endpoint returns 200 OK. By switching environment, the same test runs on dev or prod servers.

Postman

/* Postman test script example */

// Environment variables setup:
// dev environment: baseUrl = https://dev.example.com
// prod environment: baseUrl = https://prod.example.com

// Request URL:
// {{baseUrl}}/api/status

// Test script to check response status
pm.test("Status code is 200", function () {
    pm.response.to.have.status(200);
});

Important Notes

Always define all needed variables in each environment to avoid missing values.

Use descriptive environment names to avoid confusion.

Remember to select the correct environment before running your tests.

Summary

Environment switching lets you reuse tests with different settings easily.

Use {{variable}} syntax to insert environment variables in requests.

Select the environment in Postman to change variable values automatically.

Practice

1. What is the main purpose of environment switching in Postman?

easy

A. To reuse the same requests with different variable values easily

B. To change the Postman app theme

C. To create new collections automatically

D. To export test results to a file

Solution

1. Step 1: Understand environment switching concept

   Environment switching allows changing variable values without editing requests.

2. Step 2: Identify the main benefit

   This lets you reuse the same requests with different settings easily.

3. Final Answer:

   To reuse the same requests with different variable values easily -> Option A

4. Quick Check:

   Environment switching = reuse requests with different variables [OK]

Hint: Think: same request, different settings [OK]

Common Mistakes:

• Confusing environment switching with UI themes
• Thinking it creates new collections
• Assuming it exports test results

2. Which syntax correctly uses an environment variable in a Postman request URL?

easy

A. https://api.example.com/{{userId}}/data

B. https://api.example.com/$userId/data

C. https://api.example.com/%userId%/data

D. https://api.example.com/userId/data

Solution

1. Step 1: Recall Postman variable syntax

   Postman uses double curly braces {{variable}} to insert environment variables.

2. Step 2: Match syntax to options

   Only https://api.example.com/{{userId}}/data uses {{userId}} correctly in the URL.

3. Final Answer:

   https://api.example.com/{{userId}}/data -> Option A

4. Quick Check:

   Use {{variable}} for environment variables [OK]

Hint: Remember: double curly braces {{}} for variables [OK]

Common Mistakes:

• Using $variable or %variable% instead of {{variable}}
• Writing variable name without braces
• Confusing environment variables with query parameters

3. Given two environments in Postman:
Dev: baseUrl=https://dev.api.com
Prod: baseUrl=https://api.com
And a request URL: {{baseUrl}}/users
What will be the full URL when the 'Prod' environment is selected?

medium

A. https://dev.api.com/users

B. https://api.com/users

C. {{baseUrl}}/users

D. https://users.api.com

Solution

1. Step 1: Identify the selected environment variable value

   In 'Prod' environment, baseUrl = https://api.com

2. Step 2: Substitute variable in request URL

   Replacing {{baseUrl}} with https://api.com gives https://api.com/users

3. Final Answer:

   https://api.com/users -> Option B

4. Quick Check:

   Selected environment variable replaces {{baseUrl}} [OK]

Hint: Pick variable value from active environment [OK]

Common Mistakes:

• Using variable value from wrong environment
• Not replacing variable at all
• Mixing variable name with URL parts

4. You switched to a new environment in Postman but your request still uses old variable values. What is the most likely cause?

medium

A. Postman does not support environment switching

B. You used incorrect {{variable}} syntax in the request

C. You forgot to select the new environment in the environment dropdown

D. You need to restart Postman to apply environment changes

Solution

1. Step 1: Understand environment selection in Postman

   Switching environment requires selecting it from the environment dropdown.

2. Step 2: Identify why old values persist

   If old values appear, likely the new environment was not selected properly.

3. Final Answer:

   You forgot to select the new environment in the environment dropdown -> Option C

4. Quick Check:

   Select environment dropdown to switch variables [OK]

Hint: Always check environment dropdown selection [OK]

Common Mistakes:

• Assuming syntax error causes old values
• Thinking Postman needs restart
• Believing environment switching is unsupported

5. You have two environments:
Test: apiUrl=https://test.api.com, token=abc123
Live: apiUrl=https://live.api.com, token=xyz789
You want to run the same collection with both environments automatically in Postman. Which approach is best?

hard

A. Use environment variables but run only with one environment at a time

B. Manually edit requests to change URLs and tokens each time

C. Create separate collections for Test and Live with hardcoded URLs

D. Use Postman Collection Runner and select each environment before running

Solution

1. Step 1: Understand how to run collections with different environments

   Postman Collection Runner allows selecting environment per run.

2. Step 2: Identify best practice for automatic environment switching

   Selecting each environment in Collection Runner lets you reuse the same collection easily.

3. Final Answer:

   Use Postman Collection Runner and select each environment before running -> Option D

4. Quick Check:

   Collection Runner + environment selection = easy reuse [OK]

Hint: Use Collection Runner with environment selection [OK]

Common Mistakes:

• Hardcoding URLs instead of using variables
• Editing requests manually each time
• Running only one environment without switching