BiP Messenger Android App Unstructured Exploratory Bug Hunt

Hello Topcoders! Welcome to the BiP Messenger Testing Challenge. This is a Bug Hunt style competition.

If this is your first competition on Topcoder do not fear - we have all the instructions, you need to participate in this challenge specification and in the challenge forums.
Click the register button on this page to sign up, and then you’ll be granted access to the challenge forums where you can find documentation and ask questions.

IMPORTANT - This challenge has more than one prize placement! Prizes will be awarded to the top 3 scorers as follows:
1st place: $600 | 2nd place: $300 | 3rd place $200

ABOUT THE APPLICATION

BiP is a communication application that is even more beautiful than the GSM operator and used by the whole world.

You can send unlimited text, send photos and videos, and share locations with your friends. You talk to your loved ones all at once with the groups you are able to create. You have friends who do not have BiP? Do not worry! you can also sending free SMSs and MMSs.

Read the challenge specification carefully and watch the forums for any questions or feedback concerning this challenge. Let us know if you have any questions in the challenge forum!

WHAT TO TEST

Scope:

Exploratory testing of BiP application on multiple Android devices (OS version 5, 6, 7 etc..). Scope includes all the workflows. Only Functional issues, Usability issues (user interface, OS & device compatibility) and User Experience feedback (any suggestions, enhancements) are in scope.

1. Chat
2. Secret Messaging
3. Notifications
4. Audio/Video Calling
5. Games etc...
6. Also please report any issues related to 'Accessibility' specified in 'Mobile Accessibility Testing Checklist' document. Please check the forum to download the document.
7. In this Bug Hunt, your tickets should include device informations specified in the issue reporting guidelines. If not tickets will be rejected.

 

• Test Application: Download BiP Messenger Application | OR Check the forum for the link.
• Primary target device(s): Real Android devices (OS version 5, 6, 7 etc..) | Simulators
• We are accepting UX/UI suggestions for scoring. But UX/UI suggestions will not be paid.
• Content Bugs: Content, Spelling and Grammar, Spacing Issues, Tooltips, Missing/Broken Images/Videos, Font mismatch, Broken links on news articles, blog posts, products details pages, FAQ, Privacy, Terms and Conditions and articles are OUT OF SCOPE.
• Also other minor UI, Usability issues that are not affecting to the core functionality of the application are likely to be REJECTED.
• Important: Because you are testing a live Application DO NOT Test/send data via contact forms. They are out of scope. Also don't complete the 'Subscription' process because you won't get a refund.
• An edge case would be anything that does not reflect typical user behavior. They are accepted according to the impact to the end-user and based on the workarounds available.

HOW TO CREATE NEW BUG REPORTS

1. Create an account on GitHub (if you do not already have one): http://www.github.com | Tutorial
2. You can get access to the GitHub repo using ‘Self Add to repository’ tool specified in the challenge forum thread to create new bugs OR If you are getting 404 error, request access to the repo using correct forum thread.
3. There is an issue template whenever you click New Issue in GitHub. Please use this template.
4. Issues/Bugs found in this application/App must create here: (URL for creating Bugs) https://github.com/topcoderinc/turkcell-qaas/issues. DON'T use any other link to create new issues OR submit a document, they won't be counted and won't be paid.
5. Please label issues with the appropriate browser type and mode, bug type, and platform type.  The labels can be viewed here: https://github.com/topcoderinc/turkcell-qaas/labels

ISSUE REPORTING GUIDELINES

For each report of a limitation or bug, we need the following information:

