Exploratory Testing Certification — Questions and Answers

Question 1: How does a risk register inform exploratory test charter creation?

It assigns bug severity levels before testing begins
It identifies high-priority risk areas that should be translated into targeted charters (Correct answer)
It replaces the need for charters entirely
It provides a list of pre-written test cases for each risk

Correct answer: It identifies high-priority risk areas that should be translated into targeted charters

A risk register surfaces the areas and scenarios most likely to cause problems, which become the basis for targeted exploratory charters.

Question 2: What is the difference between a 'bug' and an 'observation' in an exploratory testing session report?

A bug is a confirmed defect, while an observation is a noteworthy finding that may warrant follow-up but is not yet classified as a defect (Correct answer)
Observations are made by test leads only, while bugs are reported by testers
An observation is a more severe category of defect than a bug
A bug requires a code fix while an observation requires a documentation update

Correct answer: A bug is a confirmed defect, while an observation is a noteworthy finding that may warrant follow-up but is not yet classified as a defect

Observations capture interesting behaviors, anomalies, or questions that need further investigation before being classified as defects or dismissed as intended behavior.

Question 3: What information should always be included in a test charter to make it actionable?

Target area or feature, available resources or constraints, and the goal or information sought (Correct answer)
Names of the developers who built the feature
Bug IDs from the previous release cycle
Estimated lines of code in the module under test

Correct answer: Target area or feature, available resources or constraints, and the goal or information sought

An actionable charter tells the tester where to look, what they have to work with, and what they're trying to learn or discover.

Question 4: What is the danger of focusing exclusively on happy-path testing in risk-based exploratory testing?

High-risk edge cases and error conditions may go untested (Correct answer)
The happy path will be over-tested, wasting resources
Performance risks will be automatically mitigated
The application will pass all user acceptance tests

Correct answer: High-risk edge cases and error conditions may go untested

Happy-path testing misses error handling, boundary conditions, and unusual usage patterns where high-impact defects often hide.

Question 5: What is a 'risk-based charter' in exploratory testing?

A charter approved by the risk management team
A charter targeting areas most likely to have high-impact defects (Correct answer)
A charter written to satisfy audit requirements
A charter that lists all known bugs to retest

Correct answer: A charter targeting areas most likely to have high-impact defects

Risk-based charters focus testing effort on areas with the highest potential impact if defects are present.

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

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 a charter is updated mid-sprint to reflect new requirements
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 7: What is a 'reproducibility rate' in defect reporting?

The ratio of bugs to test sessions
How consistently a defect can be triggered using the same steps (Correct answer)
The percentage of bugs filed that are accepted
How quickly a developer can fix the defect

Correct answer: How consistently a defect can be triggered using the same steps

Reproducibility rate reflects whether a defect occurs every time, sometimes, or rarely when the reproduction steps are followed.

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

Business analysts write all charters during requirements gathering
Only senior test managers are authorized to write charters
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)

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 primary goal of an exploratory testing debrief session?

To review session findings, assess coverage, identify follow-up actions, and communicate risk status to the team (Correct answer)
To convert all session notes into scripted test cases for the regression suite
To formally sign off on the completion of exploratory testing for a feature
To evaluate individual tester performance based on the number of bugs found

Correct answer: To review session findings, assess coverage, identify follow-up actions, and communicate risk status to the team

A debrief transforms raw session notes into actionable insights by reviewing what was found, what was covered, and what needs further attention.

Question 10: What is the role of metrics in evaluating the effectiveness of an exploratory testing program?

Metrics are only useful in scripted testing where pass/fail counts are available
Metrics like bugs per session, session coverage percentage, and debrief frequency help identify trends and improve testing quality over time (Correct answer)
The only meaningful metric in exploratory testing is the total number of bugs filed
Metrics undermine exploratory testing by imposing a scripted mindset on a creative process

Correct answer: Metrics like bugs per session, session coverage percentage, and debrief frequency help identify trends and improve testing quality over time

