Revolt QA · Bug Hunt · Results

Our first Bug Hunt champions

Three practice storefronts, 20 planted defects in each, and a lot of very good bug reports. These are the hunters whose reports a developer could pick up and fix straight away.

69 reports13 hunters3 bug sets1 winning rule: quality over quantity
Wisdom
£15
The sharpest eye in the room
2
Zainab Rafiu
£20
Bug reports a developer could act on
1
Momoh Ose
£10
Every report a real bug
3

The winners

Each winner is shown with one of their own reports, exactly as they submitted it.

1st
Gold

Zainab Rafiu

The most professional bug reports of the hunt. Clear titles, numbered steps, and what happened set against what should have happened, almost every time.

£20 prize12 reports7 real bugs2 bug sets
MediumP3 – MediumGet a deal, subscription
The subscribe button under the "get deals" section in the lower part of the page is malfunctioning
Actual: after clicking Subscribe, a confirmation message popped up even though no email was provided. Expected: an error message or a prompt to enter an email.
  • The titles say what's broken and where, so you know the bug before you open it.
  • Found the empty category dropdown, the stock error that never recovers, the mis-wired Account tab, the broken product image, the "ADD to cart" casing slip and the dead Add to cart.
  • Rated severity sensibly: Low for a cosmetic slip, Critical for a checkout blocker.

To go further: keep one bug per report and drop observations that aren't defects, such as the cart icon having no text label.

2nd
Silver

Wisdom

Spotted the subtle bugs nobody else found, and kept testing to confirm them.

£15 prize20 reports~15 real bugs3 bug sets
MediumP3 – MediumCart · Promo code
Discount/Coupon Tab
The discount/coupon tab shows +£0.00 instead of -£0.00 to reflect a price reduction.
  • Read "+£0.00" as proof the promo code adds to the total instead of subtracting, and spotted it with an empty cart.
  • Noticed checkout counts every click as a new order, then filed a follow-up after more testing. That's the duplicate-order bug.
  • Caught the faint helper text, the "Invalid Date" on delivery, the 2019 copyright and the phone-number placeholder on the email field.

To go further: add steps and a location to every report, and keep Critical for bugs that truly block a customer.

3rd
Bronze

Momoh Ose

Six reports, six real bugs. Every one had steps to follow, and the severity ratings were the closest to the answer key of anyone.

£10 prize6 reports6 real bugs0 invalid
LowP4 – LowProducts
Font discrepancy
The font for the 'add to cart' button for the jollof rice spice mix is different compared to the other. The 'Add' is in uppercase.
  • Found the dead Add to cart, the broken Orders and Account navigation, the missing Jollof image, the casing slip and the wrong placeholder.
  • Rated each one to match its real impact: Critical, High, Medium and Low in the right places.

To go further: describe exactly what you see. Search did respond, but it returned the wrong products.

Honourable mentions

These were close to the podium.

Iyobosa

Nine real bugs, all accurately observed, including the sort dropdown that does nothing and the ✕ that won't close the product view. Add steps and calibrate severity and this is a podium finish.

Richard Chiwetalu

The best-structured reports in the hunt, with steps naming specific products and clear actual vs. expected results. More reports next time.

Angela Okolo

Noticed that the broken image moves with whichever product is sorted to the top. That's a sharp root-cause observation.

What makes a winning bug title

The title is the first thing a developer reads. These come from this hunt's own reports.

Hard to act on

  • Add to Cart Button
  • Filler
  • Picture
  • Webpage Failures

Ready to fix

  • Add to Cart button does not respond when clicked
  • The drop down menu directly under the search section is blank
  • The "Retry" button under the product section is not functional
  • Account button does not navigate to the account page when clicked

How the winners were chosen

Every report was checked against the answer key for the bug set that was live when it was submitted.

Is it real?

The report has to match a planted defect. Reports of things that aren't bugs count against you.

Can a developer reproduce it?

A clear title, steps, a location, and what happened vs. what should have happened.

Is the severity right?

A cosmetic slip marked Critical loses points. A checkout blocker marked Medium does too.

Did it take insight?

Spotting a subtle bug, or the cause behind a symptom, beats repeating the obvious ones.

A bug reported several times counts once. Splitting one bug across several reports, or packing many bugs into a single report, scores lower than one clear report per bug.