John Hancock - Innovation Portal Test Cases Execution (QAAS)

Challenge Overview

In this challenge, we are looking to close out testing of Innovation Portal web app by executing test cases created in a previous challenge.
 
The first place prize indicated is reflective of the total prize pool. Please read the rule for more information on how prizes are awarded.

Note: there's a 24h waiting period for this bug hunt so members from different timezones can get preparted, exactly 24h after challenge starts we'll post challenge details to the forum so you can get started on the testing.

Challenge Details

This challenge will be run differently than other Bug Hunt type challenges. Please read the instructions below and follow them closely or you risk not qualifying for payment.
In this challenge each test case will be executed three times, by three different competitors. To manage this process, we are using Github issues to track who owns which deliverables.
 
To participate:

1. Register and open the challenge forum to download the test cases and test case execution report template.
2. Navigate to the Gitlab repository with the issues listed, we'll post the link to the forum after the waiting period is over. Please try to get access to the repo by posting your gitlab username to the forum, so you can assign yourself an issue direclty using the "assign yourself" link (http://take.ms/3Pe6w), keep in mind you can only assign unassigned issues. The next option is to comment on an issue to claim an issue but that's not as effective.
3. 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”
4. Do not work on a ticket already claimed by another competitor.
5. 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.
6. 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. We have created a sample issue (#43) to demonstrate this requirement, if you still feel confused please ask in the forum.
7. 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”
8. 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.
 
Additional Rules and Payment Details

• A single participant cannot execute the same test cases multiple times. (EX: You cannot execute test cases 1-20 and then claim another ticket for 1-20 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.

Final Submission Guidelines

Please submit to Topcoder Online Review a zip file containing the following:

• A text file with your topcoder handle and your Gitlab username.
• Copies of all Test Execution Summaries which you participated in.