Kitchen Inc - Unstructured Exploratory Bug Hunt Challenge

 

• Unstructured Testing

• Desktop site, Mobile Site

• E-commerce site

 

About the Application

 Kitchenaid.com is a site dedicated to all things kitchen - applicances, kitchenware, inspiration. It showcases the company products and has e-commerce features - product listing, cart, checkout, accounts, special offers, product registration, newsletter, product support sections, etc.
 

Assets

 

Project repository information is posted in the forums

 

What to Test (Scope)

https://www.kitchenaid.com is the site under test - all the site features are in scope except live chat and submitting actual orders (everything until the final order confirmation and checkout step is in scope, just don't submit real orders)
 

• Test URL: https://www.kitchenaid.com

• Accepted types of bugs: Functional, UI, UX Testing

• Subdomains: Pages to be tested are only that are within the main domain. Pages apart from the main domain will be rejected. Subdomains are out of scope

• Primary target device(s): Desktop, Mobile

• Browser requirements: Latest Google Chrome, Firefox, Safari and Edge on Windows/macOS. IE11 and below versions are out of scope. Safari on Windows is out of scope.

• Content Bugs are IN SCOPE [Spelling and Grammar, Missing/Broken Images/Videos inside product details pages and articles.]

• Also other minor UI, Usability, Content issues, Tooltip, Broken Link issues that are not affecting to the core functionality of the application are likely to be REJECTED.

• Important: Because you are testing a live website DO NOT Test/send data via contact forms, use live chat feature or submit orders. They are out of scope.

• An edge case would be anything that does not reflect typical user behavior. They are accepted accordance to the impact to the end-user and based on the workarounds available.

 

How to Create New Bug Report

 

1. Create an account on GitLab (if you do not already have one): https://gitlab.com.
2. You can get access to the GitLab repo using url 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 GitLab. Please use this template to report your issues.
4. Issues/Bugs found in this application/App must create here:  https://gitlab.com/kitchen-inc/testing/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 browser type, bug type, and platform type.  The labels can be viewed here: https://gitlab.com/kitchen-inc/testing/labels

 

Issue Reporting Guidelines

 

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

1. 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)

2. Current result(s) before the bug is fixed

3. Expected result(s), after the bug, is fixed

4. Screenshots for all UI/UX/functional issues - videos are not required

5. Attach the high-level labels: browser, issue type, platform

Missing or Incorrect details to ANY of the above fields will mark the bug report as INCOMPLETE. 

For example, Incorrect Steps, Missing Screenshot/Screencast (If it is a UI issue, you have to mark it on the screenshot), Incorrect Actual and Expected results etc.

 

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.

 

Scoring

 

• Functional Issues     - 10 Points

• User Interface Issues     - 5 Points

• Usability/UX Issue     - 2 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.