Challenge Overview
Welcome to the HP LPC - Women's Community Savings bug hunt challenge. This project aims at creating a e-ledger mobile application that helps to simplify record keeping by digitizing it, thereby increase accuracy and improve data security. We've run multiple challenges so far and built out a native Android prototype app, a web-based admin tool and the corresponding backend Nodejs microservices.
We now want to run a bug hunt to exhaustively test the Android app and the admin tool for any issues.
SCOPE & BACKGROUND INFORMATION
Details are provided in forums.
RULES TO FIND BUGS
We need you to hunt for the issues and report these issues to Github, to get access to the project, post in the challenge forums. Gitlab Repo link is 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. Android app crashes, Admin Tool 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 issues of priority (Blocker/Critical/Major) 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 $200 for 2nd position, $150 for 3rd position and $100 for 4th position.