Skip to main content

BUG HUNT

I have recently organized a bug hunt in my company.
The point was to motivate testers for testing outside of the scope of their work.
Here are the general settings:
________________________________________________________________________________

TERMINOLOGY

Territory – application, system
Prey – bug, issue, problem, meaningful change request
Hunt – the event in which is are the bugs searched and reported in the particular application in a given time

ROLES

Old hunter
  • He is the most experienced Hunter in the particular territory
  • Tester who has not currently the role of the Hunter
  • He informs other Hunters about the application
  • He evaluates reports
Gatherer
  • He gathers the reports from Hunters
  • He anonymizes the reports and forwards them to the Old Hunter for evaluation
  • He will maybe provide reward for the Lead Hunter
Hunter
  • His role is to catch the prey
Lead Hunter
  • He will be known at the end of the hunt
  • He is the best among hunters, the chosen one
  • He will receive a big chunk of meat or something

RULES

  • You will be given access to the territory (application, system) by the Old Hunter
  • He will provide information about
    • Basic application logic, functionality, purpose
    • What not to look for
    • What to look for
    • Who to address bug reports
    • Known prey (bugs, issues)
  • You can always ask the Old Hunter about the territory, when you are not sure
  • Your goal is to find the prey (bugs, issues, defects, problems etc.)
  • You can also suggest meaningful changes
  • When to hunt? Whenever you want. You can spend the whole week looking for a prey, or you can avoid hunting and eat grassJ
  • You will report everything to a gatherer, who will sent it anonymously to the Old Hunter for evaluation
Every prey is evaluated and given a value (0-5 meat points) by the Old hunter
  • Prey is evaluated firstly according to its size (significance, severity, priority)
  • More points are given to the Hunter who catches the prey as first
  • Points will devaluate if many Hunters catch this particular prey
  • Points are given also according to the quality of hunt report – simplicity, accuracy, clear, reproducible
  • Hunters should not share information about the prey – but this is only an recommendation
  • Duration of the hunt is restricted to a week, till enough prey is caught, or till one Lead Hunter (most points) is clear

LET THE HUNT BEGIN


________________________________________________________________________________

Comments

Post a Comment

Popular posts from this blog

When to start automation?

If you are asking this as a tester, you probably asking too late. Automation is something that can save you some portion of your work (understand resources for your client) and i rarely found cases of testing work that did not need at least some portion of automation. I know that it is rarely understood that automation is something to be developed & maintained and if you cover enough of the application, you do not need any more regression - well i do not think that somebody has done an automation regression suite that if fully reliable (i am not speaking about maintaining this code - which is another topic). There can be always a bug (or quality issue) that slips through, even when you scripts go through the afflicted part. I understand that many testers have no development background or skills, but i doubt the developers that could help you are far away. I am not assuming that they can do the scripts for you.... However if they understand what you need, they can say how e
4 comments
Read more

Testers toolkit

As every craftsman needs his tools, testers are no exceptions. I was this weekend at  SOCRATES SWITZERLAND  (SOftware CRAftsmanship and TESting) where we talked also about useful everyday tools. This list tries to be as general as possible to provide tools which can be useful to most part of everyday work, more specialised test-useful tools are very context dependent. I use most of the tools mentioned here and believe they can provide value also to you. Documenting Screenshot  - good picture is worth thousand words, this applies especially for testing, the following are some screenshotting tools and editors I used and can recommend Lightscreen  - simple tool for capturing pictures, free, cannot edit the pictures FastStone  - screen capturing tool and editor, cheap & gets the job done Snagit  - very powerful screen capturing tool and graphic editor, many functions which you never knew you can do, but wont be able to live without afterwards, a bit pricey Recording  (
1 comment
Read more

Many problems with one button

I admire the complexity which can emerge from elementary designs. Especially in the problem space. One example speaks for itself, the 'On/off app' : - an webapp consisting only from one button which can either turn 'things' on or off ( 'Picture 1 ' is an aproximate illustration of both visual states of the app) - 'things' are marketing campaigns, some more complex processes to send particular marketing messages under particular conditions to particular customers (details of such don't matter in this context) Picture 1 source: https://www.vecteezy.com/vector-art/88994-on-and-off-chrome-buttons Even when my team was highly qualified in software development, under the fog of communication  and implicit expectations that we missed, we discovered the following problems with the implementation:  Wrong template The template which we used in the test environment was not meant for production, the impact was low - only a few business
1 comment
Read more