What is exploratory testing and when do you use it?
- exploratory testing
- session-based
- test design
Answer it first, then compare. Nothing here is saved or scored.
Model answer
Exploratory testing is simultaneous learning, test design, and execution. You explore the application without predefined test cases, using your domain knowledge and intuition to find bugs. Use when: (1) New feature with minimal documentation. (2) After scripted tests pass, to find edge cases. (3) Under time pressure, highest bug-finding ROI. (4) For usability and UX evaluation. Structure it with session-based testing: set a charter ("Explore checkout flow focusing on error handling"), time-box it (45-90 minutes), and document findings in a session report.
What interviewers listen for
- Risk-based prioritisationYou can defend skipping coverage on a path because the risk maths supports it.
- Test design fluencyYou apply equivalence partitioning and decision tables to concrete inputs in real time.
- Metric judgmentYou distinguish between metrics that drive learning and metrics that drive theatre.
- Strategy under constraintYou can produce a defensible plan when the team has half the time and twice the scope.