Session-based testing: Difference between revisions

Revision as of 04:42, 10 July 2007

Revision as of 05:34, 10 July 2007

Line 1:

'''Session-based testing''' is a software test method that providescombines [[accountablity]] and [[exploratory testing]] to provide rapid defect discovery through, creative on-the-fly test design, combined with management control and metrics reporting. ItThe ismethod morecan closelyalso relatedbe toused [[Exploratoryin test]]ingconjunction than towith [[Scenario test]]ing,. but the concepts can be used in conjunction. Session-based testing was developed in 2000 by Jon andJonathan James Bach.

{{context}}

'''Session-based testing''' is a software test method that provides rapid defect discovery through creative on-the-fly test design, combined with management control and metrics reporting. It is more closely related to [[Exploratory test]]ing than to [[Scenario test]]ing, but the concepts can be used in conjunction. Session-based testing was developed in 2000 by Jon and James Bach.

It is a controlled and improved ad-hoc testing that is able to use the knowledge gained by a test team as a basis for ongoing, sustained product improvement. The improved test results can help enable code changes throughout development, and provide ways in which the testing team can build on the initial processes to arrive at a better overall testing outcome. 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 is ideal when formal requirements are not present, incomplete, or changing rapidly.

It is a controlled and improved ad-hoc testing that is able to use the knowledge gained by a test team as a basis for ongoing, sustained product improvement. The improved test results can help enable code changes throughout development, and provide ways in which the testing team can build on the initial processes to arrive at a better overall testing outcome. 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 is ideal when formal requirements[[requirement]]s are not present, incomplete, or changing rapidly.

The main tool in session-based testing is the charter or test point. Charters and test points list what should be tested and provide a record of what was tested. They should take between two and four hours to execute. Testers using Session-based testing plan their testing daily and new revelations on what needs to be tested are added as tests are executed.

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

===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 on the fly and records their progress.

===Session Report===

The session report records the test session. Usually this includes:

*Charter.

*Area tested.

*Detailed notes on how testing was conducted.

*A list of any [[software bug|bug]]s found.

*Percentage of the session spent on the charter vs investigating new opportunities.

*Percentage of the session spent on:

**Testing - creating and executing tests.

**Bug investigation / reporting.

**Session setup or other non-testing activities.

*Session Start time and duration.

===Debrief===

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

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

Testers using session-based testing can adjust their testing daily to fit the needs of the project. Charters can be added or dropped over time as tests are executed and/or requirements change.

==External links==

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

*[http://www.workroom-productions.com/papers/AiSBTv1.2.pdf Adventures in Session-Based Testing]

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

Line 19 ⟶ 46:

[[Category:Software testing]]

{{soft-eng-stub}}