Key Information

Register
Submit
The challenge is finished.

Challenge Overview

Project Overview

Welcome to the NASA - ISS FIT (International Space Station Food Intake Tracker) - iOS App Bug Hunt. This project is to test the functionality of NASA ISS FIT mobile application

Contest Overview

ISS FIT is an iOS iPad only application that will be used by astronauts onboard the International Space Station to log and track the food they eat on a daily basis. Astronauts can enter food using the app, and administrators can add food to the app using an admin tool.

The objective is simple, just test everything, make sure it works:

  • Must be able to sync data between two iPads. Meaning, log data in one, and it gets sync to the DB, and then if you log into another iPad as the same user, have the data load automatically.
    Must be able to create / edit / delete users & foods in the admin tool and have the iPad app get updated automatically.

There are no test cases or test plan for this contest. We would like you to verify all functionality find any defects. 

Device Requirements

  • iOS 7.X+, iOS 8.X+, iOS 9.x+
    iPad 3rd generation, iPad Air 2nd generation, and iPad Air 3rd generation
    Portrait orientation only.

Contest Guidelines

1. Issues must include clear descriptions and steps to reproduce and expected vs. actual results in order to be counted.
2. First competitor to find an issue gets credit, duplicates will not be counted.
3. Reviewers will accept, reject or mark the issues as duplicate.
4. Please DO take a look at the reported bugs, duplicated bugs cost your work time and the reviewer's time.
5. We'll decide whether a bug is valid or not based on our knowledge about the app, it's totally up to us
6. Please focus on functionality testing based on the requirements, all bug reports based on your own assumptions will be rejected.
7. Please focus on functionality issues, really trivial issues like typos, missing comma or period in sentences, very minor UI issues will likely get rejected
8. You must not edit the bug report once created, so make sure you enter all the details at the time you create the issue, otherwise your issue will be move to the end of the queue. If you really need to edit an issue you must use the comments section for this (i.e. add a comment to describe any changes you want to make to the issue), and we'll decide whether the changes are major enough to move the issue to the end of the queue. You are allowed to add screenshots in the comments section though, assuming your issue report contains all the details when created.

Installation, Setup & Known Issues

Get IPA file download link from the forum.



Final Submission Guidelines

Prize, Payment Structure & Scoring

1. 1st Place - $800
2. 2nd Place - $400
3. For scoring, the submitter with the most accepted bugs will win. The 2nd submitter with the 2nd highest amount of accepted bugs will win 2nd place.
4. For submitters who submit but don't take 1st place or 2nd place, if they submit bugs that aren't covered in the 1st place or 2nd place submission, they will receive $5 for each unique bug reported up to a maximum of the 2nd place prize ($400).

Submission Guidelines

1. The first 24 hours of the contest is just a registration period, and no one can submit any bug.
2. During the registration period, you must give us your testing device UDID so that we can create a new build for you. Send your UDID to rashid@topcoder.com.
3. After end of the registration period, You can access .IPA file and JIRA link from the project forum.
4. For more details check project forum.

Important Notice:

All defects must include the following:

1. Environment (iOS version and Device model)
2. Steps to reproduce
3. Outcome vs. Expected Outcome
4. Screenshot or Video

This bug hunt follows the standard bug-hunt contest rules, the one logs the max number of valid bugs win, and you should try to merge the similar issues in one bug (e.g. input box one page1 & page2 validation error should be counted as one same bug). 

Tips

1. 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.
2. 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.
3. 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

REVIEW STYLE:

Final Review:

Community Review Board

Approval:

User Sign-Off

SHARE:

ID: 30054473