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.