Challenge Overview
Hello Topcoder members! Welcome to the CertainTeed.com Unstructured Testing Challenge. This is a Bug Hunt style competition.
If this is your first competition on Topcoder, do not fear - we have all the instructions you need to participate in this challenge specification and in the challenge forums. Click the register button on this page to sign up, and then you’ll be granted access to the challenge forums where you can find documentation and ask questions.
IMPORTANT - This challenge has more than one prize placement! The number listed as first place is the total prize pool. Prizes will be awarded to the top 3 scorers as follows:
-
1st place: $600
-
2nd place: $300
-
3rd place $150
https://www.certainteed.com/ is predominantly used by home owners, dealers and distributors - looking for best material for their homes. It has been observed that home owners have grown increasingly sophisticated, thanks to their experiences with the host of other social media sites…and they would like a similar experience here. It is therefore key that the website enables end-customers to browse the products and services, search for relevant information, and where appropriate move from information gathering to purchasing products and logging into the secure site, regardless of their device.
This Bug Hunt challenge is targeting Functional and UI/UX suggestions to help our customer understand the issues lying in current website… and what can be improved in this website to make it more attractive for home owners, dealers and all those who wish to place orders.
- Usability issues and improvement suggestions from an end-user perspective (for e.g. ease of use, search, navigation, etc.)
- Cross browser-device compatibility issues
The website https://www.certainteed.com/ that you need to test them in are:
- Latest Google Chrome, Firefox, Safari and Internet Explorer (Edge) on the Desktop
- Any iOS (iOS 9.0 and later versions) and Android (4.4 and later versions) Mobile or Tablet testing that you can manage would be most appreciated
How to Log Tickets
1. Create an account on GitHub (if you do not already have one): http://www.github.com
2. Post your Github handle in the appropriate challenge forum thread. You will be added to the repository ASAP.
3. There is an issue template whenever you click New Issue in Github. Please use this template. Log issues here: https://github.com/topcoderinc/certainteed-qaas/issues
5. Please label issues with the appropriate browser type and mode, bug type, and platform type. The labels can be viewed here: https://github.com/topcoderinc/certainteed-qaas/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
2. Current results before the bug is fixed
3. Expected results, after the bug is fixed
4. Screenshots
5. Attach the high-level labels.
6. Attach detailed platform, device, operating system and browser version information in the issue detail. The high-level labels aren’t sufficient for issue replication and diagnosis.
Issue Weights
1. Functional Issues - 10 points
2. User Interface Issues - 2 points
3. User Interface Suggestions - 5 points
4. Duplicating existing issue on new platform, browser, or browser mode combination - 1 point.
Important Notice
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, for instance, you will likely only get credit for the original bug report. 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 developers.
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.
- Only verified issues will be counted. Tickets logged for enhancements or non-bug issues 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 bonus for unique verified issues.
Please note the $5 payment bonus is only for verified
1. Functional issues
2. User Interface Issues
This is NOT applicable for
1. User Interface Suggestions
2. Duplicate Issues even if the reproduced on different browser, platform mode.
If two users submit the same issue, the user that submitted the issue first will receive credit.
Tips
Some of the tips helpful for the contest:
- Submitting what is obviously the same issue multiple times with small variations will only annoy the reviewer that has to sort through all the issues and will only count as one issue anyway. If it's less obvious if it is the same issue or not, use your best judgment and the reviewers will do the same.
- 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.
- Double check your steps to reproduce and test cases to make sure they are clear. Make sure your steps include creation of any necessary data.
Final Submission Guidelines
Submit all your bugs directly to Github. When you are done with your submissions please submit a .txt file to Topcoder Online Review using the Submit to this Challenge button. In this file include:
-
your name
-
email address
-
topcoder handle
-
Github handle used to raise the issues.