Key Information

Register
Submit
The challenge is finished.

Challenge Overview

Faith Comes By Hearing is an organization which provides the Christian Bible in audio form to people around the world in a myriad of different languages.  They have recently developed a new version of an Android application, labeled Cyber App 1.7, which is targeted to users where internet connectivity may not be consistently available, bandwidth is limited, and where mobile device memory may be constrained.   FCBH is asking the Topcoder community to help test and debug the latest release of their Cyber App.    The application and deployment instructions can be found in the forums attached to this challenge.   FCBH would like to completely test the Android Application but there are new sharing features in this version of the application that FCBH would like to be certain to validate.

You can access the sharing features from the menu feature at the top right of the main application interface as shown here:

The "Share App" menu item generates a link to second embedded APK file.  Please validate the installation of this second apk file as well.  One way to share the embedded apk file is through GMail/Email as shown below: 

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.
  • -Please do include screenshots of the reported issues.

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.

 



Final Submission Guidelines

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

 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/FCBH2016

Scoring

  • For scoring, the submitter with the most accepted bugs will win. There's no second place winner.
  • 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 half 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. 

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

  • - For each member, the final submission should be uploaded to the Online Review Tool.
  • - 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.

 

REVIEW STYLE:

Final Review:

Community Review Board

Approval:

User Sign-Off

SHARE:

ID: 30053156