Claims Live Chat UI Bug Hunt

Challenge Objectives 

Welcome to yet another Bug Hunt(Exploratory testing) challenge for a Chatbot functionality of a website. All you need is to explore the Chatbot functionality & Usability  and report the discrepancy in the Jira. The format for reporting the bugs are given below, please go through submission section. 

This challenge will open for 24 hrs registration period and then  for bug hunting and submission. 

 ABOUT THE APPLICATION
Our Client has an operational Chatbot available to customers for commonly asked Claims Customer Service inquiries.  However, they have added a new feature in the chatbot to provide Live Agent Customer Service Chat support inorder to  facilitate their customers to get the prompt service through the Live Agent. Typically, a customer will start with inquiries through the Chatbot, and then contact a Live Agent if needed, or call the Care Center directly through the phone numbers provided.

Assets

Application Testing URL and Testing Use Case Summary  : Will post on forum once registration period is over.

WHAT TO TEST

The client is looking  for General Observation, Design improvement, and  System failure/defect (here we can say UX/Usability, UI  and functional issue respectively). So we request all the testers to focus considering  Ease of Use from the End User perspective.

Note: All the inquiries and responses typed into the Chatbot and Live Chat sessions are logged and will be reviewed by the client’s team.

Scope of Testing: 

•   Webclaims CHATBOT UI Functionality - Open Chatbot UI through the Need Help Icon.

•   Webclaims LIVE CHAT UI Functionality – Click on Live chat from the main menu of chatbot.

Out Of Scope : 

• Areas other than chatbot are out of scope. 

 OTHER DETAILS

Browsers: Latest stable versions of Chrome, IE11, Edge, Firefox and Safari

Device:  Desktop/Laptop/Ipad/Ipad pro/Tablet/Mobile Phone

Operating System: Windows 10, macOS, IOS, Android(KitKat and above) and Chrome OS ( Chrome books with the latest stable version)

Note: iOS Device and OS scope

• iPad , iPad mini ,  iPad pro in scope.

• iPhone 7 and above are in scope.

  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.

• Scoring is directly proportional to weight:  Weight 1 = 1 point, Weight 10 = 10 points.

• The participant with the highest score will win the 1st place - $400 the member who gets the 2nd most points will win $200.

• Only verified issues will be counted. Tickets created for enhancements/Suggestions will be counted as  Design improvement if it is valid. Duplicate issues will be closed and not counted. Log issues according to the guidelines provided on submission section. Issues that do not follow these guidelines may be rejected due to lack of information.

• For challenge scoring, the user with the most verified issues will be selected as the winner. Submitters that do not take 1st and 2nd will be paid $5 for each non-duplicate and verified issue up to a maximum of the 2nd place prize. If two users submit the same issue, the user that submitted the issue first will receive credit.

ISSUE WEIGHTS

• General Observation (UX/Usability Suggestions Issues) - 5 Points

• Design improvement (User Interface Issues) - 5 Points

• System failure/defect (Functionality Issues) - 10 Points

HOW TO PARTICIPATE

• Please request access to Jira in the forums if you have not yet registered in our Jira Platform.  

 Let us know if you have any questions in the challenge forum!

                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.

• 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.

• DON'T create the same issue on different platforms; instead, merge them into one; All the 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 Submission Guidelines

For each report of bug, we need the following information:

• Issue Title : 

• Device: The type of device used.  

• Operating System: OS being used.

• Browser:  Latest stable Chrome, IE11, Edge, Firefox and Safari

• Steps to reproduce : including any additional information (Must list all the steps, screen shots,  that need to reproduce the bug.)

• Actual result: What actually happened 

• Expected results: What should happen (we expect suggestions and it’s benefits when bug type is UX)

• Bug Priority : High/Low/Medium

• Bug Type : General Observation(UX)/Design improvement(UI)/System failure(Functional)

• Testing collateral:  Screenshots of Device Info, Browser Details and issue details  ( will provide gdrive link on forums to put these file)

 When you are done with your reporting, please submit a .txt file in Direct using the "Submit" button before the submission phase ends. In this file please include the following details:

                       TopCoder Handle: <>

                       Jira Username: <>