Test for Success Challenge Series - QA Challenge 139 (Bug Hunt)

Welcome to Test for Success Challenge Series - QA Challenge 139 (Bug Hunt). This is a weekly challenge of Test for Success Challenge Series to execute tests for MS Teams - Shift(int) application. There is no coding or designing needed in these challenges. All you need in order to participate is to have the correct device and have good attention to detail. The Shift(int) app is part of a larger suite of Employee Management App. This app is available as iOS, Android, Web and Windows app.

This challenge will have 24hrs for the registration (during this phase no one will see details) and 24hrs for bug hunting. Details will be posted on Jul 24, 00:30 EDT.

Note: The challenge prizes are mentioned for top 3 placement prizes and extra $50 prize. For other submitters, the extra prize money will be awarded to valid bugs after client review feedback - please refer issue weight and scoring section.

Challenge Objectives

• Exploratory or unstructured testing and reporting.
• Complete as many as you can in 24 hours.
• First 6 hours - Only Bug Reporting allowed.
• Last 18 hours - Bug Reporting and Bug Challenge allowed.
• iOS App, Android App, Web App, and Desktop site (see ‘Devices In Scope’ below).

How to Participate

• Scope: Shifts(int) application is in scope. Please download and test the application.
• Jira: Please request access to Jira in the forums if you have not received an email invite.
• App Builds: Available in the forums when we open the submission phase. Specific instructions for how to install are available in the reference document.
• Jira Project: Please refer Jira project name and url shared in reference document (which will be accessible after Jira registration).
• Deliverables: upload bug videos, bug screenshots and log files in the provided one drive shared folder and add the links to your bugs.
• Bugs: Create new bug issues when you find any bugs during your execution.
• GitLab Repo Document: Before executing your first test case, please read the shared document carefully. The links to document is provided in the forum.

Devices In Scope

The following devices are in scope, anything outside this set will not be considered. Fill the form to track the device used for testing and any bugs or blockers that were found. Here are the following devices that are in scope for this week’s testing. The OS version mentioned is the minimum version required on that particular device.

• iOS:
  • iPhone 7 (10.3.2)
  • iPhone 6s+ (10.3.2)
  • iPhone 5s (10.3.2)
  • iPhone 6 (10.2.1)
  • iPad Air (10.3.1)
  • iPad Air 2 (10.3.2)
  • iPad Pro 9.3 (10.3.2)
  • iPad Pro 12.9 (10.3.1)
  • iPad Mini 4 (10.2)
• Android:
  • Samsung Galaxy S3 Neo (4.4.4)
  • Samsung Galaxy S7 Edge (7.0.1)
  • LG Flex 2 (5.1.1)
  • Samsung Galaxy Tab (6.0.1)
  • Sony Xperia (6)
  • Nexus 6P (7.1.1)
  • Moto G, 4th Gen (7.0.1)
  • One Plus 3T (7.0.1)
  • Huawei Honor 6x (6.0.1)
  • Nexus (7.1.1)
  • Pixel XL (7.1.2)
• Windows: Desktop App
• Web Browsers in Scope:
  • Latest stable browsers - Firefox, Edge, IE11, Chrome.
  • You are allowed to test on latest mobile browsers, like Chrome and Firefox browsers for mobiles.
• HeadSpin Devices: If you don't have in-scope devices to execute test cases, then you could use this oppertunity now. So you are allowed to use in-scope devices from HeadSpin device pool for testing.

Note: The above mobile devices are preferable for testing, but testers are allowed to use any mobile devices for testing

• iOS mobile devices: the required os version is 10.2 or above
• Android mobile devices: the required os version is 4.4.4 or above

Penalty on Duplicate Bug Reporting: If you log/report any duplicate bug, then you will receive penalty 3 Points per duplicate bug regardless of Bug type.
Penalty on Rejected Bug Reporting: If you log/report any bug without required information (insufficient info on bugs or missing repro steps or missing screenshot or missing video, etc.), then you will receive penalty 3 Points per rejected bug regardless of Bug type.

