Content deleted Content added
Mkltesthead (talk | contribs) m →Mission |
Jnestorius (talk | contribs) |
||
(21 intermediate revisions by 15 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
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.
==Elements of session-based testing==
Line 9 ⟶ 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
===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
===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
===Session report===
Line 34 ⟶ 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===
Line 48 ⟶ 46:
==See also==
*[[Software testing]]
*[[Test case (software)|Test case]]
*[[Test script]]
*[[Exploratory testing]]
*[[Scenario testing]]
==References==
Line 59 ⟶ 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]]
|