Challenge Overview
Project Overview
The goal of the NASA Asteroid Data Hunter project is to provide professional astronomers & citizen hobbyists with a tool that will identify asteroids in images. The Asteroid Data Hunter Tool, for input, uses images and detects asteroids using an algorithm.
The application is installed on the users workstation as a small embedded web application.
The scope of this contest is to certify the Asteroid Data Hunter tool is working without any issues in all supported platforms.
Contest Objective
The goal of this competition is to clearly identify the limitations of the provided application and ensure the application has no issues.
To test the application you will have to do the following, first you will have to deploy the application by following the Deployment Guide.
Browser Requirements
The application must be tested on:
- Windows
- IE - 9+
- FF - 32+
- Chrome - 37+
- Safari - 7+
- Linux
- Same as above, but no IE
Platforms
The application must be installed and tested on both Linux(any flavor) and Windows.
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.
- 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.
Provided Resources
VM
Two VMs will be assigned to you. Linux and Windows. Ask for a VM by sending an email to anass@copilots.topcoder.com
Contest Prize Eligibility
The submitter with the most accepted bugs will win the contest.
Final Submission Guidelines
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
- Browser version
- Platform
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/BUGHUNTDATAHUNTER and when creating a bug you MUST select the Asteroid Data Hunter JIRA component. Bugs will not be counted if a selection is not made.
Scoring
The Scoring guidelines followed for the contest are given below:
- For scoring, the submitter with the most accepted bugs will win.
- For submitters who submit but don't take first, 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 1st 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 via the challenge detail page on topcoder.com.
- 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.