Challenge Overview
Welcome to Test for Success Challenge Series - QA Challenge 57 (Regression Testing). This is a weekly challenge of Test for Success Challenge Series to execute test cases for MS Teams - Shift(int) app. 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 App. These apps are available as iOS, Android, web, and Windows apps.
This challenge will have 24hrs for the registration (during this phase no one will see details) and 26hrs for regression testing. Details will be posted on Jan 14, 21:30 EDT.
This challenge will have 24hrs for the registration (during this phase no one will see details) and 26hrs for regression testing. Details will be posted on Jan 14, 21:30 EDT.
Note: The challenge prizes displayed 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 Jira 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 $10 - $150 prize.
Challenge Objectives
- Structured or regression 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
- 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.
Additional Rules and Payment Details
- A participant is not supposed to hold the test case ticket for more than 2 Hours of time, otherwise it will be unassigned from the participant. Similarly the review feedback needs to be resolved within 2 Hours, otherwise the ticket submission will be rejected and the ticket will be opened for pickup by others. (Please prepare your submission very carefully before submiting it, the ideal case here is that your submission would be qualify for just one round of review then you don't need to worry about this 2 Hours rule)
- 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, then 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.
- For incomplete submissions or tickets/bugs having review feedback will receive penalty on ticket price. This will reduce 10%, 25%, 50% of ticket price for each failed submission and 50% is the most deduced price. So it is recommended to read the shared document carefully and submit the report with all necessary information without fail.
- The challenge submission that was scored more number of accepted tickets after review by reviewers on Jira wins and in case of tie on accepted number of tickets, then the challenge submission that was uploaded earlier wins.
Final Submission Guidelines
Your final deliverable for each ticket is as mentioned below:
- Provid required info details on each ticket when you complete the test case ticket execution on Jira
- Videos for all Test Case steps and also bug videos for the repoduction steps
- Screenshot of bug with highlighting the issue
- The app log files for each test case
- Screenshot of your device information
- TopCoder Handle: <>
- Jira Username: <>
- 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.