Challenge Overview
Challenge Objectives
-
Unstructured Test
-
Desktop site, Mobile Site
About the Application
Our Client is in their early application development in the Health Insurance Industry. They are creating a Patient Concierge Chatbot web application that will have features to answer patient inquiries regarding - Account Balance, Payments, Payment Arrangements, Recurring Payments, Insurance, Financial Assistance, Patient Requests, etc.
Assets
All assets are attached in the forums
-
User Interface Design
-
Known issues list
What to Test (Scope)
In this challenge you have to test the complete chatbot app to make sure it works properly on desktop and mobile.
-
Login and register flows - existing accounts are available in the forums. The account registration requires the user to enter correct values for account number, zip codes, SSN and date of birth - sample values are available in the forums (registering a new account won’t work with wrong values - the user has to know the correct details of a hospital patient information).
-
Test the express payment flow - note that payment processing is implemented as a demonstration and no actual payment gets processed (payment integration will be done in the future).
-
Test the chatbot features - checking balance, making a payment, downloading payment statement, updating user profile, adding/editing insurance, filling the financial assistance form and viewing other request data. Chatbot should also detect the user intent by typing in the chat box. Supported intents are:
-
Balance Inquiry
-
Financial Assistance
-
Make a Payment
-
Other Request
-
Update Information
-
Update Insurance
-
Note that we have a list of known issues it’s attached in the forums and please don’t log new issues that are duplicate of the existing ones.
-
Test URL: SEE FORUMS
-
Accepted types of bugs: Functional, UI, UX
-
Subdomains: Pages to be tested are only that are within the main domai
-
Primary target device(s): Desktop, Mobiles and tablets
-
Browser requirements: Latest Google Chrome, Firefox, Safari and Internet Explorer (Edge) on Windows/macOS. IE11 is in scope (below versions are out of scope). Safari on Windows is out of scope.
-
Content Bugs are IN SCOPE [Spelling and Grammar, Text spacing issues inside a paragraph, Tooltips, Missing/Broken Images/Videos inside an article, Font mismatch, Broken links on details pages, FAQ, Privacy, Terms and Conditions and articles.]
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 result(s) before the bug is fixed
-
Expected result(s), 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.
-
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.
-
If it is a comparison, you must provide the URL and Screenshot/video of that location.
IMPORTANT NOTE:
Missing or Incorrect details to ANY of the above fields will mark the bug report as INCOMPLETE.
Be careful when you are providing only the direct URL and not listing the steps to go to that particular page in 'Steps to reproduce' section. Sometimes the Provided URL with parameters won't load the page to the reviewer and the bug may be get closed as 'CAN'T REPRODUCE'. So better to list all the steps till the end or double check the URL is loading or not.
Issue Weights and Scoring
-
Scoring will be based on the number of bugs by weight. Be sure to correctly attach a weight to your bug. The delivery team has the right to change a severity at their discretion.
-
Only verified issues will be counted. Tickets created for enhancements or that are not bugs will not be counted. Duplicate issues will be closed and not counted. Log issues according to the guidelines above issues that do not follow these guidelines may reject due to lack of information.
-
For challenge scoring, the user with the most points will be selected as the winner. If two users submit the same issue, the user that submitted the issue first will receive credit.
-
Please focus on functionality/UI testing based on the requirements, all bug reports based on your own assumptions will be rejected.
-
Functional Issues - 10 Points
-
User Interface Issues - 3 Points
-
Usability/UX Issue - 1 Point
-
Content Bug - 1 Point
Submitters that do not take 1st, 2nd or 3rd place will be paid $5 for each non-duplicate and verified issue up to a maximum of the 3rd place prize.
Important Notice
-
Follow the standard topcoder Bug Hunt Rules.
-
If you do not properly document your bug reports, they will likely be rejected due to lack of information or documentation. If you submit the same bug in multiple areas/pages, (for instance, Same validation issue of a form can be found in different pages/sections) you will likely get credit for the original bug report only. The others will all be closed as duplicates.
-
If you duplicate an issue on a platform or browser that hasn’t been tested yet, you should create a new issue and add a link/reference in the issue description to the existing issue number. Our copilot will review these items and consolidate them later. Please don’t make adjustments or change labels of existing issues logged by other competitors.
-
DON'T RE-OPEN the issues in the review phase and anyone who RE-OPENS a ticket will be disqualified from the challenge.
-
If Mobile and Tablet testing are available DON'T create the same issue on different platforms; instead, merge them into one; All the others will be marked as Duplicate.
-
If you see multiple broken links on the same page combine them into one ticket. Others will be marked as DUPLICATE.
-
You must not edit the bug report once created, so make sure you enter all the details at the time you create the issue, otherwise, your issue will be moved to the end of the queue. If you really need to edit an issue you must use the comments section for this (i.e. add a comment to describe any changes you want to make to the issue), and we'll decide whether the changes are major enough to move the issue to the end of the queue. You are allowed to add screen shots in the comments section though, assuming your issue report contains all the details when created.
-
You must specify the test data you have used in the 'Reproduction Steps', All the issues will be marked as 'Incomplete', if the correct test data is not provided.
-
Keep an eye on the issues being submitted by other participants to minimize the time you may be spending on duplicate efforts. Knowing what has already been reported will allow you to better focus your time on finding yet undiscovered issues.
-
There will be no appeals phase. The decision of PM/Copilot for validity and severity of each filled issue will be final.
Final Deliverables
Submit all your bugs directly toGitLab. 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:
-
topcoder handle (The one displayed in the top right corner near the Profile picture)
-
GitLab handle used to raise the issues.
- 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.