Dyson Exploratory Testing Series - 2

Welcome to the Dyson Exploratory Testing Series -2. It’s a Bug Hunt challenge. All you need is to explore and experience the app as an end-user and report UI/UX observations in Jira. The format for reporting the bugs are given below, please go through the submission section. 

This challenge will open for 36hrs for bug hunting and submission. Please do not report any issues in Jira after it, they will not be accepted.

ABOUT THE APPLICATION

Dyson is a British technology company who designs and manufactures household appliances such as vacuum cleaners, air purifiers, hand dryers, bladeless fans, heaters, hair dryers, and lights. For this challenge, we request you to perform an unstructured/ exploratory testing of the company’s online store (URL copied below) to identify opportunities to create improved retail customer experience.

Assets

Application Testing URL : https://www.dyson.in 

WHAT TO TEST : we request all the testers to perform exploratory testing of critical workflows (Product Search, Checkout, Delivery, etc.) of the given application to identify opportunities for creating better customer experience. Please focus on following criteria when reviewing the end user experience. 

Buyers Experience Evaluation Criteria

• Clarity - How clear was the journey from choosing to checkout?

• Speed - Was the duration of checkout comparable or better compared to other similar experiences?

• Friction - Where there hurdles for the user to find and buy what they wanted?

• Support - How well supported is the buyer through their experience?

• Simplicity - Is the purchase journey simple for the user to comprehend, use, and move through?

• Control - Does the experience empower the user with information through the experience?

• Usefulness - Does the experience help users with their goals and provide actionable information?

• Navigation - Does the navigation fit the mental model of the user and help them orientate?

• Findability - Does the experience help users find what they are looking for (on page, search)?

Additional Owners Experience Evaluation Criteria

• Proactivity - How reactive or proactive is the support given?

• Ease of access - Similar to friction, but across all touch points, how easy is it for a user to engage?

• Delight - Does the experience feel desirable, liked and provide novel moments that are memorable?

Things to ignore

• Minor UI Issues (Like Product picture alignment in cells)

• Content Issues/Sentence grammar

OTHER DETAILS

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

Device: Laptop/ Desktop/Mobile/Ipad/Tablet

Operating System: Latest version Windows , macOS, IOS , Android

  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 1st place - $300; the participant with the 2nd most points will win $200 and third place will win $100.

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

• 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  will have negative scoring ( with 5 points) for issue creator.

• Please make sure to log issues according to the guidelines provided on the submission section. Issues that do not follow guidelines may be rejected due to lack of information.

• If two users submit the same issue, the user that submitted the issue first will receive credit.

ISSUE WEIGHTS

• Functionality Issues - 10 Points

• User Interface Issues - 5 Points

• Usability/UX Issues - 5 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.
  You need to find issues worth of minimum 100/75/50 points to earn the 1st, 2nd and 3rd  prizes respectively and you will receive $5 per issue in the case if total points of the issues does not meet the above scenario.

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: Used browser.

• 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 

• Bug Priority : High/Low/Medium

• Bug Type : type of bug

• Testing collateral:  Screenshots of Device and Browser Details,  screenshots and video (only for functional and UX issue) of issue.  ( 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: <>