Challenge Overview
Please register now if you are interested.
SCOPE & BACKGROUND INFORMATION
We're building an iPad that will be used by Physicians to track the order status and view order results for all the patients they have under their care. Through the order results, the application will also assist Physicians in determining which antibiotics to prescribe to patients. We ran a design challenge for this app and then another challenge to build a prototype for this app. The app currently uses mock data for various screens. You are encouraged to add/remove data to test the app for various conditions.
You'll need to have a Mac and latest XCode to be able to run the app on an iPad simulator. Scope of testing is as follows
- Any deviations (except Scan Screens) from provided design
- Any crashes/ UI issues in app based on data changes in mock data
RULES TO FIND BUGS
We need you to hunt for the issues and report these issues to Gitlab, to get access to the project, post in the challenge forums. Gitlab Repo link will be provided in forums.
The issue you report should have the following :
1. Clear title for the issue
2. Provide a detailed description with screenshots/ video with steps to produce as the issue description. Any bugs without a screenshot or video are likely to be rejected
3. If you have technical explanation, then you can provide more details with links to the code in the github repo that is causing the problem.
4. Assign it a priority level you think fits:
4.1. P1 - Blocker - This bug prevents anyone from using the app. No work around exists. E.g. app crashes, app freezes etc.
4.2. P2 - Critical - This bug prevents some users from using the app for some features/ on some browsers. No work around exists.
4.3. P3 - Major - This bug prevents some users from using the app, but they can work around the issue (ie: use a nav to get back home, submit the form with the enter key when the submit button is off screen, etc)
4.4. P4 - Minor - This is an annoyance, but won’t prevent the target market from using the app
4.5. P5 - Enhancement - Something noticed by testers that should be fixed, but isn’t considered a bug.
Please note:
1. Assigning what you think is the severity helps the admin/co-pilot. It is up to them to determine their actual severity, so it may be reassigned at their discretion before opening the bug for the bug bash.
2. If you have doubt about specific feature/button not working please post in forums for clarifications.
3. We are mainly looking for issues related to style, logic, flow, and functionality. Spelling mistakes issues are considered trivial.
4. We will not pay for duplicate bugs. We will accept the first submitted bug, based on time in GitLab. Please do not submit slight differences to try and get accepted. This will get you banned.
5. The member that report the highest number of weighted points will win the first place prize.
6. There will be no appeals phase. The decision of PM/co-pilot for validity and severity of each filed issue will be final.
ADDITIONAL PAYMENTS
In addition to the first place prize, we will be awarding the following prize money to other competitors
Blocker/ Critical - $10
Major - $8
Minor - $5
Cosmetic/ Trivial/ Enhancement - $2
The additional prizes will be up to $150 for 2nd position, $100 for 3rd position and $50 for 4th position.No prizes will be awarded beyond 4th position for any bugs
Final Submission Guidelines
You will need to report your issues in our Gitlab repo (access will be provided via forums on Sunday 8th July - 2 AM EST).Please submit a text file contains your gitlab handle to Online Review, this is needed so we can process payment if you win.