HP Exploratory Testing Series - 6

Welcome to the HP Exploratory Testing Series -6 Bug Hunt challenge . All you need is to explore the app and report the bug in the Jira. The format for reporting the bugs are given below, please go through the submission section. 

This challenge will open for  24 hrs registration period and then 72 hrs for bug hunting and submission.  Please do not report any issues in Jira  until then. They will not be accepted.

ABOUT THE APPLICATION

HP is a multinational information technology company. For this challenge, we will conduct

unstructured exploratory testing on the company’s online store.

Assets

Application Testing URL : will share on forums once registration period is over.

WHAT TO TEST : Verify url pattern change for the entire store. Ensure the URL now contains the context ‘/us-en/shop/’ instead of ‘/us/en/

Page / Flow :  Will share on forums once registration period is over.

Things to look out for 

• Functional Errors ( ETR URLs should contain /us-en/shop/ on a given test case).

• Broken urls, images, access denied errors

Things to ignore

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

• Content Issues

OTHER DETAILS

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

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 $150. Submitters that do not take 1st, 2nd place will be paid $5 for each non-duplicate and verified issue up to a maximum of the 2nd place prize for top 200 valid issues. 

• 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 the submission section. Issues that do not follow these 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

• Functional issue ( URL mismatch ) - 5 Points

• Usability/UX Issues (Broken urls, images, access denied errors

) - 2 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 Type][Browser] Issue Desc eg. [Web] [Chrome] Unable to add product.

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