Juno - Vehicle Service Contract - iOS AR App Bug Hunt

 

Final Submission Guidelines

Issue Weights and Scoring

• For every ticket that you create, kindly attach the corresponding device label “iPhone” or “iPad” or both to it. You are not expected to assign any other label (you still need to specify iOS version in the bug description). If the same issue affects both iPads and iPhones but is logged separately, it's counted as one ticket for both devices

• Scoring will be based on the device types it affects: Both iPad & iPhone - 10pts, only iPad or only iPhone - 5pts. 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 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 place will be paid $5 for each non-duplicate and verified issue up to a maximum of $150.
     

Issue Reporting Guidelines

 

For each report of a limitation or bug, we need the following information:

1. Steps to reproduce, including any needed information (Must list all the steps that need to reproduce the bug)

2. Current result(s) before the bug is fixed

3. Expected result(s), after the bug, is fixed

4. If it is a UI bug attach a Screenshots (Mark the area where the bug is) | Functional Bug - Videos (You can attach videos directly on GitLab, if not use services like www.screencast.com Don’t use www.youtube.com to host the videos) | Crash - Console/Crash Logs. | Performance testing - Support documents

5. Attach the high-level labels. If you are selecting multiple labels (Platform/Device); You have to provide screenshots for each and every Device/Platform you have selected; If not Bug will be REJECTED. [Eg: If you select labels Device: iPhone, Device: iPad you have to provide screenshots of all the device types you have selected]. Same applies to Platform.

6. Attach detailed platform, device model (iPhone, iPad), operating system, Frequency in the issue detail.  The high-level labels aren’t sufficient for issue replication and diagnosis.  

7. If it is a comparison, you must provide the URL and Screenshot/video of that location.

IMPORTANT NOTE:

Missing or Incorrect details to ANY of the above fields will mark the bug report as INCOMPLETE. 

For example, Incorrect Steps, Missing Screenshot/Screencast (If it is a UI issue, you have to mark it on the screenshot), Incorrect Actual and Expected results etc.

 

Important Notice

• Follow the standard topcoder Bug Hunt Rules.

• 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 platform or browser that hasn’t been tested yet, you should create a new issue and add a link/reference in the issue description to the existing 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 in the review phase and anyone who RE-OPENS a ticket will be disqualified from the challenge.

• If Mobile and Tablet testing are available DON'T create the same issue on different platforms; instead, merge them into one; All the others will be marked as Duplicate.

• If you see multiple broken links on the same page 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. 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 and severity of each filled issue will be final.

 

Final Deliverables

 

Submit all your bugs directly to GitLab. 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:

• topcoder handle (The one displayed in the top right corner near the Profile picture)

• GitLab handle used to raise the issues. (https://gitlab.com/[Your Username])

 

- ALL THE SUBMISSIONS WITHOUT ABOVE INFORMATION WILL BE REJECTED AND WON’T BE 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.

- Participants who haven't submitted will not be paid.

- DON'T use any other link to create new issues OR submit as document, they won't count and won't be paid.