Challenge Overview
Project Overview
The client of this application is Sharous, a company that is in progress of starting a mobile-based, location-centric social networking application, also called Sharous. The objective of this project is to build a proof-of-concept and to enrich the idea that they have for Sharous.
Sharous will initially be offered as a mobile application for iOS devices, where users will be able to share their location from their phone in close to real-time, view a world map showing the location of their friends, people around them, and other users, and interact with other users in the map or on their contact list.
The application will also provide standard social networking features such as requesting to add friends, accepting or rejecting friend requests, removing friends, viewing contact (friends) list, posting status message, changing profile and avatar and chat messages.
Given to the real-time nature of the location data in the application, it will greatly help user to find and keep in touch with his/her friends. Users will also be aware of other users in the surrounding, and will be able to chat with them or see their profile, or arrange to meet them offline. This will give them opportunity to meet new people.
In addition, the system will provide functionality for administrator to manage problematic users (including deleting or blocking users) and see statistics related to the server.
This project aims to create a proof of concept that, once ready and approved, will be converted to a production ready application to be listed in Apple App Store. In the future, the client also intends to expand the application to other platform, including Android and Windows Phone
One of the challenges in this project is that there are a lot of existing social networks, including some location-based social networks that are available for mobile phone like Foursquare. The application will offer benefits that are not offered in existing networks, such as near real time nature of location update, the map-centric interface in the application.
Contest Objective
The scope of this contest is to hunt bugs for iOS platform (iOS 4+) including iPhone 3GS, iPhone 4/4s, and iPhone 5.
Things to test in the current competetion are:
- The UI is properly show in the tested device
- The functionality works properly in the tested device
Platform Requirements
The application should be tested in real devices that has iOS 4+ installed.
How To Install the App
The application will be distributed via TestFlight,
Each member will have to sign up for a test account here: http://tflig.ht/101Jgai,
Please register your testing devices properly, so our client can collect all device UID's first of all, then add them to the developer profile of Apple and approve them all at once.
We will give 24h registration phase for prepartion, all members will be granted access at the end of registration phase, then the bug hunt will be started at 05/26/2013 at 08:00 EST (UTC-05) .
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.
- Issues must include screenshots and tested device information.
- 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 4+
- Objective C
- HTML5
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
- Test device including the 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 here: https://apps.topcoder.com/bugs/browse/SHAROUS
Scoring
The Scoring guidelines followed for the contest are given below:
- For scoring, the submitter with the most accepted bugs will win. The submitter with the second most accepted bugs will receive second place.
- For submitters who submit but don't take first or second, if they submit bugs that aren't covered in the first or second place submission, they will receive $5 for each unique bug reported up to a maximum of the 2nd 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.
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 to the Online Review Tool.
- 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.
Final Submission Guidelines
N/A