Attendee Admin - Web App Bug Hunt

All details related to this bug hunt challenge will be made available on Mar 13th 6:00 AM EST.  The bug hunt will be run for 48 hours.

 

Please register now if you are interested.

 

Welcome to the Event Admin Web - Bug Hunt!

 

We’re building a modern and intuitive event management application that will be used from event admins.

 

The application is a web application written in ReactJS. We’re providing the source code on Gitlab.

 

We’ve run the following challenge for this application till now. You can go through its spec to familiarise yourself.

 

Attendee Admin - Web App UI Prototype

Attendee Admin - Web App UI Prototype Part 2

SCOPE & BACKGROUND INFORMATION

Details are provided in forums including information on how to access Gitlab repos.

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 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 reproduce the issue. 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 gitlab repo that is causing the problem.

4. Assign it a priority level you think fits:

   1. P1 - Blocker - This bug prevents anyone from using the app. No work around exists. E.g. app crashes, app freezes etc.

   2. P2 - Critical - This bug prevents some users from using the app for some features/ on some browsers. No work around exists.

   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. P4 - Minor - This is an annoyance, but won’t prevent the target market from using the app

 

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 - weighted average - 10/8/5) 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 filled 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/ Major - $6

Minor/ Duplicating existing issue on new platform, browser or browser mode combination/ Cosmetic/ Trivial- $2

The additional prizes will be up to $250 for 2nd position, $200 for 3rd position, $175 for 4th position and $150 for 5th position.

We will award $6 for each unique Blocker/ Critical bugs. Same bug/ issue on different platform/ browser will not qualify under this.

Other than Blocker/ Critical, No prizes will be awarded beyond the 5th 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 Mar 13th 6:00 AM EST). Please submit a text file contains your Gitlab handle. This is needed so we can process the payment if you win.