Hypothesis Based Testing (HBT) is a personal scientific test methodology that focuses on leveraging one’s intellect by enabling sharp goal focus, via tools for scientific thinking to rapidly assess cleanliness of software. The central theme of HBT is to hypothesis potential defect types (PDT) that can impede “cleanliness of software” and then “prove their presence”. […]
[Read by people] Clarity is key to what we do Value in what we deliver rather than activities we do. Evolve continuously and adapt. Do less and deliver more. Prove why we do and effectiveness of what we do. The focus of HBT is to enable you to “see clearly”. To ask questions 1. Are you clear about what […]
So what is the difference between the typical and HBT way of testing? Typically testing is seen as a series of activities whose outcome(goal) is dependant on the individual’s experience. In the case of the HBT goal clarity is sought for before commencement of any activities – “What are you testing and what are you […]
A scientific approach is about stating a problem, coming up with hypothesis and then proving/disproving them. Read more about in the Wikipedia link. In the context of testing, we state the problem in terms of end user expectations and then hypothesize potential types of defects that may be probable and then prove their presence. The picture below […]
The act of validation in HBT consists of “SIX Stages of DOING”. It commences with first two stages focused on a scientific approach to understanding of the customer expectations and the context of the software. One of the key outcomes of the first two stages is “Cleanliness Criteria” that gives a clear understanding of the […]
The various activities related to testing are done in SIX stages (S1-S6) and and these activities are performed scientifically using the EIGHT disciplines of thinking. Each discipline consists of a tiny tools that use THIRTY TWO core concepts that form the core of scientific thinking.
HBT is based on sound engineering principles geared to deliver the promise of guaranteeing cleanliness. Its core value proposition is about hypothesizing potential defects that may be present in the software and then allow you to engineer a staged detection model to uncover the defects faster and cheaper. The key value propositions from HBT are: […]
Common terms used in HBT and its definitions/meaning are listed in table below.
A problem can be solved in two ways : (1)using one’s experience or (2) by applying a well formed scientific approach that is implemented via a process. The former depends on the “skill of an individual” while the latter depends on the “strength of the process”. Skill-based problem solving can be seen as an ‘art/craft […]
Given that a need has to be meeting the expectation(s), how do we state the expectation? In HBT, this is stated as “cleanliness criteria” what quality aspects, where a criterion represents a characteristic/property that ‘a need’ shall have to satisfy. A collection of the entire criterion for ‘a need’ is termed “cleanliness criteria”, to enable […]