Valentine Month Special: Topcoder QA Fun Challenge Series 8 - Thrive Web App Bug Hunt

Challenge Overview

Welcome to participate in this challenge. This is a Bug Hunt style competition focused on exploratory testing for a web application.
 

Note: this challenge will have 24h for registration (during this phase no one will see details) and then 48h for bug hunting.

We’ll use github (https://www.github.com) to create issues. Please create a github account if you do not have one. The URL for creating issues will be shared after the submission phase starts.
 

If this is your first competition on Topcoder do not fear - we have all the instructions, you need to go through this challenge specification and check 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.

 

Prizes:

1st Place: $300 

2nd Place: $150

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.

Challenge Details

The topcoder Thrive is a place where topcoder and community shares guides, tutorials etc for the topcoder community members.

This valentine let's work together to make Thrive the most loved app of topcoder. Let's find the bugs and let the team make the Thrive app the best!

In this challenge you have to test all functionalities featured on Thrive and log defects. <b>Only Functional, UI, and UX issues</b> will be considered.

Testing URL: https://www.topcoder.com/thrive

Github URL for creating issues: https://github.com/topcoder-platform/community-app/issues

Note: The URL of valid bugs must begin with the above Testing URL. e.g. https://www.topcoder.com/thrive/tracks?track=Competitive%20Programming&tax=Recursion is a valid bug URL.

Target Platforms: Windows and Mac OS

Target Browsers: Latest Google Chrome and Firefox

Final Submission Guidelines

Bug Report Template

Please use the following template while creating a new issue:

Title: <Concise description of the bug>

================Body part starts=================

Target URL: <Fill the URL of this bug>

### Reproduction Steps ###

<Detailed steps to reproduce the bug>

### Expected Result ###

<Expected result after reproduction steps>

### Actual Result ###

<Actual result after reproduction steps>

### Screenshots or screencast ###

<Screenshots or screencast showing the bug>

### OS/Browser Information ###

<Detailed OS and Browser Information>

================Body part ends=================

Bug Label: <Select one of Functional, UI, UX>  (Make sure select correct labels for your bugs)
 

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.

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

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

• There will be no appeals phase. The decision of PM/co-pilot for validity and severity of each filed issue will be final.

ISSUE WEIGHTS

• Functional Issue - 10 Points

• UI Issue - 5 Points

• UX Issue - 1 Point

Scoring

For scoring, the submitter with the most points 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.

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 the 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 BEFORE the Submission phase ends. This file includes:

1. Your topcoder handle

2. Your Github username

 

- ALL THE SUBMISSIONS WITHOUT ABOVE INFORMATION WILL BE REJECTED AND WON'T BE PAID.

- IMPORTANT: Submit the above details before the Submission Phase ends. If you can't submit due to technical difficulties within the Submission Phase please email your submission with above details to support@topcoder.com

- Participants who haven't submitted will not be paid

- DON'T use any other link to create new issues OR submit as document, they won't count and won't be paid.