Topcoder Community Newsletter Bug Hunt

Welcome to the Topcoder Community Newsletter Bug Hunt challenge. Recently we have created a new template for our monthly Topcoder Community Newsletter. In this challenge, we are looking for you to find bugs in this 2020 Community Newsletter by testing it on a number of platforms & email clients listed in the specifications.

Note: this challenge will have 18h for registration (during this phase no one will see details) and then 24h for bug hunting.
Let us know any question you have!

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

Contest Objective

The purpose of this challenge to thoroughly test the Topcoder 2020 Community Newsletter on the required browsers, app & email clients. Please register to see details so you can test it effectively.
Gitlab account details to log issues have been provided in the forum.

The following types of issues are being looked for:

• Bugs in frontend
• UI/UX improvements

Platform Requirements

• Gmail iOS App
• Gmail Android App
• Gmail on Desktop browser (Chrome or Firefox)
• Yahoo iOS App
• Yahoo Android App !important
• Yahoo on Desktop browser (Chrome or Firefox)
• Outlook 2015 email client (Mac & Windows) !important
• Outlook 2019 email client (Mac & Windows) !important
• Outlook on Desktop browser (Chrome or Firefox)
• iOS native email app (iPhone & iPad)

The use of litmus for email testing is allowed.

Issue weight

• Category10 - 10 Points: UI Issue found on Outlook 2019 email, Outlook 2015 email & Yahoo Android App
• Category5 - 5 Points: UI Issue found on iOS native email app, Gmail iOS App, Gmail Android App, Yahoo iOS App
• Category1 - 1 Point: UI Issue found in Gmail, Yahoo or Outlook on Desktop browser

Bug Hunt Requirements

• In this bug hunt, at the start of the submission phase, we are going to send test emails containing the newsletter to be tested to your email accounts. We are also going to provide the HTML code of the same template that you paste here & send emails to your desired email account(s) for testing.
• You have to test the newsletter template on a number of platforms and log defects. Only UI related issues will be considered.
• You must follow the template listed below for logging bugs. A snapshot or a screencast of the issue reported is mandatory.

Template for creating a new bug:

Title: Title of the bug

//- Body Section -//

Screenshots or screencast

Screenshots or screencast

Platform

// Platform where the bug is reproduced //

Reproduction Steps

// Reproduction Steps of the bug //

Expected Result

// Expected Result of the bug //

Actual Result

// Actual Result of the bug //

//- End Body Section -//

Bug Label:

Select one of the Category1, Category5 or Category10 label

Bug Hunt Rules

• Follow the standard Topcoder Bug Hunt Rules
• If you do not properly document your bug reports, they will likely be rejected due to a lack of information or documentation.
• If you submit the same bug in multiple areas/pages, (for instance, the 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.
• DON'T EDIT OR ATTACH FILES to the issues in the review phase and anyone who is doing this will be disqualified from the challenge.
• 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 screenshots in the comments section though, assuming your issue report contains all the details when created.
• There will be no appeals phase. The decision of PM/co-pilot for validity and severity of each filed issue will be final.