QA Engineer interview question
How do you run exploratory testing?
Run exploratory testing with a time-boxed charter, risk hypothesis, representative data and environment; vary inputs and sequences, record observations and coverage, capture reproducible defects, then debrief and update future checks.
Direct answer
What a strong answer covers
How it works
Exploratory testing is structured learning about the product rather than random clicking. A session has a charter: an area, a risk hypothesis, and a time box, typically 60 to 90 minutes. The tester uses realistic data and an environment close to production, varies inputs, sequences, timing, and state in ways scripted tests do not, and takes notes on what was covered, what was surprising, and what was left untouched. Defects are captured with reproduction steps as they are found. A debrief afterwards turns the notes into new charters, new automated checks, and questions for the team, so each session compounds.
Example
Charter: explore the invoice editing flow with a focus on concurrent edits and undo, 75 minutes. The tester opened the same invoice in two tabs, edited a line in each, and saved both; the second save silently overwrote the first, which no scripted test had checked. Notes listed the state combinations tried, and the debrief produced a bug, an automated conflict test, and a new charter for the same behaviour in the mobile app.
Common mistakes
- Exploring with no charter and reporting only that it seems fine.
- Testing with placeholder data that never triggers real-world edge cases.
- Losing the findings because nothing was written down during the session.
A useful answer structure
Answer from your own work.
Do not memorise a script: use only examples you can explain honestly in follow-up questions.
Open the desktop workspace and rehearse a clear answer in your own words.