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

Welcome to Test for Success Challenge Series - QA Challenge 10 (Bug Hunt). This is a weekly challenge of Test for Success Challenge Series to execute tests for MS Teams - Shift(int) and Staffhub applications. 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. Both of these applications are employee scheduling apps. The Shift(int) app is part of a larger suite of employee management apps, while StaffHub is a stand-alone app. These apps are available as iOS, Android, web, and Windows apps.

Note: The challenge prizes are mentioned for top 5 placement prizes. For other submitters, there are additional prize money to be awarded per valid bugs or issues or suggestions created in the system and approved by client after review - please refer issue weight and scoring section.

Challenge Objectives

• Exploratory or unstructured testing and reporting.
• Complete as many as you can in 24 hours.
• iOS App, Android App, Web App, and Desktop site (see ‘Devices In Scope’ below).

How to Participate

• In scope: Shifts(int) and StaffHub applications. Please download and test either one or both of the applications.
• Use self-service link provided in forum to add yourself to the Test For Success GitLab group.
• The required GitLab repo urls are provided in forum which will be accessible after challenge registartion.
• App builds for this week is available in the forums when we open the submission phase. Specific instructions for how to install are available in the forum.
• The project repo contains reference documents to help you participate - please read these carefully before participating.
• Submit your bug report with complete details as mentioned on the reference documents.
• Upload your bug videos, bug screenshots and log files to the shared folder provided on the reference documents.

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 - Safari(Mac Only), Edge, IE11, Chrome.
  • You are allowed to test on latest mobile browsers, like Chrome for Android and Safari of iOS mobiles.

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/co-pilot 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 review team has the right to change a issue category, priority and severity at their discretion.
• Only verified issues by reviewer and accepted by client will 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 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.
• Please focus on exploratory testing and log issues
• For any suggestions or improvements, please create separate issues.
• The following points will be awarded as per issue category:
  • Functional Issues: 10 Points
  • Security Issues: 10 Points
  • User Interface Issues: 5 Points
  • Usability/UX/Suggestion/Improvements: 2 Points
  • Content Issues: 1 Point
• The 1st and 2nd place submissions must raise at least bugs worth 150 points (75 points on Staffhub and 75 points on Shift-Int). Out of the 75 points, 30 points should be from Android devices, 30 points should be from iOS devices & 15 points from web/desktop
• The 3rd, 4th and 5th place submissions must raise at least bugs worth 100 points (50 points on Staffhub and 50 points on Shift-Int). Out of the 50 points, 20 points should be from Android devices, 20 points should be from iOS devices & 10 points from web/desktop
• For challenge scoring, the user with the most verified issues will be selected as the winner. Submitters that do not take 1st, 2nd, 3rd, 4th or 5th place will be Paid $2 Per Earned Point for each non-duplicate and verified issue up to a maximum of the 5th place prize. If two users submit the same issue, the user that submitted the issue first will receive credit.

Final Submission Guidelines

Submit all your bugs with following details directly to GitLab.

• Bug report and format (refer GitLab issue format)
• Videos for bug reproduction steps
• Screenshot of bug
• App log files of bug
• Screenshot of your device information

When you are done with your submissions please submit a .txt file using the "Submit" button before the submission phase ends. In this file include following details:

• TopCoder Handle: <>
• Gitlab ID: <>

You could refer below instructions how to get your info:

• TopCoder handle (The one displayed in the top right corner near the Profile picture)
• GitLab handle (Login to GitLab and click on the Profile picture > Your Profile. Check the URL https://gitlab.com/[Your Username] )

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.