Challenge Overview
Project Overview
Stone provides business to business service. As parts of its products, Stones has provided the Otis elevator company a web-based platform for Otis's customers to monitor the performance and health of their equipments. The current web application has already been applied along with functions like monitoring equipment, service interaction, reporting, email notification etc. Now the client wants to be the first company in the elevator industry to offer transparent service to its customers on a mobile application. Therefore they are looking to create a new mobile application that allows users to monitor and track the performance of their equipment.
The client wants to provide responsive maintenance and repair services to its customers. Usually it will sign contracts with its customers. A contract will contain several buildings in which there will be several equipment called units. The client will conduct unplanned visits to customers' sites upon request regarding the problems of units. Also maintenance visits will be done by the mechanics regularly. All these operations will be planned and logged on the web application.
Currently, there was no mobile application that allowed Stones' customers to view and monitor the performance of their equipment. They have to access the web application with PCs for such information periodically. All these issues give rise to the opportunity to have a native mobile application which allows the user to perform operations remotely and quickly.
Contest Scope
In the previous contests - POC Assembly - Stone Cross-Platform Mobile App and Module Assembly - Stone Cross-Platform Mobile App Part 1 - iOS, we have implemented the a set of screens by interacting with the backend web services.
- Login Screen
- Forget Password Screen
- Change Password Screen (To reduce masstive login issue, the real call will be disabled)
- View Open Calls Screen
- View Open Call Details Screen
- View Completed Activities Screen
- View Completed Activity (Service Call, Repair and Maintenance) Detail () Screen
- Contact Info Screen
- Performance Dashboard Screen
- View Unit/Total Events Screen
- View Service Call Details/View Repair Details/View Maintenance Details Screen
- Log Service Call Screen
The goal of this competition is to clearly identify the bugs in the developed iPhone app, based on the Specification.
Testing Account
You can use this common account for testing: TestUser328@test.com1/otis123
Format
For each report of a limitation or bug, we need the following information:
1) Steps to reproduce, including any needed information
2) Screenshots (if applicable)
3) Expected results after the bug is fixed
4) Current results, before the bug is fixed
5) iOS version (5.0, 5.1, 6.0)
6) iPhone 4, 4s, 5
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.
Issues should be created in https://apps.topcoder.com/bugs/browse/STONESGENBH, You must select Mobile App Part 1 - iOS component, in order to be a valid ticket to be reviewed.
NOTE Testing on a device is recommended as you will likely see many more issues than in the simulator.
Final Submission Guidelines
You MUST submit a file with a list of your reported bugs into OR during the submission phase, for review purposes. If you do not do this, you will not get credit for any logged bugs!
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
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.