Topcoder Marketing Platform Unstructured Bug Hunt Challenge

This challenge will have 24hrs for the registration (during this phase no one will see details) and 24hrs for bug hunting. Details will be posted on Nov 28, 23:00 EDT.

Challenge Objectives

• Exploratory or unstructured testing and reporting
• ���Layout, Functionality, Accessibility, and Performance issues

About the Application 

The Topcoder Marketing will be releasing additional pages intended for Topcoder’s Platform information and updates. We want the site to be error free in terms of UI and functionality, fast to load, and complies with the accessibility standards.

Browser Requirements:

The pages should be responsive.

• Desktop: Latest versions of Chrome, Microsoft Edge, IE11, Safari, and Firefox Browsers (Mac & Windows). 
• Mobile: Chrome, Safari, and Firefox

Attachment requirement:

• You MUST attach images and videos to the ticket as their original file type, NOT as zip files.  
• Images are preferred over videos - don't use a video to replace something that could easily be a screenshot.

Challenge Scope:

• Focus on the content section. The top navigation and footer sections are out of scope.
• Look for typo, broken links, and content issues.
• All "Book a Demo" buttons and its variants are URL placeholders for now, so don't report that as an issue.
• All the links for the bottom section "CONTRACT TOP TALENT START A PROJECT OR TALK TO SALES" are placeholders for now and out of scope.
• The description in each item in the Pricing table are also placeholders and out of scope.

Challenge Guidelines:

1. As issues are identified they need to be logged on Gitlab, you can find the link to the Gitlab page in the forum once you register.
2. Issues must include clear descriptions, steps to reproduce and expected vs. actual results in order to be counted.
3. The first competitor to find an issue gets credit, duplicates will not be counted.
4. Reviewers will accept, reject or mark the issues as duplicate.
5. Please DO take a look at the reported bugs, duplicated bugs cost your work time and the reviewer's time.
6. The copilot, reviewers, and PM decide whether a bug is valid or not based on our knowledge about the pages.  There will be no appeals.
7. Please thoroughly test the pages and find all kinds of issues.
8. Functionality testing must be based on the common functionality, all bug reports based on your own assumptions will be rejected.  If you are unsure about something, please ask in the forum.
9. Our expectation from Members is that they will report bugs on different browsers/ platforms under the same ticket if they have means to test it. Members should not be creating separate tickets for the same repeating bugs for separate platforms/browsers. In such a case it's totally up to the copilot and reviewers whether to accept the bug or not.
10. 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 (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 screenshots in the comments section though, assuming your issue report contains all the details when created.

Important Note:

You must also be the first person to report the issue and submit it while the submission phase is open. Issues submitted outside the submission phase will NOT be counted and will be rejected.

Contest Prize Eligibility

The submitter with the most accepted bugs will win the contest. 

Final Submission Guidelines

Final Submission Guidelines

1. Bug Report Process

Bug Report Format
For each report of a bug, we need the following information:

1. Steps to reproduce, including any needed information
2. Screenshots or Screen Capture (required)
3. Expected results after the bug are fixed
4. Current results, before the bug is fixed
5. Browser version and OS version

Important Notice:
If you do not properly document your bug reports, they will likely be rejected due to a lack of information or documentation. Also, make sure your bug reports are reasonably general.

If you submit the same bug that is seen in multiple screens, for instance, you will likely only get credit for the original bug report. The others will all be closed as duplicates.

2. Ticket Logging
You will log your tickets in the specified Gitlab repo that will be posted in the forum.

3. Scoring
For scoring, the submitter with the most accepted bugs will win 1st place.

For submitters who submit but don't take the top place, if they submit bugs that aren't covered in the top 2 place submissions, they will receive a prize of $5 for each unique bug reported up to a maximum of the second-place prize.

If one member tests and report issue in one OS, the member is supposed to test the same issue in all mainstream browsers in that OS, specifically:
- Windows: Edge / IE11 / Chrome
- Mac OS: Chrome

Our expectation is this member should file bugs for all the remaining platforms/browser, if they have means to do it. (Assumption is that a member filing the repeating bug has not filed any matching bug for a separate platform/ browser already. In such cases we will reject it.)

Important Notice:
If two submitters submit the same bug report, the submitter who submitted the report first into Gitlab will get credit for the bug. The second submitter will not. 

4. Tips
a) 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.  You are welcome to ask in the challenge forum for clarification.

b) Put an eye on the issues being submitted by other members 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.

c) Double-check your steps to reproduce and test cases to make sure they are clear. Make sure your steps include the creation of any necessary data.

5. Submission Deliverables
You need to report your issues in Gitlab. Please submit a text file containing the bugs you reported to OR.

6. Final Submission
For each member, the final submission should be uploaded via the challenge detail page on topcoder.com.