Exploratory Testing Knowledge 4 — Questions and Answers
Question 1: Which best describes a 'test idea' in the context of exploratory testing?
- A fully documented test case with steps, data, and expected results
- A brief note capturing a potential thing worth testing, used to guide the session (Correct answer)
- An automated script that can be re-run on every build
- A formal review comment submitted to the development team
Correct answer: A brief note capturing a potential thing worth testing, used to guide the session
Test ideas are lightweight prompts—not full test cases—that an exploratory tester jots down and then investigates during the session.
Question 2: What is the role of 'mental models' in exploratory testing?
- They replace automated regression suites
- They help testers predict likely failure points based on how they believe the system works (Correct answer)
- They are formal UML diagrams that testers are required to draw
- They document bugs in a structured database format
Correct answer: They help testers predict likely failure points based on how they believe the system works
Testers build mental models of how the system works, and discrepancies between the model and actual behavior reveal potential defects.
Question 3: Which characteristic makes exploratory testing particularly effective at finding 'unknown unknowns'?
- It relies on exhaustive test case libraries
- It allows testers to follow unexpected leads that scripted tests would never reach (Correct answer)
- It runs tests in a fixed, repeatable sequence every time
- It uses static analysis tools to find code defects
Correct answer: It allows testers to follow unexpected leads that scripted tests would never reach
Because exploratory testers adapt in real time, they can pursue surprising behaviors that no pre-planned script anticipated.
Question 4: What does the 'TOUR' heuristic (FCC Touring Heuristics) suggest testers should do?
- Test only user-facing screens and skip back-end APIs
- Use real-world metaphors like traveling to systematically explore different aspects of an application (Correct answer)
- Run tours of the codebase before testing the UI
- Automate a tour of every menu item in alphabetical order
Correct answer: Use real-world metaphors like traveling to systematically explore different aspects of an application
Touring heuristics (e.g., the Guidebook Tour, Money Tour) use travel metaphors to help testers systematically vary their exploration strategy.
Question 5: In exploratory testing, when should a tester stop exploring a particular path?
- Only when a manager explicitly tells them to stop
- When the risk of continuing is low and higher-priority areas remain unexplored (Correct answer)
- When they have run exactly 10 tests on that path
- When no bugs have been found in the first two attempts
Correct answer: When the risk of continuing is low and higher-priority areas remain unexplored
Good exploratory testers make real-time decisions about where their time yields the most value, moving on when a path seems low-risk.
Question 6: Which of the following best represents 'knowledge transfer' as a benefit of exploratory testing?
- Test scripts are reusable by automation engineers
- Testers develop deep application understanding that improves future testing and team knowledge (Correct answer)
- Managers can read test logs without attending debriefs
- Defects are automatically categorized by the test tool
Correct answer: Testers develop deep application understanding that improves future testing and team knowledge
The learning that happens during exploration builds team knowledge about how the system actually behaves, benefiting future development and testing cycles.
Question 7: What is the key knowledge difference between a 'checklist' used in exploratory testing and a traditional test script?
- Checklists are generated by AI; test scripts are written by humans
- Checklists remind testers what to cover but leave execution approach open; scripts dictate exact steps (Correct answer)
- Checklists are only used for regression testing
- Test scripts are informal; checklists are legally binding documents
Correct answer: Checklists remind testers what to cover but leave execution approach open; scripts dictate exact steps
A checklist ensures broad coverage without constraining how the tester investigates each item, preserving exploratory freedom.
Exploratory Testing Knowledge 4
Which best describes a 'test idea' in the context of exploratory testing?