Challenge Overview
Welcome to the HP Exploratory Unstructured Testing Challenge!
HP is a multinational information technology company. For this challenge, we will conduct
unstructured exploratory testing on the company’s online store.
This is a bug hunt style competition.
This challenge will have a 24hr registration period and then 3 days for bug hunting.
Information about the submission phase is posted in the forum.
WHAT TO LOOK FOR
Perform the testing as best you see fit. Approach the application as if you were an end user.
In this test cycle, you will be looking for:
Functional issues
Performance / Security issues
UI issues / UX issues
Content issues are out of scope. Please ignore Minor UI issues (cell /picture alignment) also.
Some key issues to report:
– Functional Errors, including ‘Access Denied’ errors
– Unresponsive/slow performance
OTHER DETAILS
��� Test URL: https://uat.store.hp.com/us/en
��� Page flow to be tested.
��� Any test account used to test the functionality of registration must be recorded in the
issue details.
��� Type of users : Registered / Guest.
��� ONLY valid Functional, Security, performance , UI, and UX issues are in scope.
��� Target device(s): Desktop, Mobile/Laptop/Tablet
��� Browser Requirements: Latest Google Chrome, Firefox, Safari, IE11/Microsoft Edge on
Windows, macOS, Android or iOS.
NOTE: We are only testing the page flow illustrated above by the client, at the given URL.
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: ex. Weight 1 = 1 point, Weight 10 = 10
points.
��� The participant with the highest score will win 1st place - $600; the participant with
the 2nd most points will win $300 and third place will win $200.
��� 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 be rejected due to lack of information.
��� 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. If two users
submit the same issue, the user that submitted the issue first will receive credit.
ISSUE WEIGHTS
��� Functionality Issues - 10 Points
��� Performance / Security Issues - 10 Points
��� User Interface Issues - 5 Points
��� Usability/UX Issues - 2 Points
HOW TO PARTICIPATE
��� Jira: Please request access to Jira in the forums if you have not received an email
invite.
��� Gdrive: Please submit testing collateral to the Gdrive link posted in the forum.
Issue reporting will open 24 hrs after the challenge starts. Please do not report any
issues in JIRA until then. They will not be accepted. The announcement will be made in
the forum when the time comes - please watch the forum for it and other updates.
Read the challenge specification carefully and watch the forums for any questions or
feedback concerning this challenge. Let us know if you have any questions in the
challenge forum!
��� Device: The type of device used.
��� Operating System: OS you are using. Only Windows, MacOS, Android and iOS are in
scope.
��� Browser: The browser used.
��� Steps to reproduce, including any additional information (Must list all the steps that
need to reproduce the bug.)
��� Actual result: What actually happens
��� Expected results: What should happen
��� Testing collateral: In Gdrive, upload the:
Video recording and/or Screenshot(s)
Console log
Screenshot of OS version
Screenshot of browser version
Be sure to put the Gdrive link in the appropriate field in JIRA.
When you are done with 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: ()
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.
��� 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.
Payments
Topcoder will compensate members in accordance with our standard payment policies,
unless otherwise specified in this challenge. For information on payment policies, setting up
your profile to receive payments, and general payment questions, please refer to Payment
Policies and Instructions.
HP is a multinational information technology company. For this challenge, we will conduct
unstructured exploratory testing on the company’s online store.
This is a bug hunt style competition.
This challenge will have a 24hr registration period and then 3 days for bug hunting.
Information about the submission phase is posted in the forum.
WHAT TO LOOK FOR
Perform the testing as best you see fit. Approach the application as if you were an end user.
In this test cycle, you will be looking for:
Functional issues
Performance / Security issues
UI issues / UX issues
Content issues are out of scope. Please ignore Minor UI issues (cell /picture alignment) also.
Some key issues to report:
– Functional Errors, including ‘Access Denied’ errors
– Unresponsive/slow performance
OTHER DETAILS
��� Test URL: https://uat.store.hp.com/us/en
Testing should be done only for the given page flow at https://uat.store.hp.com/us/en, for the US store..
If the url gets redirected to any country, please change the url back to /us/en.
If url gets redirected to any other page/domain other than ‘uat.store.hp.com/us/en’, it is
out of scope for testing. The only exception is Paypal.
Do submit orders as this is a UAT environment. We will share the credit card test
accounts in the forum.
If the url gets redirected to any country, please change the url back to /us/en.
If url gets redirected to any other page/domain other than ‘uat.store.hp.com/us/en’, it is
out of scope for testing. The only exception is Paypal.
Do submit orders as this is a UAT environment. We will share the credit card test
accounts in the forum.
��� Page flow to be tested.
��� Any test account used to test the functionality of registration must be recorded in the
issue details.
��� Type of users : Registered / Guest.
��� ONLY valid Functional, Security, performance , UI, and UX issues are in scope.
��� Target device(s): Desktop, Mobile/Laptop/Tablet
��� Browser Requirements: Latest Google Chrome, Firefox, Safari, IE11/Microsoft Edge on
Windows, macOS, Android or iOS.
NOTE: We are only testing the page flow illustrated above by the client, at the given URL.
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: ex. Weight 1 = 1 point, Weight 10 = 10
points.
��� The participant with the highest score will win 1st place - $600; the participant with
the 2nd most points will win $300 and third place will win $200.
��� 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 be rejected due to lack of information.
��� 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. If two users
submit the same issue, the user that submitted the issue first will receive credit.
ISSUE WEIGHTS
��� Functionality Issues - 10 Points
��� Performance / Security Issues - 10 Points
��� User Interface Issues - 5 Points
��� Usability/UX Issues - 2 Points
HOW TO PARTICIPATE
��� Jira: Please request access to Jira in the forums if you have not received an email
invite.
��� Gdrive: Please submit testing collateral to the Gdrive link posted in the forum.
Issue reporting will open 24 hrs after the challenge starts. Please do not report any
issues in JIRA until then. They will not be accepted. The announcement will be made in
the forum when the time comes - please watch the forum for it and other updates.
Read the challenge specification carefully and watch the forums for any questions or
feedback concerning this challenge. Let us know if you have any questions in the
challenge forum!
Final Submission Guidelines
For each report of a limitation or bug, we need the following information:��� Device: The type of device used.
��� Operating System: OS you are using. Only Windows, MacOS, Android and iOS are in
scope.
��� Browser: The browser used.
��� Steps to reproduce, including any additional information (Must list all the steps that
need to reproduce the bug.)
��� Actual result: What actually happens
��� Expected results: What should happen
��� Testing collateral: In Gdrive, upload the:
Video recording and/or Screenshot(s)
Console log
Screenshot of OS version
Screenshot of browser version
Be sure to put the Gdrive link in the appropriate field in JIRA.
When you are done with 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: ()
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.
��� 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.
Payments
Topcoder will compensate members in accordance with our standard payment policies,
unless otherwise specified in this challenge. For information on payment policies, setting up
your profile to receive payments, and general payment questions, please refer to Payment
Policies and Instructions.