Content deleted Content added
Tag: possible vandalism |
Jnestorius (talk | contribs) |
||
| (33 intermediate revisions by 21 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 [[
Session-based testing can be used to introduce measurement and control to an immature test process
▲==Elements of session-based testing==
▲===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 may be added or changed at any time. Often charters are created from a [[specification]], [[test plan]], or by examining results from previous test sessions.▼
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 explains "what we are testing or what problems we are looking for."<ref name=SBTM>{{cite web |url=http://www.satisfice.com/articles/sbtm.pdf |title=Session-Based Test Management |first=Jonathan |last=Bach |date=November 2000}}</ref>{{rp|1–2}}
===Session=== ▼
An uninterrupted period of time spent testing, ideally lasting one to two hours. Each session is focused on a charter, but testers can also explore new opportunities or issues during this time. The tester creates and executes [[test case]]s based on ideas, heuristics or whatever frameworks to guide them and records their progress. This might be through the use of written notes, video capture tools or by whatever method as deemed appropriate by the tester.▼
===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
▲An uninterrupted period of time spent testing, ideally lasting one to two hours. Each session is focused on a charter, but testers can also explore new opportunities or issues during this time. The tester creates and executes
===Session report===
Line 29 ⟶ 32:
===Debrief===
A debrief is a short discussion between the manager and tester (or testers) about the session report.
* 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
===Parsing results===
With a standardized Session Report, software tools can be used to [[parsing|parse]] and store the results as [[aggregate data]] for reporting and metrics. This allows reporting on the number of sessions per area or a breakdown of time spent on testing, bug investigation, and setup / other activities.
==Planning==
Line 44 ⟶ 46:
==See also==
*[[Software testing]]
*[[Test case (software)|Test case]]
*[[Test script]]
*[[Exploratory testing]]
*[[Scenario testing]]
==References==
Line 55 ⟶ 57:
==External links==
*
*
*{{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}}
*
[[Category:Software testing]]
| |||