Skip to main content


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:


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


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
  • 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
  • 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


  • 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




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

Testing impact on security

... or the impact when testing is lacking? Security breaches , hacks , exploits , major ransomware attacks - their frequency seem to increase recently. These can result in financial, credibility and data loss, and increasingly the endangerment of human lives. I don't want to propose that testing will always prevent these situations. There were probably testers present (and I'm sure often also security testers) when such systems were created. I think that there was simply a general lack of risk-awareness on these projects. There are many tools and techniques from  a pure technical point of view to harden the software in security context. Some of them have automated scans which crawl through your website and might discover the low hanging fruits of security weaknesses ( ZAP , Burpsuite ...), without much technical knowledge from the person operating it. The more important aspect is however the mindset with which you approach the product. The tester is often the f

RST Explored - My experience

My experience report from my recent RST Class I attended the RST class after a while, wanting to refresh my knowledge about the RST view on testing. It was a 4-day event, each day 3 Sessions, approx 4hour/day. My general impression was that it enriched and refreshed my understanding of testing.   Each of the four days had an central theme Day 1: "It is possible to test everything?" Day2: "When to stop testing? How to test from specifications." Day3: "Product coverage outline. Complexity of the system" Day4: "Risk analysis and coverage"   Going deeper into the topics of each day would be impossible without spoilers, I will therefore rather focus on my impressions and what this training has brought me. The way Michael was guiding us through the class was very engaging, although we usually started with a short lecture, questions and remarks were encouraged from start and we had an shared review after each exercise - students explaining their work,