Challenge Overview
Project Overview
The goal of this project is to build a mobile tool for community members to be more effective and more engaged in the Topcoder platform. Upon installing this mobile app, the user should be presented with the list of open challenges. The user can also Login/sign-up but that's not a required step to see the open challenges. Once a user attempts to register with a challenge, they will be forced into the sign-up/login flow. Optionally, the user can go to the navigation element and sign-up/login.
All submitters passing review on this developer challenge will also earn the Swift/iOS Ready Show Your Skills badge at the completion of the challenge. Ordinarily, this badge can only be earned by passing one of the peer-reviewed Show Your Skills challenges. During Swiftoberfest, certain challenges have been identified as [Swift/iOS Ready] which let you earn your badge while competing in real-world challenges, too!
Contest Objective
The goal of this competition is to clearly identify the limitations of the provided app and ensure the requirements as they were described have been met. You can find the documents describing the application in contest forum.
Things to test in the current competetion are:
- The app works properly on all supported iPhone models
- The app has no layout / UI issues on all supported iphone models
- All requirements from the document are addressed
- The app has works smoothly on all supported iPhone models
Contest Guidelines
The guidelines for this contest are given below:
- As issues are identified they need to be logged in JIRA.
- 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.
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+
- iPhone 5+
- Swift
- Xcode
- REST
Provided Resources
The following documentation will be available in the contest forum:
- Requirements document
- Source code
Contest Prize Eligibility
The submitter with the most accepted bugs will win the contest.
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
- Browser 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 here: https://apps.topcoder.com/bugs/browse/TCIOSAPP and when creating a bug you MUST select the v1 component. Bugs will not be counted if a selection is not made.
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, 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
- 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.
Submission Deliverables
You need report your issues in JIRA. Please submit a text file contains the bugs you reported to OR.
Final Submission
- For each member, the final submission should be uploaded via the challenge detail page on topcoder.com.
- You must not include any identifying information, such as your handle, in your submission. Your submission should be anonymous and you will be scored down in screening for not complying.