Session-based testing: Difference between revisions

Revision as of 18:30, 7 September 2013

Revision as of 02:53, 13 December 2013

Line 2:

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.

{{portal|Software Testing}}

==Elements of session-based testing==

Line 11 ⟶ 9:

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 tells us “what we are testing or what problems we are looking for.” <ref>First published 11/2000 in STQE magazine, today known as Better Software http://www.stickyminds.com/BetterSoftware/magazine.asp</ref>

===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===

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.

Line 48 ⟶ 46:

==See also==

{{portal|Software Testing}}

*[[Software testing]]

*[[Test case]]

Line 67 ⟶ 66:

[[Category:Software testing]]

{{soft-eng-stub}}