[Short Cycle: 24hrs] Structured Test Case Execution - QA Challenge 2

Welcome to [Short Cycle: 24hrs] Structured Test Case Execution - QA Challenge 2. This is weekly challenge in a series of multiple challenges to execute the Test Cases for one of the product application (MS Teams - Shift(int)).

Note: The challenge prizes indicated is just the place holder which is total challenge prize amount. The prize money is per test cases basis. The prize money with each test case is tagged into gitlab issue tracker. The prize money will be paid for successful acceptance after review of test results submitted by tester. The test case wise prize money ranges from $20 - $150 prize.

Challenge Objectives

• Structured Test (Manual Test Case Execution).
• Test the iOS App, Android App, Windows Desktop App and Web App using specific Devices and OS.
• Fill out the test case execution report with PASS/FAIL/Blocked to execute test case under column Test Result and write down your comments under Obervations/Remaks/Assumptions Column of the shared template for test results reporting. The Google Forms and template files are available in the forum.
• For each test case you are executing, you have to attach the screenshot of your Device info screen.
• Submit the Test Case Google Form with the execution report (links provided in the forum) by producing video with execution steps.

Project Background

This is a Structured Test Case Execution Project for one of the product application (MS Teams - Shift(int)) and there will be series of challenges for every week to execute provided Test Cases. Every week there will be a Structured Test Case Execution challenge with around 110 Regression Test Cases which has to be executed on Android, Windows Desktop and Web Browsers within 24 hours. The payment will be of Pay-Per-TestCaseExecution Model and the prizes range from $20 - $150 for each Test Case Execution.

Technology Stack

• .NET Technology
• iOS App
• Android App
• Windows Desktop App
• Web App - (Edge, IE11, Chrome, Safari Browsers)

Test Application Details

All the access and download information and credentials are posted on the forum. Please register the challenge to access the forum.

• iOS App
• Android App
• Windows Desktop App
• Web App URL

Challenge Requirements

Manual Test Case Execution should be performed on GitLab repo. We have provided total 110 test cases (known as tickets) can be found under issues on GitLab repo. These details are available in forum, so please register the challenge to access the forum.

Fast Submission:

Please note that this Test Cycle is limited to 24 hours window for test execution results submission. It is highly recommended to participate early to understand the App flow and the Test Cases. You need to pick up one ticket at a time. Once you pick a ticket, then you need to submit Test Case Google Form report for review within 2 hours of assignment. It is recommended to submit your test execution results quickly and encouraged to work on as much as you can after completing the one that you have assigned to yourself.

Devices in Scope:

Following are the list of devices and browsers in scope of this test execution cycle. But you can let us know what device you want to use which are outside the listed devices. Initially, we are monitoring your interest and passion for the testing without limitation to the devices. But in future, the test execution will limit to the below listed devices.

• 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 - Edge, IE11, Chrome, Safari

How to Participate:

• Register into the challenge and open the challenge forum to get the instructions to download the builds and setup the devices for test execution, test cases, test case execution report Google Form and template and bug report Google Form and template.
• Navigate to the GitLab repository provided on the forum to register your GitLab ID to get access to GitLab repo.
• Assign yourself to one unassigned ticket (having label as "tcx_OpenForPickup") with a prize amount associated to it.
• Pick the ticket which shows label as "tcx_OpenForPickup". It will automatically change the label on this ticket to "tcx_Assigned" once ticket is assigned. Do not work on a ticket that is already claimed by another competitor.
• A competitor may only assign one ticket at a time. You will be unassigned if you are assigning multiple tickets and previous assigned ticket is not ready for review.
• Execute the test case associated with your ticket. You have a maximum of 2 hours to complete this task or the ticket will be unassigned from you and another competitor can claim it.
• Complete the test case execution as quick as possible, so that you can work on other unassigned tickets to maximize your chance of getting more tickets and prizes on your name.
• Prepare the Test Case Google Form report with the screenshot of your Device info screen and also provide a recording for test case execution. If the test case execution takes longer time, you can split the video. Video Name should have the step numbers covered (if you are splitting).
• If you identify any issues log them in the repository. It is important to note which test case and on which step the issue occurred. If someone already logged that issue, you can mention that ticket number, don't log duplicates.
• Upon completion of your test cases and logging of issues attach the test case execution report to the issue you assigned yourself. Update the label to "tcx_ReadyForReview".
• Once it is ready for review, then you may assign yourself another ticket and continue testing.
• If your submission is accepted, then reviewer will change your ticket label to "tcx_FixAccepted".
• If your submission has any issues or need any inputs from you, then reviewer will change your ticket label to "tcx_Feedback".
• If your ticket label is changed to "tcx_Feedback", then you will work on this ticket feedback to submit again and update the label to "tcx_ReadyForReview".

Note: Continue above steps until all test cases execution or GitLab issues have been resolved.

Additional Rules and Payment Details:

• A participant is not supposed to hold the test case for more than 2 hours of time. Else, it will be unassigned from the participant.
• You will be awarded the listed prize amount for successfully executing the test cases for that test case and accepted by reviewer. If you successfully complete multiple sets of test cases, you will be awarded a prize for each one completed.
• If you execute a test case and miss an issue that is found by the reviewer, then you are on risk losing payment for that test case. It requires you to be thorough in testing and show clear verification steps in the video.

Winning Strategy:

• Register the challenge and participate early to understand the App flow and the Test Cases.
• You need to assign yourself the unassigned/open tickets only, please don't work on tickets assigned to others.
• Prepare the videos and screenshots for the current test case execution.
• Submit the Test Case Google Form report and Bug report Google Form (if found any bug) on required template/format for review.
• Once the current assigned ticket is ready for review, then you can work on next open ticket by assigning yourself.
• For a ticket, if you receive any feedback from reviewer, then work on it and submit quickly to pass review.
• For a ticket, if it is accepted by reviewer, then you will get paid the prize amount associated with the test case title.
• You can work as many tickets you can complete within 24 hours timeline to win more prizes.

Final Submission Guidelines

Submit all your bugs directly to GitLab. 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: <>
• List of Submitted Tickets (GitLab links) and Test Case Numbers separated by comma: <[Gitlab Ticket Link],[Test Case Number]>

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:

• ALL THE SUBMISSIONS WITHOUT ABOVE INFORMATION WILL BE REJECTED AND WON'T 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.
• IMPORTANT: 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.
• DON'T use youtube or public shared location for uploading your videos and screenshots.

This month, with December’s Big Give, you’ll earn a BONUS entry into the weekly prize purse of $250 if you participate in this challenge that just went live. Check it out here and remember, everyone wins on these challenges!