Well-chosen metrics for exploratory testing provide management visibility and help testers improve without reducing exploration to mechanical execution.

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

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

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 12: What does 'defect isolation' mean in exploratory testing?

Assigning the defect to an isolated developer
Retesting the defect in a separate environment
Moving all defects to a separate tracking system
Narrowing down the exact conditions under which the defect occurs (Correct answer)

Correct answer: Narrowing down the exact conditions under which the defect occurs

Defect isolation identifies the minimal, specific conditions that trigger the bug, making it easier for developers to diagnose.

Question 13: What is the appropriate response when a tester consistently fails to complete their charters within the allotted session time?

Switch to scripted testing to ensure all planned steps are completed
Review charter scope and either reduce it or extend session duration based on the complexity of the area (Correct answer)
Double the number of testers assigned to each charter
Remove the tester from the project due to poor performance

Correct answer: Review charter scope and either reduce it or extend session duration based on the complexity of the area

Persistent time overruns signal that charters are over-scoped or the product area is more complex than estimated, requiring charter or scheduling adjustments.

Question 14: How should a tester handle a charter that turns out to be too broad for a single session?

Split it into multiple focused charters covering different aspects of the original scope (Correct answer)
Complete as much as possible and mark the rest as skipped
Request a longer session duration to cover all areas
Abandon the charter and create a scripted test suite instead

Correct answer: Split it into multiple focused charters covering different aspects of the original scope

A broad charter should be broken into smaller, focused charters so each session has a manageable and meaningful scope.

Question 15: Which of the following best represents 'knowledge transfer' as a benefit of exploratory testing?

Managers can read test logs without attending debriefs
Testers develop deep application understanding that improves future testing and team knowledge (Correct answer)
Test scripts are reusable by automation engineers
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 16: How does knowledge of recent code changes inform risk-based exploratory testing?

Recent changes should be tested only by the developer who wrote them
Areas with recent changes are higher risk because new code introduces new defects and may break existing behavior (Correct answer)
Code change history is irrelevant to exploratory testing priorities
Recent code changes reduce risk because they represent the most thoroughly reviewed code

Correct answer: Areas with recent changes are higher risk because new code introduces new defects and may break existing behavior

Code change hotspots are proven defect attractors; recent changes, large refactors, and integration of new dependencies all increase the probability of defects.

Question 17: Which metric is most useful for evaluating the quality of exploratory testing sessions over time?

Number of automated tests added
Lines of code covered by unit tests
Defect detection rate per session hour (Correct answer)
Number of test scripts executed

Correct answer: Defect detection rate per session hour

Defect detection rate per session hour helps teams gauge how effectively exploratory sessions are finding meaningful issues relative to time invested.

Question 18: What evidence should an exploratory tester typically attach to a defect report?

Screenshots, screen recordings, and relevant log files (Correct answer)
The complete session sheet
Only the tester's verbal description of the issue
The test charter for the session

Correct answer: Screenshots, screen recordings, and relevant log files

Visual evidence (screenshots, recordings) and logs give developers the context they need to understand and reproduce the defect.

Question 19: Which of the following is the most critical element of a useful defect report?

A long description of all related features
The tester's opinion of the root cause
Clear, minimal reproduction steps (Correct answer)
The development team's email addresses

Correct answer: Clear, minimal reproduction steps

Clear, minimal reproduction steps allow developers to quickly confirm and fix the defect without guessing what went wrong.

Question 20: How should exploratory testers handle 'intermittent bugs' when writing their reports?

Document all reproduction attempts, conditions observed, and frequency, even if consistent steps cannot be confirmed (Correct answer)
Mark intermittent bugs as 'works as designed' until they can be reproduced three times consecutively
Escalate intermittent bugs directly to the product owner without filing a formal report
Only report bugs that can be reproduced on demand; discard intermittent findings