Additional Rules:

• Follow the standard Topcoder Bug Hunt Rules (if any conflict please ask in forum)
• 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 different platform that hasn’t been tested yet, you should create a new issue and add a link/reference in the issue comments section about the Original 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 closed by reviewer and anyone who RE-OPENS a ticket will be disqualified from the challenge.
• DON'T EDIT OR ATTACH FILES to the issues once it has been submitted and anyone who is doing this will be disqualified from the challenge.
• 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 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/Copilot for validity and severity of each filed issue will be final.

Issue Weight and Scoring:

• Scoring will be based on the number of bugs by weight. Be sure to correctly attach a weight to your bug.
• The management team has the right to change a issue category, priority and severity at their discretion.
• Only verified issues by challenger/reviewer and accepted by client will be counted - (valid on hold bugs are considered as accepted for final standings). All duplicate & rejected issues will be closed with penalty and not counted.
• Log issues according to the guidelines above. Issues that do not follow these guidelines may reject due to lack of information.
• For challenge scoring, the user with the most verified issues/points will be selected as the winner. If two users submit the same issue, the user that submitted the issue first will receive credit.
• For any suggestions or improvements, please create separate issues.
• The following points will be awarded as per issue category:
  • Functional Issues: 5 Points
  • Security Issues: 5 Points
  • User Interface Issues: 2 Points
  • Usability/UX/Suggestion/Improvements: 0.5 Points
  • Content Issues: 0.5 Points
• Challenge points for bug successfully reproduced:
  • Functional/Security Issues: 2 Points
  • UI/UX/Content Issues: 0.5 Points
  • Client Rejected Issues: 0 Points
• Challenge points for bug having No Repro / Not a Bug / Duplicate / Out of Scope status:
  • Reporter Loses Issue Points Value
  • Challenger Gains Issue Points Value
• The placement points will be calculated after receiving client feedback with accepted bugs only - (valid on hold bugs are considered as accepted for final standings). The client rejected bugs like Duplicate bugs will receive 3 Points penalty per bug where as by design, not a bug, no repro and any other bugs will receive no penalty.
• The 1st and 2nd place submissions must collect at least client accepted 10 points from each platform (Android, iOS, Web/Desktop) and total client accepted bugs worth 40 points.
• The 3rd place submission must collect at least client accepted 5 points from each platform (Android, iOS, Web/Desktop) and total client accepted bugs worth 25 points.
• In case, no participants qualify for the placement prizes as per above rule, then one winner will be selected who have scored highest points after reviewers accepted bugs worth 40 points.
• For challenge scoring, the user with the maximum points will be selected as the winner. Submitters that do not take 1st, 2nd or 3rd place will be distributed with extra $50 prize on each client accepted bugs/points reported first on the system (first come first serve basis) till it reaches $50 limit.
• If two users submit the same points, then user that submitted the client accepted bug first will receive credit for higher position.
• Duplicate/Rejected Bugs Reporting: If you log/report any duplicate bug during review phase and after client review feedback, then you will receive penalty 3 Points per duplicate bug regardless of Bug type. If you log/report any bug without required information (insufficient info on bugs or missing repro steps or missing screenshot or missing video, etc.), then you will receive penalty 3 Points per rejected bug regardless of Bug type.

Final Submission Guidelines

Create and submit all your bugs with following details directly to Jira project.

• Bug report as per Jira format
• Videos for bug reproduction steps
• Screenshot of bug with highlighting the issue
• App log files of bug
• Screenshot of your device information

Final Submission Notes:

• When you are done with your Jira submissions please submit a .txt file using the "Submit" button before the submission phase ends. In this file include following details:
  • TopCoder Handle: <>
  • Jira Username: <>
• You must required to submit before the submission phase end to this challenge to get paid.

Important Notes:

• DON'T use any other link to create new issues or submit as document, they won't count and won't be paid.
• DON'T use youtube or public shared location for uploading your videos and screenshots.