Bug Hunting
Bug hunting is an informal testing activity focused on actively searching for defects using experience, intuition, and investigative techniques.
“A test approach in which gamification and awards for defects found are used as a motivator.”
(Definition reproduced from the ISTQB Glossary. Copyright belongs to ISTQB.)
View the complete ISTQB GlossaryWhat is Bug Hunting?
Bug hunting encourages testers to explore the software beyond predefined test cases to uncover unexpected defects, especially in areas known to be error-prone.
Experience-driven: Testers rely on product knowledge and previous defect patterns.
Creative exploration: Testers intentionally try unusual or unexpected actions.
Relationship to exploratory testing: Bug hunting often complements structured testing activities.
Real World Example
A regulated product team is preparing a release where Bug hunting appears in reviews, test design conversations, or defect triage rather than as an isolated glossary word.
The risk is that the team treats Bug hunting 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 Bug hunting and similar ideas.
The page becomes useful in practice because Bug hunting is connected to a specific testing decision, not memorized as a detached definition.
Practice Questions
Question 1
Which plan BEST supports a bug hunt?
Question 2
Which outcome indicates a successful bug hunt?
Test your knowledge with real ISTQB-style questions
You’ve learned Bug Hunting. Test your understanding with topic-specific questions in our Mock Exams.