Welcome to the Bug Hunt for the IBM Mail app!

This project is the foundation for a complex, enterprise email, calendaring, and messaging system.  We are building a robust REST API to allow multiple frontend clients to connect to many different services, including multiple mail server backends.

In this bug hunt you will focus on the UI and functionality issues that affect rendering pages properly for the users.

You will use this deployment for testing http://castle-dev-branch.mybluemix.net/

You are provided with a user list you can use to test the app (you can find it in challenge forums)

Bug values

 

Rules to Find Bugs

We need you to hunt for the issues and report these issues to GitLab, to get access to the project go to this tool and enter your GitLab username to join the project group (you should have done this already to see this page), the issues link is https://gitlab.com/ibm-castle/api/issues you will use to report issues.

The issue you report should have the following :
1. Clear title for the issue
2. Provide a detailed description with screenshots with steps to produce as the issue description.
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:
  4.1. P1 - Blocker - This bug prevents anyone from using the app in any browser. No work around exists.
  4.2. P2 - Critical - This bug prevents some users from using the app 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. Only test areas of the application listed in the "What to Test" section below (Please note everything in the UI is implemented so 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 should be out of the scope.
4. Please look at existing reported bugs, we have ongoing bug bounty to fix existing reported bugs in Gitlab, avoid reporting same bugs that were already reported.
5. 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.
6. The member that report the highest number of issues of priority (Blocker/Critical/Major) will win the first place prize.

Supported browsers

Your submission must work on the browsers listed below:
- IE10+
- Safari latest version on Mac & Windows
- Firefox latest version on Mac & Windows (including 45.01 and 38)
- Chrome latest version on Mac & Windows

What to Test

1. Login
2. Logout
3. Inbox
4. Read Message
5. Create Message Draft
6. Composing message
7. Calendars (View and Create Invite)
8. Contacts (List, create contact, create group)
9. Preferences (View Preferences).

Final Submission Guidelines