Challenge Overview
The first place prize indicated is reflective of the total prize pool. Please read the rule for more information on how prizes are awarded.
Challenge Objectives
- Structured Test (Test case execution)
- Test the iOS , Android App using specific devices and OS
About the Application
In 2017, ATCO Electric (AE) had developed the Site Finder mobile application (app) using Android Studio and Xcode. The Site Finder mobile app improves navigation to ATCO’s substations and remote offices. It assists in providing quick access to site information (including site procedures, local weather conditions, and emergency information). The mobile app also streamlines traditional paper processes, being the Journey Management and Driving Tailboard.
AE has enhanced the Sitefinder App to include the below features:
What to Test (Scope)
Each test execution on 2 iPhones (iPhone SE and iPhone 6s) running iOS11 + android device (Samsung A5) running version 7 and 8 .
Perform Functional testing of the Site Finder mobile app (v2) on the below devices. For this test cycle below devices are only in scope. Testing on other devices are out of scope.
- iPhone SE (v11)
- iPhone 6s (v11)
- Samsung A5 (version 7 and version 8)
- Test Application URLs: iOS App | Android App [ All the Access and download information and credentials are posted on the forum]
- Accepted types of bugs: Functional
- Primary target device(s): Mobiles
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: https://github.com/topcoderinc/Site-Finder/issues [If you don't have access to the project, use the ragnar link to get access. 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 time. Change the label on this ticket to “Assigned”
- Do not work on a ticket already claimed by another competitor.
- Execute the test cases associated with your ticket. You have up to 24 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 as you with PASS/FAIL results. For the 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 you identify any issues of medium or higher severity log them in the repository with the Issue label. 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 attached 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, at which point the challenge ends. Check below sample tickets to get an idea. https://www.screencast.com/t/lX1iejLvdzif
Tickets: https://github.com/topcoderinc/Site-Finder/issues/26
Test case Ticket: https://github.com/topcoderinc/Site-Finder/issues/25
Additional Rules and Payment Details
- A single participant cannot execute the same test cases multiple times. (EX: You cannot execute test cases 1-10 and then claim another ticket for 1-10 and execute again)
- 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 set of test cases and miss an issue that is found by another competitor executing those test cases you risk losing payment for that set. It pays to be thorough.
- Only report issues which prevent you from reaching the expected outcome in a test case - there are no prizes for finding bugs outside the scopes of the test cases.
How to Create New Bug Report
1. Create an account on GitHub/GitLab (if you do not already have one): https://github.com | https://gitlab.com.
2. You can get access to the GitHub/GitLab repo using ‘Ragnar’ tool specified in the challenge forum thread to create new bugs OR If you are still getting 404 error, request access to the repo using correct forum thread.
3. There is an issue template whenever you click New Issue in GitHub/GitLab. Please use these template to report your issues.
4. Issues/Bugs found in this application/App must create here: (URL for creating Bugs) https://github.com/topcoderinc/Site-Finder/issues. DON'T use any other link to create new issues OR submit a document, they won't be counted and won't be paid.
5. Please label issues with the appropriate failed test case number. If you can't find the number already please create a label and assign it to the bug report. The labels can be viewed here: https://github.com/topcoderinc/Site-Finder/labels
Issue Reporting Guidelines
For each report of a limitation or bug, we need the following information:
- Steps to reproduce, including any needed information (Must list all the steps that need to reproduce the bug, DON'T list only the URL without test data)
- Current results before the bug is fixed
- Expected results, after the bug, is fixed
- If it is a UI bug attach a Screenshots (Mark the area where the bug is) | Functional Bug - Videos (You can attach videos directly on GitLab, if not use services like www.screencast.com Don’t use www.youtube.com to host the videos) | Crash - Console/Crash Logs. | Performance testing - Support documents
- Attach the high-level labels. If you are selecting multiple labels (Platform/Device); You have to provide screenshots for each and every Device/Platform you have selected; If not Bug will be REJECTED. [Eg: If you select labels Device: iPhone, Device: Android you have to provide screenshots of all the device types you have selected]. Same applies to Platform.
- Attach detailed platform, device model (iPhone, iPad, Laptop, Desktop), operating system (Window 7 64 bit, iOS 11, Android 7.0 etc.), Frequency in the issue detail. The high-level labels aren’t sufficient for issue replication and diagnosis.
Final Submission Guidelines
Submit all your bugs directly to GitHub/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:- 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/GitLab handle used to raise the issues. (Login to GitHub and click on the Profile picture > Your Profile. Check the URL https://github.com/[Your Username] | https://gitlab.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.