Mock vs stub comparison in Postman

Introduction

Mocks and stubs help test parts of software by pretending to be other parts. They make testing easier and faster.

When you want to test a feature but the real service is not ready or slow.

When you want to check how your code reacts to specific responses from another service.

When you want to isolate your test from external systems to avoid failures caused by them.

When you want to simulate error conditions that are hard to create with real services.

Syntax

Postman

Mock: A fake server or response that simulates real API behavior.
Stub: A simple fixed response used to replace a real API call.

Mocks can simulate complex behavior and multiple responses.

Stubs usually return fixed data and are simpler than mocks.

Examples

This mock simulates a GET request to '/user/1' and returns a user named Alice.

Postman

// Mock example in Postman
pm.mockServer.create({
  name: 'User API Mock',
  responses: [
    { request: { method: 'GET', url: '/user/1' }, response: { status: 200, body: '{"id":1,"name":"Alice"}' } }
  ]
});

This stub returns a fixed user response for the GET request to '/user/1'.

Postman

// Stub example in Postman test script
pm.stub('GET', '/user/1', {
  status: 200,
  body: '{"id":1,"name":"Stub User"}'
});

Sample Program

This test uses a stub to fake the weather API response. It checks that the status is 200 and temperature is 25.

Postman

// Postman test script using stub
pm.stub('GET', '/weather/today', {
  status: 200,
  body: '{"temp":25,"condition":"Sunny"}'
});

pm.sendRequest({
  url: 'https://api.example.com/weather/today',
  method: 'GET'
}, function (err, res) {
  pm.test('Status is 200', function () {
    pm.expect(res.status).to.eql(200);
  });
  pm.test('Response has temp 25', function () {
    const jsonData = res.json();
    pm.expect(jsonData.temp).to.eql(25);
  });
});

Important Notes

Mocks are more flexible and can simulate many scenarios.

Stubs are easier to create but less powerful.

Use mocks when you need to test complex interactions.

Summary

Mocks simulate real API behavior with flexible responses.

Stubs provide fixed responses to replace real calls.

Both help isolate tests and improve reliability.

Practice

1. Which statement best describes the difference between a mock and a stub in Postman testing?

easy

A. Mocks and stubs both return fixed responses without behavior simulation.

B. Mocks simulate API behavior with dynamic responses; stubs return fixed responses.

C. Stubs simulate API behavior with dynamic responses; mocks return fixed responses.

D. Mocks and stubs are the same and can be used interchangeably.

Solution

1. Step 1: Understand mock behavior in Postman

   Mocks simulate real API behavior and can return different responses based on requests, making them dynamic.

2. Step 2: Understand stub behavior in Postman

   Stubs provide fixed, predefined responses to replace real API calls, without simulating behavior.

3. Final Answer:

   Mocks simulate API behavior with dynamic responses; stubs return fixed responses. -> Option B

4. Quick Check:

   Mock = dynamic, Stub = fixed [OK]

Hint: Mocks are dynamic; stubs are fixed response tools [OK]

Common Mistakes:

• Confusing mocks as fixed response tools
• Thinking stubs simulate behavior dynamically
• Believing mocks and stubs are identical
• Assuming stubs can replace mocks fully

2. Which of the following is the correct way to create a stub in Postman?

easy

A. Create a collection with fixed example responses and disable real API calls.

B. Use Postman Mock Server with multiple dynamic response rules.

C. Write JavaScript code to simulate API logic inside Postman tests.

D. Use Postman monitors to generate live API responses.

Solution

1. Step 1: Identify stub creation method

   Stubs are created by defining fixed example responses in a Postman collection to replace real API calls.

2. Step 2: Eliminate other options

   Mocks use dynamic rules, JavaScript simulates logic but is not stub creation, and monitors check live APIs.

3. Final Answer:

   Create a collection with fixed example responses and disable real API calls. -> Option A

4. Quick Check:

   Stub = fixed examples in collection [OK]

Hint: Stubs use fixed examples, not dynamic rules [OK]

Common Mistakes:

• Confusing mocks with stubs in creation steps
• Thinking JavaScript test scripts create stubs
• Using monitors as stubs
• Assuming dynamic responses are stubs

3. Given a Postman mock server configured to return a 200 status with body {"success": true} for GET /user, what will happen if you replace it with a stub that always returns {"success": false} for the same request?

medium

A. Tests expecting success will fail because stub returns fixed failure response.

B. Tests will pass because stub simulates the same dynamic behavior as mock.

C. Tests will fail due to syntax errors in stub configuration.

D. Tests will pass because both mock and stub return 200 status.

Solution

1. Step 1: Analyze mock server response

   The mock server returns {"success": true} dynamically for GET /user, indicating success.

2. Step 2: Analyze stub response effect

   The stub always returns {"success": false}, a fixed failure response, which differs from mock.

3. Final Answer:

   Tests expecting success will fail because stub returns fixed failure response. -> Option A

4. Quick Check:

   Stub fixed failure ≠ mock success [OK]

Hint: Stub fixed response can break tests expecting mock's dynamic success [OK]

Common Mistakes:

• Assuming stub matches mock dynamic behavior
• Ignoring response body differences
• Thinking status code alone determines test pass
• Confusing syntax errors with logic errors

4. You created a Postman mock server but your tests always receive the stub's fixed response instead of the mock's dynamic response. What is the most likely cause?

medium

A. Postman does not support mock servers with dynamic responses.

B. The mock server is not enabled in Postman settings.

C. The mock server URL is incorrectly set to the stub server URL in the tests.

D. The stub server is down, causing fallback to mock responses.

Solution

1. Step 1: Identify URL configuration issue

   If tests receive stub responses instead of mock, likely the test requests use the stub server URL mistakenly.

2. Step 2: Verify other options

   Mock servers must be enabled; stub server down would not cause stub responses; Postman supports dynamic mocks.

3. Final Answer:

   The mock server URL is incorrectly set to the stub server URL in the tests. -> Option C

4. Quick Check:

   Wrong URL causes stub responses [OK]

Hint: Check URLs to avoid mixing mock and stub servers [OK]

Common Mistakes:

• Assuming mock server is disabled by default
• Believing stub server downtime causes stub responses
• Thinking Postman lacks dynamic mock support
• Ignoring URL configuration in tests

5. You want to test an API that returns different user roles based on request headers. Which approach best uses Postman mocks and stubs together to ensure reliable and flexible testing?

hard

A. Use neither mocks nor stubs; test only against the live API.

B. Use only stubs with fixed responses for all role variations to simplify tests.

C. Use only mocks with dynamic responses and avoid stubs to prevent confusion.

D. Use a mock server to simulate dynamic role responses and a stub with fixed responses for basic role tests.

Solution

1. Step 1: Identify need for dynamic and fixed responses

   Testing different user roles requires dynamic responses for flexibility and fixed responses for stable baseline tests.

2. Step 2: Combine mocks and stubs effectively

   Mocks simulate dynamic role-based responses; stubs provide fixed responses for simple, repeatable tests.

3. Final Answer:

   Use a mock server to simulate dynamic role responses and a stub with fixed responses for basic role tests. -> Option D

4. Quick Check:

   Mocks dynamic + stubs fixed = best combo [OK]

Hint: Combine mocks for dynamic and stubs for fixed tests [OK]

Common Mistakes:

• Using only stubs loses dynamic testing benefits
• Using only mocks may complicate simple tests
• Ignoring mocks and stubs reduces test reliability
• Testing only live API risks instability