May 4, 2019

What is a Bug Hunt?


The primary objective of a bug hunt is to identify defects. Competitors in a bug hunt identify defects by testing applications and comparing the final product against requirements or test cases.

The output includes a list of software defects found. Bug hunts are run using a combination of the Topcoder platform and a Github or Gitlab project.

A bug hunt is not a bug bash. To find out more about a bug bash, please click here.

How long do bug hunts last?

Bug hunts run for 5 days. During the first 24 hours after a bug hunt has launched, you can only register and no submission of defects can occur. This is done so that all members, no matter what timezone they are in, can participate. After the first 24 hours transpire, a challenge manager will give access to the code or testing environme

How do I participate in a bug hunt?

  1. Register for the bug hunt contest

  2. Review the project documentation (any technical assets, requirements or test plans)

  3. Once the first 24 hours passes, check the contest forum for details on accessing the code / test environment.


Register > Review Documents / Wait 24 Hours > Deploy Code / Access Test Environment > Log Defects > Repeat

Prize Structure & Scoring

The participant with the highest number of valid bugs logged will be declared the winner and will earn the first place payment. The same rule will be applied for the 2nd and 3rd place winners.

These are examples only - actual contest prizes will vary.

  • 1st Place: $500

  • 2nd Place $400

  • 3rd Place: $300

In addition to the ranked placements, we will award $5.00 for every unique defect that was submitted and that does not earn a ranked placement above. For example, if you are not the 1st, 2nd or 3rd place submitter, but you submit a unique defect that was not submitted by anyone else - you will earn $5.00 for each unique defect. The total amount paid will not exceed the second place prize money.

Submitting a Defect

  • The first participant to find an issue gets the credit - duplicate issues will not be counted.

  • Before you log your issue, ensure that there is no similar issue already logged. You can do a quick keyword search and only when you are sure that there is no other ticket logged for the same issue, create one.

  • Issues must be clearly described. Provide a test case (perhaps an unlisted video reproducing the issue or a document with steps on how to reproduce the issue) along with the expected vs actual results in order for your issue to be counted.

  • Video / screenshots in your issue description will help tremendously.

  • If an issue is not properly documented, we may reject it and it will not count.

  • If you submit an issue that is seen in multiple screens as multiple issues, they will only count as one defect. Others will be marked as duplicate.

  • Only create issues during the submission phase. After that, any issue logged will not count.

  • We will mark an issue as accepted, rejected or duplicate either during the submission phase or after.

Please Note:

  • Assigning a severity to the defect helps the copilot. It is up to the copilot to determine the actual severity, so it may be reassigned at their discretion before opening the bug for a bug bash.

  • If you have a doubt regarding a specific feature not working please post in the contest forum for clarification.

  • We will not pay for duplicate bugs. We will accept the first submitted bug, based on the submission time stamp.

  • There is no appeals phase. The decision of copilot for validity and severity of each issue will be final.

Group 9
Group 9

Recommended for you

What is a Bug Bash?

Overview The primary objective of a bug bash is to fix a number of issues in either a subset of code, or an en...
Read More E4627031-A283-4694-8843-C0F351FBA3F8

Payment Policies and Instructions

Topcoder is partnered with several payment providers to send payments to our community members. Once setup, pa...
Read More E4627031-A283-4694-8843-C0F351FBA3F8

Development Reliability Ratings and Bonuses

Member profiles reflect reliability factors for the last 15 projects in each track. The reliability factor is ...
Read More E4627031-A283-4694-8843-C0F351FBA3F8