Correct answer: Document all reproduction attempts, conditions observed, and frequency, even if consistent steps cannot be confirmed

Intermittent bugs can be serious even without guaranteed reproduction steps — documenting observed conditions and frequency gives developers useful context to investigate.

Question 21: When a defect cannot be reproduced by the developer, what should an exploratory tester do first?

Close the bug report as not reproducible
Re-file the same defect report without changes
Provide additional context such as environment details, test data, and a screen recording (Correct answer)
Escalate the issue directly to the product owner

Correct answer: Provide additional context such as environment details, test data, and a screen recording

Providing richer context — environment specifics, test data values, and recorded video — often helps developers reproduce elusive defects.

Question 22: In exploratory testing, what is the 'Saboteur Tour' designed to test?

The most commonly used happy paths
Error handling and recovery when things go wrong (Correct answer)
Performance under high load
Integration with third-party APIs

Correct answer: Error handling and recovery when things go wrong

The Saboteur Tour focuses on trying to make the application fail by providing bad data, wrong sequences, or unexpected inputs to test error handling.

Question 23: What is the role of the 'test lead' in SBTM?

To write all the test charters before sessions begin
To review session sheets, conduct debriefs, and ensure charters align with testing goals (Correct answer)
To execute test sessions personally and file all bugs
To coordinate with developers to fix bugs found during sessions

Correct answer: To review session sheets, conduct debriefs, and ensure charters align with testing goals

The test lead oversees SBTM by reviewing session outputs, debriefing testers, tracking metrics, and adjusting charters based on findings.

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

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

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 25: What is a 'risk list' and how is it used in exploratory test planning?

A compliance document listing all risks that must be signed off before release
A list of all open bugs ordered by severity in the bug tracking system
A prioritized list of potential failure areas used to guide charter creation and session scheduling (Correct answer)
A developer-provided list of known limitations in the current build

Correct answer: A prioritized list of potential failure areas used to guide charter creation and session scheduling

A risk list captures identified product and project risks so testers can create charters targeting the highest-priority areas first.

Question 26: A 'blind oracle' problem in testing occurs when:

The tester is unfamiliar with the testing environment
Automated tools cannot detect visual rendering defects
Testers lack domain knowledge to evaluate the application
There is no reliable reference to determine whether observed behavior is correct (Correct answer)

Correct answer: There is no reliable reference to determine whether observed behavior is correct

A blind oracle problem arises when there is no clear mechanism or reference available to judge whether the system's actual output is correct or incorrect.

Question 27: What is meant by 'coverage-driven charter creation'?

Writing new charters to cover every bug found in the previous release
Writing charters based on a coverage outline to ensure all important product areas are explored (Correct answer)
Creating charters based only on code coverage reports from automated tests
Generating charters automatically from requirements documents using AI tools

Correct answer: Writing charters based on a coverage outline to ensure all important product areas are explored

Coverage-driven charter creation uses a coverage outline to systematically identify and fill gaps in exploratory testing across all important product areas.

Question 28: What is the role of 'exploratory testing notes' in defect reporting?

They document the test plan for the session
They list all test cases executed during the session
They provide context about what the tester was doing when the defect was found (Correct answer)
They replace the defect report entirely

Correct answer: They provide context about what the tester was doing when the defect was found

Session notes give developers context about the testing journey that led to finding the defect, which can aid in root cause analysis.

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

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

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 30: When using the 'History' oracle heuristic, a tester primarily compares:

Test results against industry compliance standards
Current defects against archived bug databases
The current product version against previous versions (Correct answer)
Actual output against user documentation

Correct answer: The current product version against previous versions

The History heuristic uses prior versions of the product as a reference point, allowing testers to detect regressions or unexpected behavioral changes in newer releases.

Question 31: What is 'testing narrative' as part of exploratory test reporting?

A qualitative description of what was tested, how the tester approached it, and what they learned about the product's behavior (Correct answer)
A story written for marketing about the software's quality features
A bug report written in narrative form instead of a structured template
A formal document describing the testing methodology used in the project

