Delivering clean software is challenging
The act of producing clean software is challenging. In other disciplines of engineering, the final artifacts are physical in nature and therefore assessment of quality (or cleanliness) is accomplished by validating the physical behavior. Software however poses an interesting challenge as expectations in the mind are translated into non-physical entities (code) whose behavior needs to be assessed for correctness. Incorrectness i.e lack of quality is not limited to flaws in code, but occur due to inappropriate design, incorrect understanding of intentions, complex interactions due to the deployment environment and finally due to interesting usage by the end users.
Traditional test approach have relied on strength of the process and the capability of the individual to ensure high quality in the given cost and time constraints. They lack the scientific rigor to enable full cost optimization and more often rely on automation as the means to driving down cost and cycle time.
For example, they do not provide a strong basis for assessing the quality of test cases in terms of their defect finding potential and therefore improve effectiveness and efficiency.
HBT on the other hand enables you to set a clear goal for cleanliness, derive potential types of defect and then devise a “good net” to ensure that these are caught as soon as they get injected. It is intensely goal-oriented and provides you with a clear set of milestones allowing you to manage the process quickly and effectively.
The HBT series of masterclasses address the entire spectrum of software development cycle spanning from understanding customer expectations to test automation. There are specialized masterclasses that cover the entire test life-cycle like strategy and planning, test design, load and performance testing.