ISTQB Experience-Based Testing Techniques 2 — Questions and Answers
Question 1: In exploratory testing, what is a 'test charter'?
- A formal test plan approved by management
- A mission statement defining the scope and goals of an exploration session (Correct answer)
- A checklist of all test cases to execute
- A defect report template used during testing
Correct answer: A mission statement defining the scope and goals of an exploration session
A test charter defines the purpose, scope, and target of an exploratory testing session, guiding the tester's exploration.
Question 2: Which of the following best describes 'checklist-based testing'?
- Testing based on a random selection of test cases
- Testing guided by a list of items to verify derived from experience or requirements (Correct answer)
- Testing that only checks items flagged by automated tools
- Testing where each item is executed exactly once in sequence
Correct answer: Testing guided by a list of items to verify derived from experience or requirements
Checklist-based testing uses experience-derived lists of conditions or items to ensure coverage of important areas.
Question 3: A tester with years of experience in a banking application is asked to test a new payment module without a formal test plan. This is best described as:
- Ad hoc testing with no structure
- Risk-based testing
- Experience-based testing leveraging domain knowledge (Correct answer)
- Regression testing
Correct answer: Experience-based testing leveraging domain knowledge
Using accumulated domain knowledge and intuition to design and execute tests without formal scripts exemplifies experience-based testing.
Question 4: In a time-boxed exploratory testing session, what should the tester do when the session ends?
- Immediately start a new session without debriefing
- Discard all notes and start fresh
- Debrief by reviewing notes, logging defects, and reporting session results (Correct answer)
- Submit all findings directly to the development team without review
Correct answer: Debrief by reviewing notes, logging defects, and reporting session results
After a time-boxed session, debriefing consolidates notes, ensures defects are logged, and captures insights for future sessions.
Question 5: Which factor most distinguishes error guessing from random testing?
- Error guessing uses automated tools while random testing is manual
- Error guessing relies on tester knowledge to predict likely defects, while random testing has no such basis (Correct answer)
- Error guessing only applies to UI testing, while random testing applies to APIs
- Error guessing requires formal documentation of every test case
Correct answer: Error guessing relies on tester knowledge to predict likely defects, while random testing has no such basis
Error guessing leverages the tester's experience and knowledge to identify where defects are most likely, unlike random testing which has no predictive basis.
Question 6: Which of the following is a limitation of checklist-based testing?
- It cannot be used by experienced testers
- Checklists may become outdated and miss new defect types if not maintained (Correct answer)
- It always results in 100% code coverage
- It requires specialized automation tools
Correct answer: Checklists may become outdated and miss new defect types if not maintained
Checklists based on past experience can miss novel defect types and must be regularly updated to remain effective.
Question 7: Session-based test management (SBTM) was primarily designed to address which challenge in exploratory testing?
- Automating exploratory test execution
- Providing accountability and measurability to unscripted testing (Correct answer)
- Replacing formal test plans entirely
- Generating test data automatically
Correct answer: Providing accountability and measurability to unscripted testing
SBTM introduces structured sessions with charters and debriefs to make exploratory testing accountable and measurable.
In exploratory testing, what is a 'test charter'?