Correct answer: A qualitative description of what was tested, how the tester approached it, and what they learned about the product's behavior

A testing narrative adds human context to session data, explaining the reasoning behind testing decisions and providing richer insight than raw metrics alone.

Question 32: In agile projects, when should exploratory test charters typically be created?

Only after all automated tests pass
During sprint planning or as user stories are refined (Correct answer)
After the product is fully deployed to production
Only during regression testing phases

Correct answer: During sprint planning or as user stories are refined

Charters are most valuable when created early, during sprint planning or refinement, so testers are prepared when development is done.

Question 33: What is 'triage' in the context of exploratory testing findings?

The process of prioritizing and categorizing bugs found during exploration by severity and business impact (Correct answer)
A medical analogy used to describe performance testing under high user loads
Removing duplicate bugs from the tracking system after a session ends
The process of assigning exploratory test sessions to testers based on skill level

Correct answer: The process of prioritizing and categorizing bugs found during exploration by severity and business impact

Bug triage applies priority and severity classification to exploratory findings so development teams can focus fixes on the most impactful defects first.

Question 34: How should a tester adjust their exploratory approach when testing a safety-critical feature?

Test it exactly the same way as non-critical features for consistency
Apply deeper, more thorough exploration with documented session notes and additional negative and boundary testing (Correct answer)
Reduce exploratory testing on safety-critical features to avoid accidental production data changes
Leave safety-critical features to automated regression suites only

Correct answer: Apply deeper, more thorough exploration with documented session notes and additional negative and boundary testing

Safety-critical features warrant more intensive exploration, more diverse test conditions, and thorough documentation because the cost of failure is extremely high.

Question 35: How should a tester handle a charter that proves too broad during a session?

Note the scope issue, narrow the focus, and suggest splitting into multiple charters (Correct answer)
Abandon the session and start a new one
Continue testing everything in the charter regardless
Request a new application build

Correct answer: Note the scope issue, narrow the focus, and suggest splitting into multiple charters

When a charter is too broad, the tester should narrow focus mid-session and recommend splitting it for future sessions.

Question 36: What does 'time-boxing' provide in an exploratory testing session?

An automated timer that pauses the application under test
A fixed duration that creates focus and makes sessions reportable and manageable (Correct answer)
A legal constraint on how long a tester can work
A way to measure the lines of code tested per hour

Correct answer: A fixed duration that creates focus and makes sessions reportable and manageable

Time-boxing (e.g., 90-minute sessions) keeps exploration focused, prevents rabbit holes, and makes effort visible to managers.

Question 37: What is the benefit of creating charters collaboratively with developers or product managers?

It guarantees 100% code coverage
It ensures charters reflect product knowledge and risk areas the team values (Correct answer)
It removes the tester's responsibility for finding defects
It replaces the need for a formal test plan

Correct answer: It ensures charters reflect product knowledge and risk areas the team values

Collaborative charter creation surfaces domain knowledge and ensures testing aligns with the team's most critical concerns.

Question 38: What is the significance of 'reproducibility' when reporting a bug found during exploratory testing?

Reproducibility only matters for performance defects, not functional ones
Reproducibility is irrelevant in exploratory testing since all findings are qualitative
A reproducible bug report provides the steps needed to reliably trigger the defect, making it actionable for developers to fix (Correct answer)
A bug must be reproduced in automation before it can be logged in the tracking system

Correct answer: A reproducible bug report provides the steps needed to reliably trigger the defect, making it actionable for developers to fix

A reproducible bug is far more useful than a one-time observation because developers need consistent steps to isolate the cause and verify the fix.

Question 39: Which of the following is the BEST source of information for writing exploratory test charters?

Previous automated test results alone
The bug tracker history exclusively
Product requirements, risk analysis, and stakeholder input (Correct answer)
Only the developer's source code

