myCall iOS App - Bug Hunt

All details related to this bug hunt challenge will be made available on Tuesday 14th Feb at 3 AM EST.  The bug hunt will be run for 48 hours.

 

Please register now if you are interested.

 

Welcome to the myCall iOS App - Bug Hunt!

 

We’re building a modern and intuitive iOS application that helps to support users with one-click access to meetings and teleconferences.

High-level Requirements

Development of an app that will:

• Enable the user to authorize iOS native calendar access

• Fetch calendar events

• Extract and parse the data into MyCall application

• Function without network access (only for saved/synced events)

• Determine if a meeting or event has both a dial-in and conference code, or one or the other.

• Convert the phone number to a device consumable string. Ex. Dial-in: 1-800-400-5123, Conf Code: 12345 to 18004005123,12345#. Which will allow for one-click dial-in access (where supported by teleconference providers).

 

The application is a native iOS application written in Swift. We’re providing the build in HockeyApp as well as 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.

 

myCall - Fast 72h Native iOS Challenge

SCOPE & BACKGROUND INFORMATION

Details are provided in forums including information on how to access Gitlab repo, HockeyApp build.

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 a 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 workaround 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 workaround 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

   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 - 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 - $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 14th Feb - 3 AM EST). Please submit a text file contains your Gitlab handle. This is needed so we can process the payment if you win.