October 2, 2016 at 2:57 am #13842ArchanaParticipant@archana
When you start testing of a new application, do you have a rate of finding defects in mind (say 1 defect every 10 minutes on an average)?
Do you focus on that?
Do you calculate the rate at the end of testing?October 6, 2016 at 9:37 pm #13877JesperParticipant@jesper-lindholt-ottosen
I don’t focus on defect detection rates or Meantime between failures MTBF. What mostly interests me is MTTR – mean time to recover, ie how fast the defect turn around time is. Sometimes it can be interesting to look at how many “iterations” a defect have before it is closed, but that depends on the number of dev teams.
I wrote about the rate of active defects here:October 12, 2016 at 3:11 pm #13942ArchanaParticipant@archana
Pretty interesting article that.
I too do not focus on defect detection rate during testing. But at the end of the testing, I do check it once.October 19, 2016 at 10:36 am #14004AugustoParticipant@augusto-evangelisti
I tend to focus more on delivering value to my customersNovember 14, 2016 at 10:23 pm #14323AlinParticipant@groza-alin88
I don’t use any defect detection rate. Personally, I don’t think it is ok to define this rate because defects have different severity. You can find 10 minor bugs in one day and 2 major bugs in the next day. Of course, there can be used metrics with various weights for defects characteristics (severity, likelihood etc.) but you risk focusing more on this metrics/rates and less on testing and quality.
I have seen managers that use this defect detection rate as a target for the testing team during a specific iteration/sprint, but the rate is set by the managers and not by the testers
AlinApril 27, 2017 at 10:44 am #16102Ronan HealyKeymaster@ronan
Good post on it here too:May 10, 2017 at 1:49 pm #16247
- You must be logged in to reply to this topic.