Despite the good testing that we do, defects do escape and are found by end users. As a good software developer our objective is to analyse, learn and strengthen our practices to become stronger. How can HyBIST help here?
The key steps in HyBIST for defect analysis are:
- First tag the defect to the appropriate EUTs
- Next analyse each escaped defect and identify the PDT it belongs to. I.e. Classify these in the Quality levels that should have caught this.
- Now analyse if this defect is a conformance defect(correct path not ok) or a robustness defect(error path not ok).
- Analyse if there was indeed test scenario(s)& cases that could have uncovered this. If Yes, analyse if this was indeed executed or not. If No, we need to add additional test cases.
- Lastly analyse if we had found the same or similar issues in our earlier cycles of testing at all.
So how does HyBIST style analysis help?
- (1) tells us clearly which parts are unclean
- (2) tells us what tests are weak (how good is our strategy)
- (3) tell us as how good our focus/objective is – largely conformance only or conformance+robustness and strength of test design
- (4) & (5) tells us the strength of our process