Comments on: QA Deathmatch

By: Anthony Damasco

Anthony Damasco — Fri, 25 Jul 2008 21:57:24 +0000

Great idea! That would make QA a lot easier to deal with. I doubt some of my co workers would go for it >

By: Dark Lord of the (QA) Sith

Dark Lord of the (QA) Sith — Thu, 24 Jul 2008 02:09:23 +0000

By the rules of the game, real QA folks would automatically be in God Mode, unless they were moonlighting as devs. Makes sense, really.

By: David

David — Fri, 11 Jan 2008 13:19:52 +0000

Awesome. How about a couple of days of Quad Damage for finding a bug that is a security vulnerability? The Quad Damage is of course transferrable to someone who inflicts enough damage before it runs out.

By: Jeff Lindsay

Jeff Lindsay — Thu, 10 Jan 2008 22:22:17 +0000

I’m totally making this a Trac plugin for DevjaVu…

By: yk

yk — Thu, 10 Jan 2008 21:12:14 +0000

I’m going to hang around the repository and check-in [make sweet love].

By: Rational Tester

Rational Tester — Thu, 10 Jan 2008 19:02:49 +0000

Love it – great way to making testing fun. Blogged about it at http://rationaltester.wordpress.com/2008/01/10/making-testing-fun-qa-deathmatch/ .

By: Jon H

Jon H — Thu, 10 Jan 2008 18:18:22 +0000

This is well-intended, but will simply never give the results that a couple of dedicated QA personnel can achieve. If you care about the quality of your software enough to pull some or all of your developers off of development tasks (since that IS what you hired them to do, right?) to test, just hire a couple of testers to develop manual and perhaps automated tests. If you want developers involved, tell them that their features will not be included in the next release, unless they include a comprehensive set of Unit Tests to be run at build time. But leave the testing, to testers.

QA Manager

By: Anonymous Tester

Anonymous Tester — Thu, 10 Jan 2008 17:38:57 +0000

Us testers do this regularly – although the managers frown on it (they don’t want to reward people on the somewhat arbitrary basis of who found more bugs).

I’m currently writing a book (signed deal with O’Reilly) on basic test design for developers. I’m constantly amazed how little developers know about testing. Try reading up a little bit on testing, if you’re looking for higher scores (try “Systematic Software Testing” or “A Practitioners Guide to Software Test Design”).

By: Mike

Mike — Thu, 10 Jan 2008 17:10:04 +0000

Now if someone could just integrate this with trac.

By: John K

John K — Thu, 10 Jan 2008 16:27:26 +0000

This is really very funny, especially because we started actually developing a FPS game at my job (on the side of course).

The idea is that when a developer wants to mark a bug as resolved, he or she would go into the game which creates monsters by pulling a list of bugs assigned to the player out of the bug tracking database.

The player then kills the monster and the game automatically resolves the bug in the bug tracking database.

Should be a lot of fun when we get it working!

By: Bartleby

Bartleby — Thu, 10 Jan 2008 13:55:14 +0000

I like the approach.
You would need some fairly objective standards to determine severity levels and assigning responsibility, or there would be even more finger-pointing than usual. But – on second thought – that may be an additional benefit.

By: H

Wed, 09 Jan 2008 18:57:33 +0000

So what qualifies as a head shot? A bug that you find that pretty much destroys the release candidate?

By: HS2

HS2 — Wed, 09 Jan 2008 15:45:43 +0000

Really cool approach – HS2