Test for Success Challenge Series - QA Challenge 132 (Regression Testing)

Note: We have made changes on how the test cases will be assigned to the testers, so please go through the challenge specifications carefully.
1. A group of test cases will be pre assigned to you. If you do not start working on the pre assigned group within 2 hours of the start of challenge and without any communication to copilot regarding the test cases in that group will be moved to open for pickup and anyone can assign the test cases to themselves. If you are not pre assigned to any group of test cases or if you completed the group assigned to you, please wait till the test cases are moved to open for pickup.
2. The challenge prizes displayed is just the place holder which is the total challenge prize amount. The prize money is on a per group basis. The prize money for each group of test cases is a fixed price. The prize money will be paid for successful acceptance after review of test results submitted by the tester.

Challenge Objectives

• Structured or regression testing and reporting.
• iOS App, Android App, Web App, and Desktop site (see ‘Devices In Scope’ below).

How to Participate

• Scope: Shifts(int) application is in-scope regression testing. Please download and test this application on different devices shared below.
• 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 folder and add the links to your tickets.
• 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 Jira ticket 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.7 (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 Windows OS, so you need to use the latest Windows 10 OS and it should be licensed one (Windows 7 OS is not allowed for testing).
  • 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

Additional Rules and Payment Details

• A participant has to start working on the group assigned to him within 2 hours of the start of challenge, if he failed to do so without having any communication with the copilot then the test cases in the group assigned to him will be moved to open for pickup for other testers.
• You will be awarded fixed price for the group of test cases assigned to you and if you complete additional test cases then you will be awarded a prize for each one completed.
• If you do not complete all the test cases in the group assigned to you then you will not be awarded any partial payment for the test cases completed.
• The challenge submission that was scored more points/prices from accepted tickets after review by reviewers on Jira wins and in case of tie on final points/prices, then the challenge submission that was uploaded earlier wins.

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 assign any group of test cases or any test case which is assigned to someone else.
• 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.