Exploratory Testing Certification — Questions and Answers

Question 1: What is the purpose of a 'minimal test case' when reporting a defect?

To reduce reproduction steps to the smallest set that still triggers the defect (Correct answer)
To create a simplified version of the application for testing
To list only the most critical features affected
To ensure the defect can be found in fewer than five seconds

Correct answer: To reduce reproduction steps to the smallest set that still triggers the defect

A minimal test case strips away unnecessary steps, making it faster for developers to reproduce and isolate the root cause.

Question 2: What does a 'mission-based' test charter emphasize?

The specific tools and automation scripts the tester must use
A strict sequence of test steps that must be followed
The number of bugs the tester must find per session
A clear goal or information need that guides the tester's investigation (Correct answer)

Correct answer: A clear goal or information need that guides the tester's investigation

Mission-based charters keep testing purposeful by ensuring every session has a clear reason to exist and a tangible outcome to aim for.

Question 3: Why should exploratory testers document 'areas not tested' at the end of a project?

To justify requesting additional testing resources for the next project
To avoid being blamed for defects found after release
To satisfy a mandatory regulatory requirement for all software projects
To inform stakeholders about residual risk and gaps in coverage so they can make informed release decisions (Correct answer)

Correct answer: To inform stakeholders about residual risk and gaps in coverage so they can make informed release decisions

Documenting untested areas gives stakeholders an honest picture of residual risk, enabling informed go/no-go decisions at release.

Question 4: What is the first thing an exploratory tester should do when they discover a potential defect?

Ask the developer if it is expected behavior
Immediately file a bug report with minimal information
Reproduce it and gather evidence before reporting (Correct answer)
Stop the session and notify the test manager

Correct answer: Reproduce it and gather evidence before reporting

Reproducing the defect and collecting evidence (screenshots, logs, steps) ensures the bug report is actionable and credible.

Question 5: How detailed should an exploratory test charter typically be?

Detailed enough to replace a test script
Detailed to the point of listing every step
As vague as possible to allow maximum creativity
Brief enough to allow freedom but specific enough to guide focus (Correct answer)

Correct answer: Brief enough to allow freedom but specific enough to guide focus

Charters strike a balance — they guide the tester's focus without eliminating the freedom to explore.

Question 6: 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 document bugs in a structured database format
They are formal UML diagrams that testers are required to draw

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 7: Which is an example of a software dashboard integration offered by Global App Testing?

Jira (Correct answer)
Google Drive
Wordpress
Trello

Correct answer: Jira

Jira is a widely used project management and issue tracking software in the software development industry. Many testing services, including Global App Testing, integrate with Jira to streamline the bug reporting and tracking process. This allows test results and discovered issues to be easily logged and managed within existing development workflows.

Question 8: Who is responsible for writing test charters in an exploratory testing engagement?

Developers write charters based on unit test failures
Charters can be written by testers, test leads, product owners, or anyone with knowledge of risks and requirements (Correct answer)
Only senior test managers are authorized to write charters
Business analysts write all charters during requirements gathering

Correct answer: Charters can be written by testers, test leads, product owners, or anyone with knowledge of risks and requirements

Charters can be written by anyone with knowledge of the product's risks, making them a collaborative artifact in exploratory testing.

Question 9: What is the 'cost of quality' concept as it applies to risk-based exploratory testing?

The expense of maintaining a full regression test suite
The budget required to hire experienced exploratory testers
The trade-off between the cost of testing thoroughly and the cost of defects reaching production (Correct answer)
The licensing cost for testing tools and environments

Correct answer: The trade-off between the cost of testing thoroughly and the cost of defects reaching production

Cost of quality balances investment in testing (prevention and detection) against the cost of failures reaching users (internal and external failure costs).

Question 10: What is the benefit of involving developers in exploratory risk identification?

Developer involvement ensures exploratory testing results are accepted without dispute
Developers can write charters on behalf of testers to save time
Developers know which parts of the code are most complex, unstable, or recently changed, revealing risks not visible from requirements (Correct answer)
Developers can fix bugs in real time during exploratory sessions, reducing rework

Correct answer: Developers know which parts of the code are most complex, unstable, or recently changed, revealing risks not visible from requirements

Developers have unique insight into code complexity, architectural weaknesses, and recent changes that testers cannot see from the outside.

Question 11: What is the difference between a 'bug report' and a 'test note' in exploratory testing?

They are the same document with different names
A bug report is a formal defect record; a test note is an informal observation during testing (Correct answer)
Bug reports go to developers; test notes go to managers only
Test notes are only written for passed test cases

Correct answer: A bug report is a formal defect record; a test note is an informal observation during testing

