Session-based testing: Difference between revisions

Revision as of 16:50, 16 July 2015

Latest revision as of 11:26, 16 August 2025

(11 intermediate revisions by 8 users not shown)

Line 1:

'''Session-based testing''' is a [[software test]] method that aims to combine [[accountability]] and [[exploratory testing]] to provide rapid defect discovery, creative on-the-fly [[test design]], management control and metrics reporting. The method can also be used in conjunction with [[scenario testing]]. Session-based testing was developed in 2000 by Jonathan and [[James Marcus Bach|James Bach]].

Session-based testing can be used to introduce measurement and control to an immature test process and can form a foundation for significant improvements in productivity and error detection. Session-based testing can offer benefits when formal [[requirement]]s are not present, incomplete, or changing rapidly.

Line 7:

===Mission===

The mission in Session Based Test Management identifies the purpose of the session, helping to focus the session while still allowing for exploration of the system under test. According to Jon Bach, one of the co-founders of the methodology, the mission tellsexplains us “what"what we are testing or what problems we are looking for.” "<ref name=SBTM>First published 11/2000 in STQE magazine, today known as Better{{cite Softwareweb |url=http://www.stickymindssatisfice.com/BetterSoftwarearticles/magazinesbtm.asppdf |title=Session-Based Test Management |first=Jonathan |last=Bach |date=November 2000}}</ref>{{rp|1–2}}

===Charter===

A charter is a goal or agenda for a test session. Charters are created by the test team prior to the start of testing, but they may be added or changed at any time. Often charters are created from a [[specification]], [[test plan]], or by examining results from previous sessions.

===Session===

Line 32:

===Debrief===

A debrief is a short discussion between the manager and tester (or testers) about the session report.

Jonathan Bach uses the aconymnacronym PROOF to help structure his debriefing. PROOF stands for:-

* Past. What happened during the session?

* Results. What was achieved during the session?

* Obstacles. What got in the way of good testing?

* Outlook. What still needs to be done?

* Feelings. How does the tester feel about all this?<ref>http://www.satisfice.com/articles/sbtm.pdf< name=SBTM/ref>{{rp|9–10}}

===Parsing results===

Line 46:

==See also==

{{portal|Software Testing}}

*[[Software testing]]

*[[Test case (software)|Test case]]

*[[Test script]]

*[[Exploratory testing]]

Line 57:

==External links==

*[{{cite web |url=http://www.satisfice.com/sbtm/ |title=Session-Based Test Management: Site]A method for measuring and managing exploratory testing |date=November 2000 |publisher=Satisfice, Inc.}}

*[{{cite web |url=http://wwwmail.quardev.com/content/whitepapers/how_measure_exploratory_testing.pdf |title=How to Manage and Measure ET]Exploratory Testing |first=Jon |last=Bach |year=2006 |publisher=Quardev}}

*{{cite web |title=SBT Lite: Components of Session-Based Test Management |url=http://mail.quardev.com/content/whitepapers/SBTMLite_samkalman.pdf |first=Sam |last=Kalman |date=May 2007 |publisher=Quardev}}

*[http://www.quardev.com/articles/sbt_lite Session-Based Test Lite]

*[{{cite web |url=http://www.workroom-productions.com/papers/AiSBTv1.2.pdf |title=Adventures in Session-Based Testing] |first1=James |last1=Lyndsay |first2=Niel |last2=van Eeden |date=27 May 2003}}

*[http://www.satisfice.com/articles/sbtm.pdf Session-Based Test Management]

*[http://www.stickyminds.com/BetterSoftware/magazine.asp Better Software Magazine]

[[Category:Software testing]]