Session-based testing: Difference between revisions

Revision as of 01:43, 5 December 2006

Revision as of 23:02, 23 February 2007

Line 1:

{{context}}

'''Session-based testing''' is 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, product sustained product improvement. The improved test results can help putenable the case forcode changechanges 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 nonnot 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.