Bug reports are formal, actionable defect records; test notes are informal observations, questions, or ideas captured during a session.

Question 12: What is the primary output artifact of a session-based exploratory testing session?

A formal test case document
A defect density matrix
A session sheet or session report (Correct answer)
An automated regression script

Correct answer: A session sheet or session report

A session sheet (or session report) captures the charter, findings, issues, and notes from an exploratory testing session.

Question 13: In SBTM, what does the acronym 'SBTM' stand for?

Session-Based Test Management (Correct answer)
Software Build and Test Monitoring
Structured Bug Tracking Mechanism
Scripted Behavior Testing Method

Correct answer: Session-Based Test Management

SBTM stands for Session-Based Test Management, a framework pioneered by Jonathan and James Bach to track and manage exploratory testing.

Question 14: What information should a tester always include in an exploratory testing session report?

The tester's professional opinion on whether the feature is ready to release
Charter, test notes, bugs found, coverage areas, issues or blockers, and time spent on each activity (Correct answer)
Only the list of bugs found with severity and reproduction steps
A count of test cases executed and passed versus failed

Correct answer: Charter, test notes, bugs found, coverage areas, issues or blockers, and time spent on each activity

A complete session report captures the mission, observations, defects, coverage, and time distribution so the team can assess what was tested and what risks remain.

Question 15: What is risk-based testing (RBT) in the context of exploratory testing?

Running all tests in a risk-free sandbox environment
Prioritizing testing effort toward areas with the highest likelihood and impact of failure (Correct answer)
Testing only the features classified as 'high risk' by management
Performing testing without any formal test plan to reduce project risk

Correct answer: Prioritizing testing effort toward areas with the highest likelihood and impact of failure

Risk-based testing allocates exploratory effort toward areas where defects are most likely to occur and have the greatest impact.

Question 16: What is the primary role of a 'charter' in session-based exploratory testing?

A script listing exact steps to reproduce a defect
A log of all bugs found during testing
A written mission statement that defines the scope and goals of an exploration session (Correct answer)
A formal test plan approved by a project manager

Correct answer: A written mission statement that defines the scope and goals of an exploration session

A charter gives the tester a focused mission—defining what to explore and what questions to answer—without dictating exact steps.

Question 17: What is the benefit of 'cross-session analysis' when reviewing multiple exploratory testing session reports?

It allows managers to compare individual tester productivity across sessions
It automatically generates scripted test cases from the combined session findings
It reveals patterns across sessions such as persistent bug clusters, coverage gaps, and areas requiring deeper exploration (Correct answer)
It validates that each session followed the approved test approach correctly

Correct answer: It reveals patterns across sessions such as persistent bug clusters, coverage gaps, and areas requiring deeper exploration

Cross-session analysis elevates individual findings into systemic insights, revealing whether certain product areas consistently produce defects or remain consistently unexplored.

Question 18: A tester follows an unexpected error message and investigates its root cause instead of continuing the original test path. This behavior is called:

Test derailment
Scope creep
Defect seeding
Reactive opportunism (Correct answer)

Correct answer: Reactive opportunism

Reactive opportunism is the exploratory practice of pivoting to investigate an interesting or unexpected observation encountered during testing.

Question 19: What results are achieved by software testing?

All of these (Correct answer)
Provide independent view of the software.
Provide stakeholders with information about the quality of the product.
Provide objective view of the software.

Correct answer: All of these

Software testing serves multiple crucial purposes. It provides an independent and objective view of the software's quality by systematically evaluating its functionality, performance, and reliability. Ultimately, the results of testing provide stakeholders with essential information about the product's quality, enabling informed decisions about its release and readiness.

Question 20: Why is it important to check whether a defect already exists in the bug tracker before filing a new report?

To check if the defect affects the latest build only
To avoid duplicate reports that waste developer time and distort defect metrics (Correct answer)
To confirm the defect is in scope for the current sprint
To determine if the tester should be credited for finding it

Correct answer: To avoid duplicate reports that waste developer time and distort defect metrics

Duplicate bug reports create noise in the tracker and waste developer time reviewing the same issue multiple times.

Question 21: When is it appropriate to modify a charter mid-session?

Never — charters must be strictly followed
Only when no bugs have been found after 30 minutes
When the tester discovers something more important or urgent to explore (Correct answer)
Only with written approval from the test manager

Correct answer: When the tester discovers something more important or urgent to explore

Exploratory testers can deviate from a charter when a discovery leads to a more important investigation.

Question 22: How does 'exploratory risk testing' differ from formal risk management in a project?

Exploratory risk testing is less rigorous than formal risk management and is not accepted in regulated industries
Exploratory risk testing actively probes the software for defects in high-risk areas, while formal risk management identifies and tracks risks at the project level (Correct answer)
Exploratory risk testing and formal risk management serve identical purposes and can be substituted for each other
Formal risk management includes exploratory testing as its primary execution method

