Challenge Overview
The Prizes indicated is reflective of the total prize pool. There is No Reliability Bonus. Please read below for more information on how prizes are awarded.
Challenge Objectives
- Structured Test (Manual Test Case Execution)
- Test the Android App, Windows Desktop App and Web App using specific devices and OS
About the Project
This is a Structured Test Case Execution Project and its a Trial Run with only 22 Test Cases.Every week there will be a Structured Test-Case-Execution Challenge with around 1000 Regression Test Cases which has to be executed on iOS, Android, Windows Desktop and Web Browsers in 24 hrs. This will be of Pay-Per-TestCaseExecution Model and the prizes range from $10 - $20 for one Test Case Execution.
Participate early to understand the App-flow and the Test Cases.
Please note that this Test Cycle has a Short Period (8 hrs).
What to Test (Scope)
Manual Test Case Execution of 22 test cases.
iOS: is Not in scope for this test cycle (but will be included for the future cycles)
Android: Only the below devices are in scope for this Test Cycle
Samsung Galaxy S3 Neo (4.4.4)Android: Only the below devices are in scope for this Test Cycle
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: IE11, Edge and Safari
Test Application Details: Windows Desktop App | Android App | Web URL [ All the Access and download information and credentials are posted on the forum]
How to Participate:
- Register and open the challenge forum to download the test cases and test case execution report template.
- Navigate to the Github repository located here: [ Details Posted on the forum]
- Assign yourself to one unassigned ticket with a prize amount associated to it. A competitor may only assign one ticket at a time. Change the label on this ticket to “Test Execution in Progress”
- Do not work on a ticket that is already claimed by another competitor.
- 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. Fill out the test case execution report with PASS/FAIL results and observations/comments. For each test case you are executing, you have to attach the screenshot of your Device info screen. Also you have to provide a recording for each and every 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 “Ready to Review”
- At this point you may assign yourself another ticket and continue testing.
Continue following these steps until all test case execution 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. 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 risk losing payment for that test case. It requires you to be thorough in testing and show clear verification steps in the video.
Final Submission Guidelines
Submit all your bugs directly to GitHub. 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:- Copies of all Test Execution Summaries which you participated in.
- topcoder handle (The one displayed in the top right corner near the Profile picture)
- GitHub handle (Login to GitHub and click on the Profile picture > Your Profile. Check the URL https://github.com/[Your Username] )
- 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.
- 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.