Topcoder App - New Member Search Bug Hunt Contest

Key Information

Register
Submit
The challenge is finished.

Challenge Overview

Welcome to the Topcoder App - New Member Search Bug Hunt Contest. This is a Bug Hunt challenge where we would like you to work with a section of Topcoder’s own website and report any bugs with it.

 

Contest Details

This contest is being launched 24 hours early. We want to give every participant an equal opportunity to start logging issues and we are thus notifying everyone 24 hours earlier. Please monitor this page. Exactly after 24 hours, we will share the details of the application that you need to test in the contest forums.

Additionally, this contest will also have a second place prize money of $200.

 

The application that you need to test is a simple web page. You don't have to deploy the web page. We will be sharing a URL with you.

We would like you to test the web page in the following browsers:

  1. Chrome 48+, 49+

  2. Firefox 44+, 45+

  3. Safari 9+

  4. For mobile:

    1. iOS: Chrome and Safari

    2. Android: Chrome

    3. Screen sizes as small as 320 x 480 (iPhone 4)

You need to log the issues is the Github Issue Tracker directly. We are using Github’s templates for the issue tracker.

 

Payment Structure and Scoring

  1. The participant with the highest number of valid bugs logged will be declared the winner and will earn the first place payment

  2. Participant with the second highest number of valid bugs logged in will earn the second place payment

  3. For other participants, we will pay up to $5 for each unique bug logged. The total amount paid will not exceed the second place prize money.

 

Points to Note

  1. Before you log your issue, ensure that there is no similar issue already logged in. 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.

  2. Simple issues related to spelling and grammar may not count.

  3. 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.

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

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

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

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

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

  9. We will mark the issue as accepted, rejected or duplicate.


Final Submission Guidelines

If you have submitted an issue through the provided issue tracker, kindly submit a simple README file containing your github handle in it. Your submissions will be evaluated through the Issue tracker.

 

REVIEW STYLE:

Final Review:

Community Review Board

Approval:

User Sign-Off

SHARE:

ID: 30053691