Correct answer: Exploratory risk testing actively probes the software for defects in high-risk areas, while formal risk management identifies and tracks risks at the project level

Formal risk management tracks project-level risks like schedule and budget, while exploratory risk testing directly investigates the software for defects in areas identified as risky.

Question 23: What does the 'Landmark Tour' technique involve?

Navigating the application between key features or screens in a variety of orders (Correct answer)
Following the application's happy path exactly once
Only testing the main navigation menu
Testing the application's help and documentation pages

Correct answer: Navigating the application between key features or screens in a variety of orders

The Landmark Tour explores key features in varying sequences to uncover order-dependent failures and navigation issues.

Question 24: What is 'charter drift' in exploratory testing?

When a charter is updated mid-sprint to reflect new requirements
When a charter is poorly written and lacks a clear target
When a tester deviates significantly from the original charter scope during a session (Correct answer)
When two testers accidentally cover the same charter simultaneously

Correct answer: When a tester deviates significantly from the original charter scope during a session

Charter drift occurs when a tester's investigation wanders too far from the original charter, reducing accountability and coverage focus.

Question 25: How does 'priority' differ from 'severity' in a defect report?

Priority is set by testers; severity is set by developers
Priority is about when the bug should be fixed; severity is about how bad the impact is (Correct answer)
Priority only applies to security defects
Priority and severity mean the same thing in most organizations

Correct answer: Priority is about when the bug should be fixed; severity is about how bad the impact is

Severity describes the technical impact; priority reflects business urgency — a low-severity bug may be high priority if it affects the product's image.

Question 26: What is 'charter completion rate' and what does it indicate about a testing cycle?

The percentage of planned charters that were fully executed, indicating how much of the intended exploration was accomplished (Correct answer)
The percentage of charters that resulted in at least one filed bug report
The number of bugs found per charter as a measure of charter quality
The rate at which new charters are being written relative to sessions completed

Correct answer: The percentage of planned charters that were fully executed, indicating how much of the intended exploration was accomplished

Charter completion rate shows how much of the planned exploration actually happened, helping teams assess whether testing coverage goals were met.

Question 27: What does 'test coverage' mean in the context of risk-based exploratory testing?

The percentage of code lines executed during testing
The ratio of passed tests to total tests run
The number of test cases executed versus planned
The proportion of identified risk areas that have been meaningfully explored (Correct answer)

Correct answer: The proportion of identified risk areas that have been meaningfully explored

In risk-based exploratory testing, coverage means ensuring each significant risk area has been deliberately explored, not just code lines touched.

Question 28: What is a 'follow-up charter'?

A charter assigned to a different tester to verify bugs
A charter used to document test results after a session
A charter that replaces a cancelled session
A charter created based on findings from a previous session that warrant deeper investigation (Correct answer)

Correct answer: A charter created based on findings from a previous session that warrant deeper investigation

Follow-up charters are created when a session surfaces a new area of interest that deserves dedicated exploration.

Question 29: Which of the following best represents a well-written exploratory test charter?

Verify that the shopping cart correctly calculates totals
Click the Buy Now button and verify the confirmation email is received
Test the payment module — check all fields
Explore the checkout workflow with a guest user account to discover payment validation weaknesses (Correct answer)

Correct answer: Explore the checkout workflow with a guest user account to discover payment validation weaknesses

A well-written charter is specific about the target (checkout workflow), the resource (guest user account), and the goal (payment validation weaknesses).

Question 30: What is 'defect clustering' and why does it matter in exploratory testing?

The observation that most defects concentrate in a small number of modules, guiding future testing effort (Correct answer)
A reporting technique that combines related bugs into one report
The practice of grouping defects by their root cause
Automatic sorting of defects by severity in the bug tracker

Correct answer: The observation that most defects concentrate in a small number of modules, guiding future testing effort

Defect clustering (Pareto's 80/20 rule in testing) shows that most bugs appear in a few modules, helping testers focus effort where defects accumulate.

Exploratory Testing Certification

A certification exam validating skills in exploratory testing methodology, including session-based test management, charter writing, bug hunting heuristics, defect investigation, risk-based exploration, and session reporting and debriefing.

Questions

35 min

Time Limit

70%

To Pass

Checking for saved progress...

Exam Rules

You can skip questions and return to them later
Flag questions for review before submitting
No feedback shown until you submit the entire exam
Unanswered questions count as wrong — answer everything
10 pretest questions are mixed in and don't affect your score
Timer auto-submits when time runs out
Your progress is auto-saved every 30 seconds