Challenge Overview
1. Contest Overview
IBM has recently launched Bluemix, (a cloud platform stocked with free services, runtimes, and infrastructure to help you quickly build and deploy your next Mobile or Web App) and would like feedback with one of the services called Mobile Quality Assurance (MQA). Using winning content from 2 previous topcoder contests in the IBM DevOps and Bluemix challenge series, IBM is providing two versions of a very simple yet interesting sentiment analysis App. The App lets a user enter a phrase, and find out how people are feeling about the phrase on Twitter.
In this contest, we want you test this app for User Experience (usability) and crashes. We want you to report either bugs or suggestions related to the user experience and also report all kinds of crashes.here is also a survey for feedback in the form of how-to recommendations, best practices, hints and tips, etc. (see Survey Requirement in Section 3 below).
Please note that the bug reporting for this contest is not conventional and it is a very exciting process which makes use of MQA (Mobile Quality Assurance Tool) provided as one of BlueMix Services.
2. Start Here!
- Register at BlueMix and IBM DevOps Services
- To participate in this competition, you will need an Android Device
- The basics about the BlueMix environment can be found at: BlueMix getting-started guide
- Sign up for a free trial of Mobile Quality Assurance (MQA) for Bluemix.
- You can use the same login for both DevOps services and MQA.
3. Testing and Logging Requirements
- Please ask access to the application in the forums.
- Once I receive the request, you will receive a mail with the installation link for the App.
- Open the link in Android device and click the "Install" link.
- The above step will install the App.
- Start using the App.
- Once you find an issue, just shake the screen.
- On shaking the screen you will see MQA objects (pencil, spray on left corner and eraser on right corner) that will allow you to mark the red boundary area where you see the bug.
- Create the mark to show us the bug and then add description for it (you will be prompted to add description once you complete the marking.)
- Details necessary in the description:
- Expected Output
- Actual Output
- Your topcoder handle
- Once you complete this, your bug will be reported to MQA.
- Reporting to MQA is the way of logging bugs as IBM DevOps service work items. We will not use JIRA for this contest.
- It is mandatory to upload the list of all reported bugs in OR. Your submission will not be counted if this is not followed.
Please remember: The clients are interested in your use of MQA in detecting/reporting User Experience bugs and suggestions and crashes. They are not interested in functional testing and hence such bugs will not count towards your ranking.
3. Scoring
- For scoring, the submitter with the most accepted bugs will win. The most accepted bugs will be combined number of bugs across the two versions of the App.
- For submitters who submit but don't take first placement, 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 the 1st place prize.
- Please note: If two submitters submit the same bug report, the submitter who submitted the report first will get credit for the bug. The second submitter will not.
Tips for Success:- Asking questions early in forums and getting feedback is very important for the success of this competition.
Final Submission Guidelines
NA