| ||
| ||
Bugs are important for the testing team like diamonds for the women. Funny statement , let’s see how we can map the 4 C's which are four variables that are used to calculate the value of a diamond to be used to evaluate bugs, “Clarity, Color, Cut, and Carat Weight”.
But first let us define the term bug which will be used here,
The ISTQB standards define a cycle about, A human being can make error/mistake which produces a defect/fault/bug/ in the code, in software or a system, or in a document. If a defect in code is executed, the system will fail to do what it should do (or do something it shouldn’t), and causing a failure.
We’ll use the term Bug instead of failure.
Bug Clarity describes the clearness or purity of a bug. This is determined by the effect, and location of the internal (inclusions) and external (blemishes) imperfections. Based on that we can define the most defected area and describes the Defect Clustering, Bug Color describes the impact and cause. Bug Cut describes the severity. This can range from cosmetics to showstoppers, business or GUI, Low or critical, the categorization of the business processes and the testing analysis layers impacting the severity clustering, we can assume the severity clustering based on the layers (Business, Application, Database and Integration layers). Bug Carat is the unit of weight for the bugs, we can simulate it by the generated values from the Risk Based Testing/Analysis for each test case we can measure it with the found bugs per each test case. Samer Desouky, Test Leader, MCS ISTQB Certified 17/12/2009 11:37 AM | ||
| Entry 5 of 5 |
| Last Page | Next Page |