Jump into concepts and practice - no test required
or
Recommended
Test this pattern10 questions across easy, medium, and hard to know if this pattern is strong
Recall & Review
beginner
What is a stub in software testing?
A stub is a simple fake component that returns predefined responses to calls during testing. It helps isolate the part being tested by simulating dependent parts.
Click to reveal answer
beginner
What is a mock in software testing?
A mock is a fake object that not only returns predefined responses but also records how it was used, allowing verification of interactions during tests.
Click to reveal answer
intermediate
How does a mock differ from a stub?
A stub provides fixed responses without tracking usage, while a mock tracks how it was called and can verify if expected interactions happened.
Click to reveal answer
beginner
In Postman, what is the purpose of a mock server?
A Postman mock server simulates an API by returning predefined responses to requests, helping test clients without needing the real API.
Click to reveal answer
beginner
Why might you use a stub instead of a mock in testing?
You use a stub when you only need to provide simple fixed responses and don't need to check how the fake was used.
Click to reveal answer
Which of the following best describes a stub?
AA fake that records how it was called for verification
BA fake that returns fixed responses without tracking calls
CA real component used in testing
DA tool to generate test reports
✗ Incorrect
A stub returns predefined responses but does not track how it was called.
What extra feature does a mock have compared to a stub?
AIt records and verifies interactions
BIt can simulate network delays
CIt generates random data
DIt runs tests automatically
✗ Incorrect
Mocks record how they are used and allow verification of interactions.
In Postman, what is the main use of a mock server?
ATo store test data
BTo generate documentation
CTo simulate API responses without the real API
DTo run automated tests
✗ Incorrect
Postman mock servers simulate API responses for testing without needing the real API.
When should you prefer a stub over a mock?
AWhen you need to verify method calls
BWhen testing UI components
CWhen running performance tests
DWhen you only need fixed responses without interaction checks
✗ Incorrect
Stubs are used when only fixed responses are needed, without verifying interactions.
Which statement is true about mocks and stubs?
AMocks can verify interactions, stubs cannot
BStubs track how they are called
CMocks are simpler than stubs
DStubs are used only in Postman
✗ Incorrect
Mocks can verify interactions, while stubs only provide fixed responses.
Explain the difference between a mock and a stub in simple terms.
Think about whether the fake just replies or also remembers how it was used.
You got /3 concepts.
Describe how Postman mock servers help in API testing.
Imagine testing an app before the real API is ready.
You got /3 concepts.
Practice
(1/5)
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
Step 1: Understand mock behavior in Postman
Mocks simulate real API behavior and can return different responses based on requests, making them dynamic.
Step 2: Understand stub behavior in Postman
Stubs provide fixed, predefined responses to replace real API calls, without simulating behavior.
Final Answer:
Mocks simulate API behavior with dynamic responses; stubs return fixed responses. -> Option B
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
Step 1: Identify stub creation method
Stubs are created by defining fixed example responses in a Postman collection to replace real API calls.
Step 2: Eliminate other options
Mocks use dynamic rules, JavaScript simulates logic but is not stub creation, and monitors check live APIs.
Final Answer:
Create a collection with fixed example responses and disable real API calls. -> Option A
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
Step 1: Analyze mock server response
The mock server returns {"success": true} dynamically for GET /user, indicating success.
Step 2: Analyze stub response effect
The stub always returns {"success": false}, a fixed failure response, which differs from mock.
Final Answer:
Tests expecting success will fail because stub returns fixed failure response. -> Option A
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
Step 1: Identify URL configuration issue
If tests receive stub responses instead of mock, likely the test requests use the stub server URL mistakenly.
Step 2: Verify other options
Mock servers must be enabled; stub server down would not cause stub responses; Postman supports dynamic mocks.
Final Answer:
The mock server URL is incorrectly set to the stub server URL in the tests. -> Option C
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
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.
Step 2: Combine mocks and stubs effectively
Mocks simulate dynamic role-based responses; stubs provide fixed responses for simple, repeatable tests.
Final Answer:
Use a mock server to simulate dynamic role responses and a stub with fixed responses for basic role tests. -> Option D
Quick Check:
Mocks dynamic + stubs fixed = best combo [OK]
Hint: Combine mocks for dynamic and stubs for fixed tests [OK]