figuring out a factor for testing tickets: Bugs are bad, passbacks are good

td3201

New member
Joined
Nov 25, 2017
Messages
4
Sorry for the vague subject. Have some data in excel that looks like this:

TicketTestingTimePassBacksBugs
10.0510
21.1200
32.322
43.681

I need to figure out a mathematical way to determine how well people are doing in testing tickets. Bugs are bad, passbacks are good, and, in general, the less testing time the better unless bugs are created. Passbacks should provide the tester with a credit against the negative of having a bug but not in a 1:1 way.

Ideally, this is presented as a factor of some sort that I can then use as a scale of good to bad.

Here's some subject analysis to help align what we're looking to create a factor around:
Ticket #1: Very good. They spent very little time, had a passback and had no bugs
Ticket #2: Good. Spent a little more time, no passbacks, no bugs
Ticket #3: Bad. 2 bugs is bad regardless of the time spent but they spent quite a bit of time which also isn't good. However, they had 2 passbacks which lessens the blow of the 2 bugs slightly.
Ticket #4: Bad. They spent a ton of time testing, had a lot of passbacks (good), but still ended up having 1 bug.

Ideally, I'm creating a single formula that factors all of this in and I can then apply a bad to good range on it. Thoughts?
 
It's more than simply vague. You've managed to narrow the problem down to infinitely many possibilities. Most importantly, I think, is that most of the resolution will have to come from how YOU feel about it and how YOU think the various elements should be related. So, give us something to work with. It's your formula. You're the one who will have to live with it. It's development should come from you.
 
I agree. Was hoping for some ideation but also agree that it's too early. Let me noodle further.
 
Top