What the bug hunt trains
Manual and exploratory testing is judged by the bugs you find and by how clearly you report them. This sandbox gives you a small online shop, the Acme Store, with several bugs switched on. You are not told which ones or where. You explore, compare what you see with what a sensible user would expect, and report what is wrong.
Reports are chosen from a list instead of being typed, so the hunt is scored instantly and without any AI: pick the page and the symptom. Choose carefully, because a report that matches nothing planted costs points, just as a false alarm costs a team time.
How to explore
- Walk each page with a purpose. On **Sign in**, try a wrong password, empty fields and the correct login (ada@example.com / correct-horse).
- On the **Shop**, search for words in upper and lower case, for something that does not exist, and add products while watching the cart badge.
- In the **Cart**, add the same product twice, apply the coupon SAVE10 in capitals and in lower case, then clear the cart.
- On **Profile settings**, save a name, save an empty name, and reopen the page afterwards to check that the change stuck.
- On the **Order page**, compare quantities, prices and totals, and open the invoice from the link. Check that the numbers agree between the two pages.
Scoring
- You get 100 points for every planted bug you report. There are 20 possible bugs; each hunt plants five of them, spread over several pages.
- Each false report costs 25 points. A false report is a problem that is not in this hunt, either because the app does not behave that way or because that bug is not planted right now.
- The daily hunt is the same five bugs for everyone on the same UTC date. A random hunt picks a new set.
- When you finish, you see every planted bug with the expected result, the actual result and how to see it, and a link to the Playwright challenge that automates catching it.
From finding to automating
Every bug in the hunt is also planted in the Playwright lab, where you write tests that must pass on the working app and fail on the buggy one. Finding a bug by hand and then turning it into a regression test is the workflow of most testers, so the results page links each bug to its challenge. To practise writing the report itself, use the bug report generator.
Frequently asked questions
Is this a real shop?
No. The Acme Store is a small demo app that runs entirely in your browser, with a simulated server. Nothing you type is sent anywhere.
How are my reports checked?
Each report is a page and a symptom chosen from a list. It is compared with the bugs planted in this hunt, so scoring is exact and needs no AI. The steps to reproduce are for your own practice and are not scored.
Why did a real bug count as a false report?
The app contains more possible bugs than any single hunt plants. A symptom that exists in the list but is not planted this time is not present in your copy of the app, so reporting it is a false alarm. Reproduce it yourself before reporting.
Can I reset the app?
Yes. Reset app starts the demo again with empty data and the same bugs, which is useful after you clear the cart or change the profile.
Is my score saved?
Your best score and your daily result are saved in this browser only.