Defect Sensitivity

Currently Testimony can filter and work defects based on their priority, i.e. Critical, High, Medium, Low. The problem with this is there could be many Defects with the same priority and we have no way of knowing which of these are the most important ones.

Defect Sensitivity introduces a new metric called ‘Impact Score’ that allows the customer to allocate a score for a defect based upon various criteria. This ‘Impact Score’ is automatically calculated (if “Perform Impact Calculation” is turned on in the propose defects program). Default configuration is provided with 2.50.

The possible categories that can be used to calculate the ‘Impact Score’ are:

• Actual Message Type
• Component
• Failure Reason
• Object Type
• Object Pass Rate
• Priority
• Root Cause
• Scripts in Defect as a % of the Object
• Number of Scripts in Defect
• Object
• Number of Execution Queues
• Number of Unique Users
• Actual Message ID / Message Number
• Next Program / Screen
• System ID

The following tables are used in the configuration of defect sensitivity:

Defect Impact Weighting – /BTI/AUT_C_BTIW
Allows you to activate/deactivate a Category for the Impact Score calculation. Allows you to assign a weighting to a Category, by default they all ship with 1

Defect Impact Scoring – /BTI/AUT_C_BTIS
Allows you to assign Scores to Category Values

Defect Impact Value – /BTI/AUT_C_BTIV
Allows you to convert the Overall Impact Score into a ‘Textual’ value.

*Once you have calculated a defect sensitivity impact score for your defects, you can then see them within the defect management grid. You are then able to filter and sort when displaying the list of defects.