Exploratory Testing & SBTM

Adhoc Testing:  Learn the application then test it.
Exploratory Testing:  Test the application while learning (or) tester test a application by exploring with his previous experience and based on the application tester writes test cases.
Example:
If a QA is asked to test an application without any concrete documents.
Adhoc: Gather information about the app from all possible sources and document and then test.
Exploratory: Gather, Document and Test the application simultaneously.
--------------------------------------------------------------------------------------------------------------
About SBTM - Session Based Test Management ?

• For each session, a session sheet is made. The session sheet consist of the mission of testing, the tester details, duration of testing, the TBS metrics along with the data related to testing like the bugs, notes, issues etc.
• Data files if any used in the testing would also be enclosed.
• Data collected during different testing sessions are collected and exported to Excel or some database.
• All the sessions, the bugs reported etc can be tracked using the unique id associated with each
• This is easy for the client as well to keep track.
• This concept of testers testing in sessions and producing the required output which are traceable is called as Session based test management.

A session can be broadly classified into three tasks (namely the TBS metrics).

• Session test up: Time required in setting up the application under test.
• Test design and execution: Time required scanning the product and test.
• Bug investigation and reporting: Time required finding the bugs and reporting to the concerned.

The entire session report consists of these sections:

• Session charter (includes a mission statement, and areas to be tested)
• Tester name(s)
• Date and time started
• Task breakdown (the TBS metrics)
• Data files
• Test notes
• Issues
• Bugs