February 23, 2012
Hypothesis Based Testing* is a unique, scientific and personal methodology that helps the testers deliver clean software since it is defect centric and adapts a quality growth model.
As opposed to traditional test methodologies that focus on defining and implementing activities and tools that can help discover potential defects in the software, Hypothesis Based Testing focuses on identifying and defining the most probable defects first.
Once the potential defects are identified, testing activities to ensure that these defects are uncovered and fixed are carried out. In case of traditional test methodologies, the ultimate discovery of defects still depends upon the experience of the tester. But with HBT*, that is not the case.
Take any software, the below are the guidelines as to how HBT actually is implemented.
In short, HBT* consists of the below six stages –
Stage I - Understand the expectations with respect to the software/product by grasping its features, attributes, business criticality etc. Align the expectations and objectives with business goals.
Stage II - Understand the context of testing in terms of project requirements and the cleanliness criteria.
Stage III - Formulate an appropriate hypothesis and potential defects catalog.
Stage IV - Devise proof with test strategy, test design and requirements traceability matrix. Also define measurements and a clear-cut plan of action.
Stage V- Identify and Select appropriate tools. Perform tooling benefit analysis.
Stage VI - Assess the software product and perform analysis based on testing results. Carry out test management and defect management activities.
Thus, HBT* is defect centric testing which can help the test team prioritize the requirements and utilize the available resources in the most appropriate and beneficial manner.
*STAG Software – is copyright and IPR holder of HBT and T Ashok Founder and CEO of STAG Software, the Architect of HBT.
Download the Enterprise Version of TestingWhiz now!