1. Steps to reproduce, including any needed information (Must list all the steps that need to reproduce the bug, DON'T list only the URL without test data)
2. Current results before the bug is fixed
3. Expected results, after the bug, is fixed
4. If it is a UI bug attach a Screenshots (Mark the area where the bug is) | Functional Bug - Videos | Crash - Console/Crash Logs [Filtered ADB logs with stack trace (required for high severity defects for e.g. app crashes, app hang,) Country/ Geo]
5. Attach the high-level labels. If you are selecting multiple labels (Platform/Device); You have to provide screenshots for each and every Device/Platform you have selected; If not Bug will be REJECTED.[Eg: If you select labels Device: iPhone, Device: Android you have to provide screenshots of all the device types you have selected]. Same applies to Platform
6. Attach detailed platform, device model (iPhone, iPad, Laptop, Desktop), operating system (Window 7 64bit, iOS 11, Android 7.0 etc.), Frequency and the country in the issue detail.  The high-level labels aren’t sufficient for issue replication and diagnosis.  
7. Mention your country
8. If it is a comparison, You must provide the URL and Screenshot/video of that location.

IMPORTANT NOTE:

Missing or Incorrect details to ANY of the above fields will mark the bug report as INCOMPLETE. 

For example Incorrect Steps, Missing Screenshot/Screencast (If it is a UI issue, You have to mark it on the screenshot), Incorrect Actual and Expected results etc.

IMPORTANT NOTICE

• Follow the standard Topcoder Bug Hunt Rules
• If you do not properly document your bug reports, they will likely be rejected due to lack of information or documentation. If you submit the same bug in multiple areas/pages, (for instance, Same validation issue of a form can be found in different pages/sections) you will likely get credit for the original bug report only. The others will all be closed as duplicates.
• If you duplicate an issue on a platform or browser that hasn’t been tested yet, you should create a new issue and add a link/reference in the issue description to the existing issue number. Our copilot will review these items and consolidate them later. Please don’t make adjustments or change labels of existing issues logged by other competitors.
• DON'T RE-OPEN the issues in the review phase and anyone who RE-OPENS a ticket will be disqualified from the challenge.
• DON'T EDIT OR ATTACH FILES to the issues in the review phase and anyone who is doing this will be disqualified from the challenge.
• If Mobile and Tablet testing are available DON'T create the same issue on different platforms; instead, merge them into one; All the others will be marked as Duplicate.
• You must not edit the bug report once created, so make sure you enter all the details at the time you create the issue, otherwise, your issue will be moved to the end of the queue. If you really need to edit an issue you must use the comments section for this (i.e. add a comment to describe any changes you want to make to the issue), and we'll decide whether the changes are major enough to move the issue to the end of the queue. You are allowed to add screenshots in the comments section though, assuming your issue report contains all the details when created.
• You must specify the test data you have used in the 'Reproduction Steps', All the issues will be marked as 'Incomplete', if the correct test data is not provided.
• There will be no appeals phase. The decision of PM/co-pilot for validity and severity of each filed issue will be final.

SCORING

• Scoring will be based on the number of bugs by weight.  Be sure to correctly attach a weight to your bug.  The delivery team has the right to change a severity at their discretion.
• Scoring is directly proportional to weight:  Weight 1 = 1 point, Weight 10 = 10 points.
• The participant with the highest score will win the 1st place - $600 the member who gets the 2nd most points will win $300 and third place will win $200.
• Only verified issues will be counted.  Tickets created for enhancements or that are not bugs will not be counted. Duplicate issues will be closed and not counted. Log issues according to the guidelines above issues that do not follow these guidelines may be rejected due to lack of information.
• For challenge scoring, the user with the most verified issues will be selected as the winner. Submitters that do not take 1st, 2nd, or 3rd place will be paid $5 for each non-duplicate and verified issue up to a maximum of the 3rd place prize. If two users submit the same issue, the user that submitted the issue first will receive credit.
• Please focus on functionality/UI testing based on the requirements, all bug reports based on your own assumptions will be rejected.
• We'll decide whether a bug is valid or not based on our knowledge about the app, it's totally up to us.

ISSUE WEIGHTS

• Functional Issues - 10 Points
• Bonus Point [App hangs or crashes with device logs] - 5 Points
• User Interface Issues - 4 Points
• Accessibility Issues - 2 Points
• Usability/UX Issue - 1 Point

TIPS

Some of the tips helpful for the contest:

• Submitting what is obviously the same issue multiple times with small variations will only annoy the reviewer that has to sort through all the issues and will only count as one issue anyway. If it's less obvious if it is the same issue or not, use your best judgment and the reviewers will do the same.
• Keep an eye on the issues being submitted by other participants to minimize the time you may be spending on duplicate efforts. Knowing what has already been reported will allow you to better focus your time on finding yet undiscovered issues.
• Double check your steps to reproduce and test cases to make sure they are clear. Make sure your steps include the creation of any necessary data.

Final Submission Guidelines

Submit all your bugs directly to GitHub. When you are done with your submissions please submit a .txt file to Topcoder Online Review using the Submit to this Challenge button BEFORE the Submission phase ends. In this file include:

• Your name

• Email address

• topcoder handle (The one displayed in the top right corner near the Profile picture)

• GitHub handle used to raise the issues. (Login to GitHub and click on the Profile picture > Your Profile. Check the URL https://github.com/[Your Username]

- ALL THE SUBMISSIONS WITHOUT ABOVE INFORMATION WILL BE REJECTED AND WONT BE PAID.
- IMPORTANT: Submit the above details before the Submission Phase ends. If you can't submit due to technical difficulties within the Submission Phase please email your submission with above details to support@topcoder.com
- Participants who haven't submitted will not be paid
- DON'T use any other link to create new issues OR submit as document, they won't count and won't be paid.