Project UBahn | Bug Hunt

This challenge will start 24hr early for the registration (during this phase, participants will NOT see the details about the hunt) and 2 days for bug hunting. Details will be posted on July 12th 2019 at 9 AM ET

 

Challenge Objectives

• Find bugs in a web based app and report them on Github

 

About the Application 

• Our client wants to create an employee management system to determine employees that are no longer working on active projects and to understand their qualifications and expertise for suitability in other projects

• The app runs on your browser. For this Bug Hunt, only Internet Explorer 11 and Google Chrome (latest) and FireFox (latest) are in scope.

 

Assets

• No assets are being shared besides a url at which you can test the web app. This url will be shared at 9 AM ET on 12 July 2020

 

What to Test (Scope)

In this challenge, you have to test a web app in either Internet Explorer 11 or Google Chrome browser (latest) or Firefox (latest).

• You need to test that the web app displays correctly in the browser

• Play around with the actions and verify that the outcome is as expected.

• You can also report any issues with the data, by inspecting the Network requests and reporting any unusual behaviour

 

Issue Weights and Scoring

• For every ticket that you create, kindly attach the label “Bug Hunt” to it. You are not expected to assign any other label.

• Scoring will be based on the number of bugs raised. Only valid bugs will count towards this.

• Typos / spelling mistakes will not count as valid bugs.

• Tickets created for enhancements or that are not bugs will not be counted. Duplicate issues will be closed and not counted. Log issues according to the guidelines above. Issues that do not follow these guidelines may be rejected 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.

• Please focus on functionality/UI testing based on the requirements, all bug reports based on your own assumptions will be rejected.

• Submitters that do not take 1st or 2nd will be paid $5 for each non-duplicate and verified issue up to a maximum of the 2nd place prize.

 

Important Notice

• Follow the standard topcoder Bug Hunt Rules. In our case, our bug submission phase is only for 48 hours (after the initial 24 hours of registration).

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

• DON'T RE-OPEN the issues in the review phase and anyone who RE-OPENS a ticket without a valid reason will be disqualified from the challenge.

• If you see multiple broken links on the same page / section combine them into one ticket. Others will be marked as DUPLICATE.

• 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 (and you might lose out if there is a duplicate issue since the earliest issue will be considered and updating an issue moves it 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 are allowed to add screen shots in the comments section though, assuming your issue report contains all the details when created.

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

• Keep an eye on the issues being submitted by other participants to minimize the time you may be spending on duplicate efforts. Knowing what has already been reported will allow you to better focus your time on finding yet undiscovered issues.

• There will be no appeals phase. The decision of PM/Copilot for validity of each filled issue will be final.

Final Submission Guidelines

Submit all your bugs directly to Github. When you are done with your submissions please submit a .txt file using the “Submit” button before the submission phase ends. In this file mention your github handle (the handle that is used to create the tickets in github). If your submission does not have this information, we may reject your submission (and still accept the bugs) but you may not get paid.

IMPORTANT - Submit the above details before the Submission Phase ends. If you can't submit due to technical difficulties within the Submission Phase please email your submission with above details to support@topcoder.com on time. Participants who haven't submitted will not be paid. DON'T use any other link to create new issues OR submit as a document, they won't count and won't be paid.