Challenge Overview
Project Overview
The client for this project has an existing PDF reference guide called "Your Guide to Industrial Gases and Cryogenic Fluids" that they would like to convert into a mobile application. Currently, salesman and customers use this PDF reference guide that explains measurements and calculations of industrial gases and cryogenic fluid. The client has decided to convert this reference guide into a mobile application. Converting this reference guide into a mobile application will allow salesman to discuss their products with their customers and use their "handy and useful" mobile application to search and show measurements, calculations and conversions to help explain a sale or their products. Customers could also use it as quick reference guide while at work or in the field. The client needs this mobile app to be cross-platform, and they have decided to go with PhoneGap / Cordova.
The scope of this contest is to hunt bugs in the frontend of the Data Source Mobile App application.
Contest Objective
The goal of this competition is to clearly identify any bug in the completed frontend code. The architecture documentation and UI prototype have been provided to show you how the frontend should work. You will also want to look at the forum discussions from the frontend assembly challenge for any clarifications / changes from the architecture. Please note, if any changes from the architecture were approved during the assembly challenge via forum discussion this takes precedent over the architecture documents. You may request access to the assembly challenge forums by posting to the forum for this challenge.
Contest Guidelines
The guidelines for this contest are given below:
- As issues are identified they need to be logged in JIRA: https://apps.topcoder.com/bugs/browse/DBMAPPBH
- IMPORTANT: Please follow the "Report Format" guidelines listed below for your bug to be counted!
- Issues must include clear descriptions, test cases / 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
- Windows Server 2003 machine with .NET Framework 4.5 installed
- SQL Server 2012
- IIS 7
- C# 5.0
- .NET Framework 4.5
- ASP.NET Web API 2.2
- Unity 3.5 - http://unity.codeplex.com/
- Log4net 1.2.13 - http://logging.apache.org/log4net/
Provided Resources
Documentation Provided
The following documentation will be available (attached to the challenge detail page):
1) Architecture and UI Prototype
2) Frontend Source code / deployment guide
3) Frontend Assembly Forum discussions - https://apps.topcoder.com/forums/?module=ThreadList&forumID=592966 (access will be granted manually upon registration - please feel free to request access via the forums to expediate)
Report Format:
For each report of a limitation or bug, we need the following information:
1) Steps to reproduce, including any needed information
2) Screenshots - Show screenshots of how the screen looks vs how it should look
3) Expected results after the bug is fixed
4) Current results, before the bug is fixed
5) Technology version (Windows 8, OS X 10.10, iOS 8, Android 5 etc...)
6) Browser details and version (Safari, Firefox, Chrome, etc..)
7) Any pertinent logs
Only actual bugs will be counted. Tickets logged for enhancements or issues that aren't bugs won't be counted.
When in doubt, always provide a screenshot. Screenshots are very helpful and clarify bugs. If you don't provide a screenshot, there's a good chance your bug will be rejected.
You will log your tickets here: https://apps.topcoder.com/bugs/browse/DBMAPPBH
You must select the "Frontend" component for each logged issue or it may not get counted during review.
 |
If you log a crash and don't provide a Javascript log, the bug will be rejected |
|
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. |
| |
For scoring, the submitter with the most points 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 the 1st 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. |
Additional Resources
Some of the additional resources helpful for the project are
Final Submission Guidelines
Submission Deliverables:
1) Report your issues in JIRA.
2) Submit a text file containing the bugs you reported to OR.