Challenge Overview
1. Project Overview
MAD App is a HTML5 Web application targeting for iOS (iPad/iPhone) and Android Platform. It is used by internal users to capture orders for mobile applications to be created.
The scope of this contest is to hunt bugs for iOS platform (iOS 4+) including iPhone 3GS, iPhone 4/4s, iPhone 5 and iPad 1+.
2. Contest Objective
The goal of this competition is to clearly identify the limitations of the provided MAD HTML5 Web application.
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
For fairness, the app url will be avaiable 3 hours after the starting of the registration phase.
2.1 Platform Requirements
The application should be tested in browsers of simulator or real devices that has iOS 4+ installed.
2.2 Users
Login to the application with any valid ibm style email address, like
- fireice@cn.ibm.com
- tester@in.ibm.com
3. 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.
4. Technologies
- HTML5
- Javascript
- Dojo
- CSS
5. Provided Resources
5.1 Documentation Provided
The following documentation will be available in the contest forum:
- MAD Prototype - You can deploy in local environment to test, but the evaluation will be based on the app deployed in VM.
6. Payment
6.1 Base Payment
TopCoder will compensate members with first and second place submissions. Initial payment for the winning member will be distributed in two installments. The first payment will be made at the close of the approval phase. The second payment will be made at the completion of the support period.
Winning Submission and Second Place payments are shown at the top of the contest page.
7. Contest Prize Eligibility
The submitter with the most accepted bugs will win the contest.
8. Competitor Restrictions
CCA is required for the current project.
9. Standard Support
Issue owner will be responsible to clarify any question about this issue when in bug fix phase.
10. Bug Report Process
10.1 Bug Report Format
For each report of a limitation or bug, we need the following information:
- Steps to reproduce, including any needed information
- Screenshots (if applicable)
- Expected results after the bug is fixed
- Current results, before the bug is fixed
- Test device including the iOS version
- Please select iOS Platform component
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.
10.2 Ticket Logging
You will log your tickets here: https://apps.topcoder.com/bugs/browse/MICAPPBH
Final Submission Guidelines
N/A