Ad Hoc Testing
Ad hoc testing is an informal testing approach where testers explore the software without predefined test cases to discover defects quickly.
“Informal testing performed without test analysis and test design.”
(Definition reproduced from the ISTQB Glossary. Copyright belongs to ISTQB.)
View the complete ISTQB GlossaryWhat is Ad Hoc Testing?
Ad hoc testing relies on the tester's knowledge, intuition, and experience rather than documented procedures. It is useful for uncovering unexpected defects that structured testing may overlook.
Flexible approach: Testers investigate the application freely instead of following scripted steps.
Experience matters: The effectiveness of ad hoc testing depends heavily on the tester's product knowledge and analytical skills.
Relationship to exploratory testing: Unlike exploratory testing, ad hoc testing is generally less structured and may not involve formal documentation.
Real World Example
A regulated product team is preparing a release where Ad hoc testing appears in reviews, test design conversations, or defect triage rather than as an isolated glossary word.
The risk is that the team treats Ad hoc testing 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 Ad hoc testing and similar ideas.
The page becomes useful in practice because Ad hoc testing is connected to a specific testing decision, not memorized as a detached definition.
Practice Questions
Question 1
Which of the following BEST describes ad hoc testing?
Question 2
What is a key limitation of ad hoc testing?
Test your knowledge with real ISTQB-style questions
You’ve learned Ad Hoc Testing. Test your understanding with topic-specific questions in our Mock Exams.