Key Information

Register
Submit
The challenge is finished.

Challenge Overview

Project Overview

 

Private Exchange is an iPad app used by consultants to walk their clients through a questionnaire which collects responses for that consultant.  The application also has links to various pieces of research that the consulting firm has created.  

 

Contest Objective

 

The goal of this competition is to focus on testing the iOS app. All use cases in the provided test scenarios must be tested.

 

You should focus on testing the functions as well as usability. We do NOT want trivial issues like some icons / layouts don't look good, typos, colors, and stuff like that.  But if there’s some intuitive usability issue you find, please submit it.

 

Contest Guidelines

 

The guidelines for this contest are given below:

 

  • As issues are identified they need to be logged in GitLab.

  • 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 focus on functional testing. We don't need bug reports on typos, spelling errors and any trivial issues like this, all such issues will be rejected and will not count

  • Please also submit standard usability issues (ie: usually ipad apps allow you to interact a certain way, this one doesn’t)

  • Important Notice:  You must also be the first person to report the issue and submit it while submission phase is open.  Any bugs submitted outside of the submission duration will not be counted.

 

Technologies

 

iOS 8

iPad 2, iPad 3, iPad Air, iPad Mini

 

 

 

 


Final Submission Guidelines

For each report of a limitation or bug, we need the following information:

 

  1. Steps to reproduce, including any needed information

  2. Screen shots (if applicable)

  3. Expected results after the bug is fixed

  4. Current results, before the bug is fixed

  5. iOS Device Type and Version (ie: iPad 3)

  6. iOS Version (iOS 8.4)

 

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

 

How to Log Tickets

  1. Go to this URL: http://tc-gitlab-ragnar.herokuapp.com/#!/ragnar/joinGroup/55cc117fba02d50f0080b5e2/255725

  2. Search for and register your GitLab handle to join the project

  3. Check out the develop branch and build the project (XCode 6.4)

  4. Go to the issues url here: https://gitlab.com/private-exchange/private-exchange-calculator/issues

  5. View and Submit Issues

 

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 or second, 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 GitLab 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.

REVIEW STYLE:

Final Review:

Community Review Board

Approval:

User Sign-Off

SHARE:

ID: 30051145