Challenge Overview
Welcome back to “Best Practices - Web Bug Hunt Challenge”. In this challenge, we would like to find issues in an Angular web application and its integration with backend.
Let us know in the forum if you have questions!
CHALLENGE REQUIREMENT
- Exploratory or unstructured testing and reporting.
- Complete as many as you can in 24 hours.
- Web application (Chrome, Edge, and Firefox) and backend integration. We are not looking to find all issues with backend application but just the endpoints to allow the web application to work properly.
Note: The challenge prizes are mentioned for top 3 placement prizes. For other submitters, there is additional prize money to be awarded per valid bugs or issues or suggestions created in the system and approved by the client after review - please refer issue weight and scoring section.
HOW TO PARTICIPATE
- Register to challenge and get the registration link to the repository with the source code.
- Deliverables: upload bug videos, bug screenshots and log files in the Gitlab issue. In Online Review submit a file with the list of issues submitted.
- Issues: Create new issues when you find any bugs during your execution.
Additional Rules:
- Follow the standard Topcoder Bug Hunt Rules (if any conflict please ask in the forum)
- 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 different platform that hasn’t been tested yet, you should create a new issue and add a link/reference in the issue comments section about the Original 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 closed by the reviewer and anyone who RE-OPENS a ticket will be disqualified from the challenge.
- DON'T EDIT OR ATTACH FILES to the issues once it has been submitted 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 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/Copilot for validity and severity of each filed issue will be final.
Issue Weight and Scoring:
- Scoring will be based on the number of bugs by weight. Be sure to correctly attach a label to your bug.
- The review team has the right to change an issue category, priority and severity at their discretion.
- Only verified issues by the reviewer and accepted by the client will 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 reject due to lack of information.
- For challenge scoring, the user with the most verified issues/points will be selected as the winner. If two users submit the same issue, the user that submitted the issue first will receive credit.
- For any suggestions or improvements, please create separate issues.
- The following points will be awarded as per issue category:
- Functional Issues: 10 Points
- Security Issues: 10 Points
- User Interface Issues: 5 Points
- Usability/UX/Suggestion/Improvements: 2 Points
- Content Issues: 1 Point
- For challenge scoring, the user with the most verified issues will be selected as the winner. Submitters that do not take 1st, 2nd or 3rd places will be paid $2 Per Earned Point 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.
Final Submission Guidelines
- Text file with:
- Gitlab handle
- Topcoder handle
- List of Gitlab issues