Exploratory testing is simultaneous learning, test design, and execution — the tester explores the app, using experience and intuition to design tests on the fly, guided by charters. Ad-hoc testing is informal, unstructured testing without any plan or documentation.
EXPLORATORY testing is unscripted but STRUCTURED by session charters and note-taking; the tester continuously designs and adapts tests based on what they observe, excelling at finding defects scripted cases miss (usability, unexpected flows, edge interactions). It complements scripted testing rather than replacing it. AD-HOC testing is even less formal — random, no documentation, relying purely on tester knowledge to 'break' the app quickly (a form of error guessing). Both leverage tester skill/intuition; exploratory adds lightweight structure and accountability (charters, session notes, time-boxing). Interviewers value understanding that these find different defects than scripted cases.
Given a new feature with thin requirements, a tester runs a 60-minute chartered exploratory session ('explore checkout with unusual payment/coupon combinations'), taking notes and uncovering a currency-rounding bug no scripted case covered.
How does exploratory testing differ from ad-hoc testing, and when is exploratory valuable?