Exploratory Testing Session-Based Test Management 2

Question 1

What is a debrief in the context of SBTM?

Accepted Answer

A meeting where testers review session results with a manager or team lead

Answer

A final sign-off document for a release

Answer

A summary report sent to stakeholders after each sprint

Answer

A code review session between developers and testers

Question 2

In SBTM, what is the purpose of tracking 'bugs per session'?

Accepted Answer

To measure tester productivity and identify high-risk areas of the product

Answer

To calculate the exact number of defects that will escape to production

Answer

To determine how many testers to hire

Answer

To replace the need for a test charter

Question 3

What should a tester do if they discover an interesting bug outside their current charter during a session?

Accepted Answer

Note it briefly and either file a new charter or return to it after the current session

Answer

Immediately stop the current session and investigate the new bug fully

Answer

Ignore it and continue with the original charter only

Answer

Escalate it to a developer immediately and end the session

Question 4

Which of the following best describes the concept of 'session time boxing'?

Accepted Answer

Limiting the session to a fixed time to maintain focus and enable consistent reporting

Answer

Restricting testers from testing features outside the sprint backlog

Answer

Setting a maximum number of bugs a tester can report per day

Answer

Scheduling only one test session per application module

Question 5

What is a 'thread' in SBTM terminology?

Accepted Answer

A specific testing activity or line of investigation within a session

Answer

A background automated test running during an exploratory session

Answer

A Jira ticket linked to a test charter

Answer

A sequence of scripted test steps

Question 6

How does SBTM enable test coverage tracking without scripted test cases?

Accepted Answer

By aggregating session charters to map tested areas against product features or risks

Answer

By using code coverage tools integrated with the test sessions

Answer

By counting the total number of sessions run per module

Answer

By comparing bugs found to the total lines of code