Topcoder Challenge Engine UI - May 7 Bug Hunt

Welcome to the Topcoder Challenge Engine UI May 7 Bug Hunt. This is a challenge of the new Topcoder Challenge Engine UI, which will be used by copilots and Topcoder staff to launch and manage challenges on the platform.

This challenge will have 24hrs for bug hunting.

Important: We have updated the rules on placement points. Please go through updated rules and scoring details mentioned below and also ask in forum discussion if you need any clarifications.

Note: The challenge prizes are mentioned for top 5 placement prizes. For other submitters, there are additional prize money to be awarded per valid bugs or issues or suggestions created in the system and approved by client after review - please refer issue weight and scoring section.

Challenge Objectives

• Exploratory or unstructured testing and reporting.
• Complete as many as you can in 24 hours.
• Windows 7,10 and macOS 13+ are in scope, targeting IE, FF, Chrome, and Safari
• Mobile is not in scope for this challenge
• Typos / Spelling / Grammatical / Content errors are NOT in scope, and any bugs logged will be rejected
• Any design errors that aren't functional, meaning something that doesn't "look" right are not in scope.  We want to target the functionality of the app, not how it looks.

 

How to Participate

• Login with one of the test accounts in the forum
• Browse the app and go through the challenge launching process
• Most functionality should be self-explanatory, but if something isn't obvious, or you aren't sure how something should work, please ask in the forum

Penalty on Duplicate Bug Reporting: If you log/report any duplicate bug, then you will receive penalty 5 Points per duplicate bug regardless of Bug type.
Penalty on Rejected Bug Reporting: If you log/report any bug without required information (insufficient info on bugs or missing repro steps or missing screenshot or missing video, etc.), then you will receive penalty 5 Points per rejected bug regardless of Bug type.

Additional Rules:

• Follow the standard Topcoder Bug Hunt Rules (if any conflict please ask in forum)
• If you do not properly document your bug reports, they will likely be rejected due to lack of information or documentation. If you submit the same bug in multiple areas/pages, (for instance, Same validation issue of a form can be found in different pages/sections) you will likely get credit for the original bug report only. The others will all be closed as duplicates.
• If you duplicate an issue on a different platform that hasn’t been tested yet, you should create a new issue and add a link/reference in the issue comments section about the Original issue number. Our copilot will review these items and consolidate them later. Please don’t make adjustments or change labels of existing issues logged by other competitors.
• DON'T RE-OPEN the issues closed by reviewer and anyone who RE-OPENS a ticket will be disqualified from the challenge.
• DON'T EDIT OR ATTACH FILES to the issues once it has been submitted and anyone who is doing this will be disqualified from the challenge.
• You must not edit the bug report once created, so make sure you enter all the details at the time you create the issue, otherwise, your issue will be moved to the end of the queue. If you really need to edit an issue you must use the comments section for this (i.e. add a comment to describe any changes you want to make to the issue), and we'll decide whether the changes are major enough to move the issue to the end of the queue.
• You must specify the test data you have used in the 'Reproduction Steps', All the issues will be marked as 'Incomplete', if the correct test data is not provided.
• There will be no appeals phase. The decision of PM/Copilot for validity and severity of each filed issue will be final.

Labeling

All reported bugs for this bug hunt MUST be labeled with the "May 7 Bug Hunt" label.  Any bugs that aren't labeled properly will be ignored.

You MUST also attach a category label to each logged bug:

• Functional
• Security
• User Interface
• Suggestions

Issue Weight and Scoring:

• Scoring will be based on the number of bugs by weight. Be sure to correctly attach a weight to your bug.  Labels are are included
• The review team has the right to change a issue category, priority and severity at their discretion.
• Only verified issues by reviewer and accepted by client will be counted. All duplicate & rejected issues will be closed with penalty and not counted.
• Log issues according to the guidelines above. Issues that do not follow these guidelines may reject due to lack of information.
• For challenge scoring, the user with the most verified issues/points will be selected as the winner. If two users submit the same issue, the user that submitted the issue first will receive credit.
• For any suggestions or improvements, please create separate issues.
• The following points will be awarded as per issue category:
  • Security Issues: 15 Points
  • Functional Issues: 10 Points
  • User Interface Issues: 5 Points
  • Suggestions: 1 Point
• The placement points will be calculated after receiving client feedback with accepted bugs only. The client rejected bugs like Duplicate bugs will receive 5 Points penalty per bug where as by design, no repro, not a bug, on hold bugs will receive no penalty.
• The 1st and 2nd place submissions must raise at least 7 client accepted bugs and at least total client accepted bugs worth 80 points.
• The 3rd, 4th and 5th place submissions must raise at least 7 client accepted bugs and at least total client accepted bugs worth 60 points.
• In case no participants qualify for the placement prizes as per above rule, then one winner will be selected who have scored highest points after reviewers accepted bugs having at least 7 accepted bugs.
• For challenge scoring, the user with the maximum points will be selected as the winner. Submitters that do not take 1st, 2nd, 3rd, 4th or 5th place will be Paid $1 Per Earned Point for each client accepted bugs up to a maximum of the 5th place prize. If two users submit the same points, then user that submitted the client accepted bug first will receive credit.
• Duplicate/Rejected Bugs Reporting: If you log/report any duplicate bug during review phase and after client review feedback, then you will receive penalty 5 Points per duplicate bug regardless of Bug type. If you log/report any bug without required information (insufficient info on bugs or missing repro steps or missing screenshot or missing video, etc.), then you will receive penalty 5 Points per rejected bug regardless of Bug type.

Final Submission Guidelines

Create and submit all your bugs with following details directly to the Github project (link provided in the forums).

• Bug report
• Videos for bug reproduction steps
• Screenshot of bug with highlighting the issue
• Any relevant JS Console logs
• Details of your OS and browser

When you are done with your submissions please submit a .txt file using the "Submit" button before the submission phase ends. In this file include following details:

•     TopCoder Handle: <>
•     Github Username: <>

Important Notes:

• DON'T use any other link to create new issues or submit as document, they won't count and won't be paid.
• DON'T use youtube or public shared location for uploading your videos and screenshots.

 

Final Submission Guidelines

Please see above