Using mock server URL in Postman - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is the main purpose of using a mock server URL in API testing?

Choose the best explanation for why testers use a mock server URL during API testing.

A To simulate API responses without calling the real server, enabling testing before backend is ready.

B To permanently replace the real API in production for faster response times.

C To encrypt API requests and responses for security during testing.

D To automatically generate API documentation from live server data.

💡 Hint

Think about why you might want to test an API before the real backend is finished.

Mock server URLs let testers simulate API responses so they can test frontend or integration without waiting for the real backend. This helps catch issues early.

❓ Predict Output

intermediate

What response does this Postman mock server return?

Given this Postman mock server setup, what will be the response body when a GET request is sent to /user/123?

Postman

{
  "mock": {
    "endpoint": "/user/:id",
    "method": "GET",
    "response": {
      "status": 200,
      "body": {
        "id": "123",
        "name": "Alice",
        "role": "tester"
      }
    }
  }
}

A {"id": "123", "name": "Alice", "role": "tester"}

B {"id": ":id", "name": "Alice", "role": "tester"}

C {"error": "User not found"}

D 404 Not Found

💡 Hint

Look at the mock response body and the URL parameter substitution.

The mock server replaces the :id parameter with the actual value 123 and returns the defined response body with status 200.

❓ locator

advanced

Which Postman mock server URL correctly matches this request?

You have a mock server with base URL https://mockserver.postman.com. Which full URL correctly calls the mock for endpoint /orders/:orderId/items with orderId 789?

A https://mockserver.postman.com/items/orders/789

B https://mockserver.postman.com/orders/items/789

C https://mockserver.postman.com/orders/789/items

D https://mockserver.postman.com/orders/:orderId/items

💡 Hint

Remember how URL path parameters are replaced in mock server URLs.

The :orderId placeholder is replaced by the actual value 789 in the URL path, so the correct URL is /orders/789/items.

❓ assertion

advanced

Which assertion correctly verifies the mock server response status is 200?

In Postman test scripts, which code snippet correctly asserts that the response status code from the mock server is 200?

A pm.test('Status is 200', () => { pm.response.status === 200; });

B pm.test('Status is 200', () => { pm.response.to.have.status(200); });

C pm.test('Status is 200', () => { pm.response.statusCode(200); });

D pm.test('Status is 200', () => { pm.response.statusCode === 200; });

💡 Hint

Check the correct Postman assertion syntax for status code.

Option B uses the correct Chai assertion syntax provided by Postman to check response status code.

🔧 Debug

expert

Why does this Postman mock server test fail?

Given this test script for a mock server response:

pm.test('Response has userId 101', () => {
  pm.expect(pm.response.json().userId).to.eql(101);
});

The mock server response body is {"userId": "101", "name": "Bob"}. Why does the test fail?

A Because pm.expect is not a valid Postman function.

B Because the mock server does not support JSON responses.

C Because the test script syntax is incorrect and missing a closing bracket.

D Because the response userId is a string "101", but the test expects a number 101.

💡 Hint

Check the data types of the expected and actual values in the assertion.

The mock server returns userId as a string "101" but the test expects the number 101. The strict equality check fails due to type mismatch.

Practice

1. What is the main purpose of using a mock server URL in Postman?

easy

A. To speed up the internet connection

B. To store user data permanently

C. To test API requests without needing the real backend server

D. To create a live production environment

Solution

1. Step 1: Understand what a mock server does

   A mock server simulates API responses without calling the real backend.

2. Step 2: Identify the main use case

   This helps test APIs when the real server is unavailable or to speed up development.

3. Final Answer:

   To test API requests without needing the real backend server -> Option C

4. Quick Check:

   Mock server = test without real backend [OK]

Hint: Mock servers simulate APIs without real backend [OK]

Common Mistakes:

• Thinking mock servers speed up internet
• Confusing mock server with data storage
• Assuming mock server is for production

2. Which of the following is the correct way to use a mock server URL in Postman?

easy

A. Replace the real API base URL with the mock server URL including the unique ID

B. Add the mock server URL as a query parameter to the real URL

C. Use the mock server URL only in the request headers

D. Append the mock server URL after the response body

Solution

1. Step 1: Understand mock server URL usage

   You replace the real API base URL with the mock server URL that includes the unique mock ID.

2. Step 2: Check other options

   Adding as query parameter, headers, or after response body is incorrect usage.

3. Final Answer:

   Replace the real API base URL with the mock server URL including the unique ID -> Option A

4. Quick Check:

   Mock URL replaces base URL [OK]

Hint: Mock URL replaces real API base URL [OK]

Common Mistakes:

• Adding mock URL as query parameter
• Using mock URL only in headers
• Appending mock URL after response

3. Given the mock server URL https://mockserver.com/12345/api/users, what will happen if you send a GET request to this URL in Postman?

medium

A. You will get a mocked response defined in the mock server for the /api/users endpoint

B. The request will fail because mock servers do not support GET requests

C. You will get a real response from the live backend server

D. Postman will ignore the mock server URL and use the environment variable URL

Solution

1. Step 1: Understand mock server behavior

   Mock servers return predefined responses for requests sent to their URLs.

2. Step 2: Analyze the given URL and request

   Sending GET to the mock URL returns the mocked response for /api/users.

3. Final Answer:

   You will get a mocked response defined in the mock server for the /api/users endpoint -> Option A

4. Quick Check:

   GET to mock URL returns mock response [OK]

Hint: GET to mock URL returns predefined mock response [OK]

Common Mistakes:

• Thinking mock servers reject GET requests
• Expecting real backend response
• Assuming environment variables override mock URL

4. You set the mock server URL incorrectly by missing the unique ID part, like https://mockserver.com/api/users. What issue will you face?

medium

A. The request will succeed and return the correct mock response

B. Postman will fail to route the request to the mock server and return an error

C. Postman will automatically add the missing unique ID

D. The request will be sent to the real backend server instead

Solution

1. Step 1: Identify the importance of unique ID in mock URL

   The unique ID is required to route requests to the correct mock server instance.

2. Step 2: Consequence of missing unique ID

   Without it, Postman cannot find the mock server and returns an error.

3. Final Answer:

   Postman will fail to route the request to the mock server and return an error -> Option B

4. Quick Check:

   Missing mock ID causes routing error [OK]

Hint: Always include unique ID in mock URL [OK]

Common Mistakes:

• Assuming Postman auto-fixes missing ID
• Expecting fallback to real backend
• Thinking request will succeed without ID

5. You want to test an API endpoint /products using a Postman mock server. Your mock server URL is https://mockserver.com/abcde. Which is the correct full URL to use in your request to get the mocked /products response?

hard

A. https://mockserver.com/api/abcde/products

B. https://mockserver.com/products/abcde

C. https://mockserver.com/abcde/api/products

D. https://mockserver.com/abcde/products

Solution

1. Step 1: Understand mock server URL structure

   The mock server URL includes the unique ID, followed by the API endpoint path.

2. Step 2: Construct the correct full URL

   Append the endpoint /products directly after the unique ID in the URL.

3. Final Answer:

   https://mockserver.com/abcde/products -> Option D

4. Quick Check:

   Mock URL + endpoint path = full request URL [OK]

Hint: Append endpoint path after mock server URL with ID [OK]

Common Mistakes:

• Placing unique ID after endpoint path
• Adding extra /api/ segment incorrectly
• Mixing order of ID and endpoint