Correct answer: Product requirements, risk analysis, and stakeholder input

Effective charters are derived from requirements, risks, and stakeholder input to ensure relevant coverage.

Question 40: What is 'regression' in the context of defect management?

A defect that occurs in the database layer
A defect found exclusively during exploratory testing
A defect that only affects older versions of the software
A defect that was previously fixed but reappeared in a later build (Correct answer)

Correct answer: A defect that was previously fixed but reappeared in a later build

A regression is when a previously working feature breaks again, typically due to a new code change.

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

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

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 42: Why should exploratory testers include the application version in defect reports?

To help developers identify which build introduced the defect (Correct answer)
To determine which tester filed the bug
To calculate the defect's age in the bug tracker
To satisfy regulatory compliance requirements

Correct answer: To help developers identify which build introduced the defect

Including the build/version number helps developers pinpoint when the defect was introduced and verify fixes in the correct version.

Question 43: When resources are limited, how should a risk-based exploratory tester allocate session time?

Spend the most time on high-likelihood, high-impact risk areas first (Correct answer)
Test only the features the test manager assigns
Divide time equally across all features regardless of risk
Focus on the newest features exclusively

Correct answer: Spend the most time on high-likelihood, high-impact risk areas first

Limited time should be invested where testing value is highest — the areas where failure is both likely and impactful.

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

To satisfy a mandatory regulatory requirement for all software projects
To avoid being blamed for defects found after release
To justify requesting additional testing resources for the next project
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 45: Why is 'user perspective testing' an effective bug hunting technique?

It is required by accessibility compliance standards in the US
It replaces the need for performance testing in exploratory sessions
It guarantees that all edge cases in the codebase are covered
It surfaces usability defects and workflow issues that technical testing often misses (Correct answer)

Correct answer: It surfaces usability defects and workflow issues that technical testing often misses

Testing from the user's perspective reveals workflow breaks, confusing UI behaviors, and usability defects that technical testers focused on functionality may overlook.

Question 46: In exploratory testing terminology, what is a 'charter'?

A list of all known bugs to retest
A legal document authorizing testing activities
A formal sign-off from the product owner
A brief statement defining the goal and scope of a testing session (Correct answer)

Correct answer: A brief statement defining the goal and scope of a testing session

A charter is a concise statement—often in the format 'Explore X with Y to discover Z'—that guides the focus of an exploratory testing session.

Question 47: Which is an example of a software dashboard integration offered by Global App Testing?

Wordpress
Jira (Correct answer)
Google Drive
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 48: What is the key knowledge difference between a 'checklist' used in exploratory testing and a traditional test script?

Checklists remind testers what to cover but leave execution approach open; scripts dictate exact steps (Correct answer)
Checklists are generated by AI; test scripts are written by humans
Test scripts are informal; checklists are legally binding documents
Checklists are only used for regression testing

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.

Question 49: What is a 'risk heuristic' in exploratory testing?

A formal statistical risk model used by project managers
A rule of thumb that helps testers identify likely risk areas based on experience (Correct answer)
A tool that automatically scores the risk level of each feature
A mandatory checklist of risks to evaluate before each session

Correct answer: A rule of thumb that helps testers identify likely risk areas based on experience

Risk heuristics are experienced-based patterns (e.g., 'new code is riskier than stable code') that help testers locate likely problem areas.

Question 50: What role does 'note-taking' play during an exploratory bug hunting session?

It replaces the need for a formal bug tracking system during exploratory sessions
It captures test ideas, observations, and findings in real time so nothing is forgotten and the session can be reconstructed (Correct answer)
It is required by audit standards for regulated industries only
It documents the exact steps taken so they can be converted into scripted test cases later

Correct answer: It captures test ideas, observations, and findings in real time so nothing is forgotten and the session can be reconstructed

Real-time note-taking ensures observations, ideas, and potential bugs are recorded as they occur, making the session reproducible and the tester's reasoning traceable.

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

60 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