What is a PDT?

Potential Defect Type (PDT) is a set of Potential Defect (PD – A possible problem/issue that could exist in the software application) grouped into a category. This is based on an HBT core concept “Defect centricity principle”. Hypothesizing PDT is done by considering the various aspects (Data, Behavior/Business Logic, Internal structure, External environment and Usage […]

Read More

What is a ‘Quality Level’?

Typically we have always looked at the levels of testing like unit, integration and system from the aspect of the “size” of entity-under test. Unit test is typically understood as being done on the smallest component that can be independently tested. Integration test is typically understood as being done once the various units have been […]

Read More

What is a ‘Test Type’?

Clarity of purpose is a key tenet of HBT. And therefore the act of uncovering specific types of defects  should be intensely goal focused.  This means that a type of test shall only uncover specific type of defects. The act of test type identification results in specific types of tests to be executed at each quality levels […]

Read More

Quality Levels – in HBT

In HBT, there are NINE pre-defined quality levels where the lowest quality level focuses on input correctness progressively going onto the highest quality level to validate if the intended business value is indeed delivered. The picture below outlines this:

Read More

Levels, PDTs and Test types

The objective of each level is to focus on specific PDTs (potential defect types). And to do this it requires specific types of tests to be executed. The picture below shows the relationship between levels, PDTs and Test types. Note that PDTs are numbered only and the exact PDT is not listed. This enables one […]

Read More

What is ‘Countability’?

‘Countability’ is a property of the test cases that relates to sufficiency.  How do we judge that the ‘count of test cases’ are indeed no-more or no-less? Is there a way to justify the number of test cases? Test design in HBT is done in two stages, first generating test scenarios and then later test […]

Read More

What is ‘Fault Traceability’?

Requirement traceability is about ensuring that each requirement does indeed have test case(s). So after we design test cases, we map test cases to requirements to ensure that all the requirements are indeed being validated. This is typically used as a measure of test adequacy. Let us consider a situation wherein there is exactly one […]

Read More