Challenge Overview
This challenge has a 24hrs notification period. During this period, no one can see the Core details and no one can submit any bugs. Partial details are posted below. Please go through them. Core details will be posted during the Bug hunting phase which commences on Sep 08, 09:00 AM EDT.
Challenge Objectives
-
Perform exploratory testing on the provided Android App focussing on the Functions and UI
-
Find as many bugs as possible (without duplicating any existing issues) and log into the provided Gitlab repo
Assets
Following assets will be made available in the Challenge Forum as soon as the Bug-hunting phase is started:
- Android app access details
- Known issue list
- List of stories that have been fixed
- UI Proposal document
- Account Creation Proposal document
- List of Scenarios
What to Test (Scope)
Details will be posted in the challenge forum, once the bug-hunting phase is started
Devices in scope
Android Mobiles and Tablets with OS versions: 8, 9 and 10
Accepted types of bugs
Functional, UI, UX and Content issues
Issue Reporting Guidelines
-
For each bug report, we need the following information:
Bug Title: <Concise description of the bug>
Country chosen when signing up: <State here the country associated with your user. Leave it blank if the bug is with the Guest user>
Steps to Reproduce: <Provide detailed steps to reproduce the bug. Start to write the steps from Opening the app till where the bug occurs. Number each steps>
Actual Result: <Actual result after reproduction steps>
Expected Result: <Expected result after reproduction steps>
Screenshots or screencast: <Attach Screenshot/Video of the issue. Video is preferred for all functionals issues.>
Device and OS Information: <Ex: Xiaomi Mi A3, Android Version 9.0>
-
Attach crash log if the bug is about a crashing issue. Also attach logs which have error-details, in the case when the bug is not easily reproducible. Logs are not necessary otherwise.
-
Attach one of the following labels that is most appropriate: Functional, UI, UX or Content-issue
-
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.
-
Penalty on Duplicate Bug Reporting: If you log/report any duplicate bug, then you will receive penalty 2 Points per duplicate bug regardless of Bug type.
Issue Weights and Scoring
Scoring will be based on the number of bugs by weight. The delivery team has the right to change a severity at their discretion.
-
Only verified issues will be counted. Tickets created for enhancements or that are not bugs will not be counted.
-
For challenge scoring, the user with the most points will be selected as the winner.
Functional Issues (High) - 10 Points
Functional Issues (Medium) - 5 Points
Functional Issues (Low) - 2 points
UI Issues (High and Medium) - 5 Points
UI Issue (Low) - 2 Points
Usability/UX Issue - 2 Points
Content Bug - 1 Point
High: Bug that causes the app to fail for the specific scenario and there is no workaround.
Medium: Bug that causes the app to fail, but there’s a workaround to prevent that issue.
Low: This is an annoyance, but won’t prevent the app from running normally.
You need to find issues worth 100 points to earn the 1st and 2nd prizes, and you will receive half prize in the case if total points of the issues >= 50pts and < 100pts.
Submitters that do not take 1st or 2nd place will be paid $1 for each point they have received upto to a maximum of $150
Bug Hunt General Rules and How-Tos: Please check here
Final Submission Guidelines
-
Submit all your bugs directly to GitHub/GitLab. Then, create a .txt file with the following information:
Topcoder handle
GitLab handle used to raise the issues.
-
Zip that .txt file and submit it using the submit button present in this page
-
All the Submissions without the above information will not get paid
-
So 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 immediately