Challenge Overview
Project Overview
The goal of this project is to design and build an iPad application that will allow the USA Diving team to track the performance of divers as they prepare for official diving events and Olympic trials. Closely monitoring the day-to-day well-being and performance of divers in training will allow coaches and physicians to adjust individual training programs, for improved results.
Contest Objective
The goal of this competition is to thoroughly test the iPad app and identify the bugs in the app. Please register to see all details about the app and thest all functionalities of the app.
Device Requirements
iPad running iOS 8+
Contest Guidelines
The guidelines for this contest are given below:
- As issues are identified they need to be logged in the specified git repo.
- Issues must include clear descriptions, test cases and steps to reproduce and expected vs. actual results in order to be counted.
- First competitor to find an issue gets credit, duplicates will not be counted.
- Reviewers will accept, reject or mark the issues as duplicate.
- Please DO take a look at the reported bugs, duplicated bugs cost your work time and the reviewer's time.
- The copilot will make decisions on whether a bug is valid or not.
- After you create a ticket in the git repo, you must NOT edit the ticket itself, otherwise we'll move your ticket to the end of queue. You can add comments if you want to add clarification to the ticket, but the reviewer will decide how much the comments affect the ticket and whether it needs to be moved to end of queue.
- You have 24h to register and provide your gitlab username in the forum, after 24h we don't accept new registrations and will ignore further posts of gitlab username. Then you have 24h to test the app and log tickets.
Important Notice:
You must also be the first person to report the issue and submit it while submission phase is open. JIRA will allow you to file issues before and after the submission phase, but these will NOT be counted.
Technologies
iOS 8+
iPad
Final Submission Guidelines
Bug Report Process
Bug Report Format
For each report of a limitation or bug, we need the following information:
- Steps to reproduce, including any needed information
- Screen shots (if applicable)
- Expected results after the bug is fixed
- Current results, before the bug is fixed
- Device model and iOS version
Important Notice:
If you do not properly document your bug reports, they will likely be rejected due to lack of information or documentation. Also, make sure your bug reports are reasonably general.
If you submit the same bug that is seen in multiple screens, for instance, you will likely only get credit for the original bug report. The others will all be closed as duplicates.
Ticket Logging
You will log your tickets in the specified git repo.
Scoring
The Scoring guidelines followed for the contest are given below:
- For scoring, the submitter with the most accepted bugs will win.
- For submitters who submit but don't take first or second, if they submit bugs that aren't covered in the first place submission, they will receive $5 for each unique bug reported up to a maximum of half the 1st place prize.
Important Notice:
If two submitters submit the same bug report, the submitter who submitted the report first into JIRA will get credit for the bug. The second submitter will not.
Tips
Some of the tips helpful for the contest are:
- Submitting what is obviously the same issue multiple times with small variations will only annoy the reviewer that has to sort through all the issues and will only count as one issue anyway. If it's less obvious if it is the same issue or not, use your best judgment and the reviewers will do the same.
- Put an eye on the issues being submitted by other members 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.
- Double check your steps to reproduce and test cases to make sure they are clear. Make sure your steps include creation of any necessary data.
- Focus on functionality testing, trivial issues like typos will be rejected.
Submission Deliverables
You need report your issues in the git repo. Please submit a text file containing your gitlab username so we can map your handle to your gitlab username.
Final Submission
For each member, the final submission should be uploaded via the challenge detail page on topcoder.com.