Browser Bug Hunting Contest Opens Today

EddieC 0 Tallied Votes 370 Views Share

Who couldn't use some extra cash these days? Thousands of dollars in prize money is up for grabs as testers face off in , a seven-day contest that starts today. Applications in the contest's arena are Google's Chrome, Firefox 3.1 alpha 2 and IE 8. To qualify, bugs must be previously undiscovered and unreported.

Testers can submit defects for any or all of the browsers. Two prizes of US$200 each will be awarded for each of the browsers; six browser-specific prizes in all. Prizes will be awarded for the "Top Bug" for each browser in terms of defect severity, accuracy of reporting and creativity; and "Best Feedback," which is described as "the feedback provided during the usability survey" in terms of feature, analysis, etc.

Contestants also will be vying for two overall prizes. A $1000 "Top Tester" prize goes to the person who reports the most valuable bugs and feedback, and to the "Top Novice," a beginner who shows the most promise as a software tester. Judging will be conducted by the uTest team as well as a few outsiders. "Entries will be judged blindly – with no knowledge of name or background (with the exception of experience for the Novice award)," according to the . The emphasis is on "actionable learning" for each of the browsers, as opposed to feature comparisons between browsers.

The bug hunt is being organized by testing community organizer uTest, which boasts more than 11,000 testers in 144 countries doing on-demand testing for organizations in need. If you're not already a uTester, you'll need to register; it's free.

Dani AI

Generated

Thanks to for the heads-up. Note: the follow-up post in this thread contains what looks like a year typo in the correction (the thread timestamps are from November 2008), so double-check the official contest page for the exact start/end times before you plan testing. (daniweb.com) Contemporary coverage from major tech outlets also reports the event as occurring in November 2008. (pcworld.com)

If entering, prioritize reproducibility and evidence over volume. Always include exact environment details (OS and build, browser build, whether extensions/plugins were enabled, profile state), a minimal set of concrete steps that reproduce the issue, and a clear statement of expected vs. actual behavior. Capture supporting artifacts: annotated screenshots, a short screen recording of the repro, and browser telemetry (console logs, a saved HAR from the Network tab, and any crash dumps). When possible reproduce in a fresh/clean profile or in a private window to rule out extension interference.

Triage your own finds before submitting: high-impact bugs (crashes, data loss, serious security/privacy leaks, and broad functionality failures) are far more valuable than minor cosmetic glitches. For layout/rendering bugs include a tiny HTML snippet or URL and the viewport/DPI used. For intermittent failures note frequency and steps that change the outcome. For security issues follow responsible-disclosure guidelines — don’t publish exploit details publicly, and mark the report clearly so maintainers can handle it privately.

A compact report template to copy/paste:

Title: Short, descriptive summary

Environment:
- OS and version:
- Browser and build/version:
- Extensions/plugins: (on/off)
- Profile: (clean/private/profile path)

Steps to reproduce:
1.
2.
3.

Expected result:
Actual result:
Frequency: (always / sometimes / 1 in N)

Evidence:
- Screenshots:
- Video (timestamped):
- HAR file / console logs (attached):
- Crash dump (attached):

Workaround (if any):
Notes / regression (worked in older build?):
Suggested severity and rationale:

Keep titles concise, attach the smallest possible reproducible test case, and follow the contest submission rules for formatting and timing.

EddieC 0 Posting Whiz in Training

CORRECTION: The contest opens Wednesday, Nov. 5, 2009 at midnight Eastern US time (which makes it more like Tuesday night). It ends the following Wednesday, Nov. 12 at 11:59 PM ET. Good luck bug hunters!

EddieC 0 Posting Whiz in Training

Results after the first 12 hours of bug hunting:
IE: 42 bugs found, 148 testers participating
Firefox: 86 bugs, 222 testers
Chrome: 120 bugs, 192 testers

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.