Mock
A mock is a test double that simulates the behavior of a real object while allowing testers to verify interactions and expectations during testing.
“A type of test double that simulates the expected behavior of the component during testing.”
(Definition reproduced from the ISTQB Glossary. Copyright belongs to ISTQB.)
View the complete ISTQB GlossaryWhat is Mock?
Mocks isolate the component under test by replacing dependencies with controllable objects that return predefined responses and record interactions.
Isolation: Dependencies are replaced during testing.
Interaction verification: Mocks confirm expected method calls and parameters.
Automation support: Frequently used in unit and component testing.
Real World Example
A regulated product team is preparing a release where Mock appears in reviews, test design conversations, or defect triage rather than as an isolated glossary word.
The risk is that the team treats Mock as interchangeable with nearby ISTQB terms. That makes test scope blurry and can lead to weak evidence for the release decision.
The tester anchors the discussion in the official definition, asks where the concept appears in the product, and designs examples that show the difference between Mock and similar ideas.
The page becomes useful in practice because Mock is connected to a specific testing decision, not memorized as a detached definition.
Practice Questions
Question 1
Which statement BEST describes Mock in the context of ISTQB terminology?
Question 2
A tester needs to explain Mock to a non‑technical stakeholder. Which approach is MOST appropriate?
Test your knowledge with real ISTQB-style questions
You’ve learned Mock. Test your understanding with topic-specific questions in our Mock Exams.