DEV Community

Discussion on: How I Measured The Software Testing Quality 

Collapse
 
codemouse92 profile image
Jason C. McDonald

Ahh, I see the inherent difference between our teams! I can agree that origins would be crucial for yours, since you have different Design, Coding, and SQA teams. By contrast, at my company, one team covers the entire process.

I can also see how origin might be useful to my team in limited situations, but in general, we don't have the time to figure out origin on every bug.That aside, I'll make room in my bug tracker for an optional origin field.


As to weights, if I'm understanding this, the longer a bug lives, the higher the score it needs, yes? If so, it's actually pretty simple, although I can't really set up the table here.

Using the same multipliers...

|       | Req | Des | Code | SQA | Prod | Total |
| MULT  | x0  | x0  | x1   | x2  | x3   |       |

If a bug is caught in Prod (3), and origin at Code (1), then SCORE = CAUGHT - ORIGIN = 3 - 1 = 2.

Similarly, if a code is caught in Prod (3) and origin at Design (0), then 3 - 0 = 3.

Like that?

Thread Thread
 
kashifkazi profile image
Kashif Gul Kazi

Ahh, what a math!
Yes, the longer a bug lives, the higher the score

Thread Thread
 
codemouse92 profile image
Jason C. McDonald

I don't know if I ever told you, but I absorbed this idea into Quantified Task Management: standards.mousepawmedia.com/qtm.html

I also talked about it here recently: legacycode.rocks/podcast-1/episode...