Challenge Overview
Welcome to everyone in the “Dragonet Data Management - Unstructured bug hunt”! The goal of this challenge is to find defects in the application we have developed.
This challenge will open for 12 hrs registration period and then 48 hrs for bug hunting and submission. Information about the submission phase is posted in the forum.
Project Overview
The project will develop a web-based desktop application platform that will help the Information Security Risk & Compliance team of a global company to manage a large amount of data that will be used to generate key risk indicators(KRIs).
Technology Stack
React Js latest, .Net Core 3.1
Browser Requirements
Google Chrome
Assets
Hosted Sites: Will be shared on the forum
Application Codbases will also be shared on the forum, you can deploy in your local machine to add your own datasets.
Scope of Testing:
-
Functional
-
Performance
-
UI & UX.
Scoring
-
Scoring will be based on the number of bugs by weight. Be sure to correctly attach a weight to your bug. The reviewer has the right to change severity at their discretion.
-
Scoring is directly proportional to weight: Weight 1 = 1 point, Weight 10 = 10 points.
Issue Weights
-
The following points will be awarded as per the issue category:
-
Functionality/Performance: 10 Points
-
UI/UX: 5 Point
-
Prizes
The participant with the highest score will win 1st place, the member who gets the 2nd most points will win 2nd prize. Other than 1st and 2nd winner, submitters will receive a prize of $5 for each unique bug accepted up to a maximum of $50.
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 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.
-
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 create the same issue on different platforms; instead, merge them into one; All the others will be marked as Duplicate.
-
If you see multiple broken links on the same page, combine them into one ticket. Others will be marked as DUPLICATE.
-
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.
-
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.
-
There will be no appeals phase. The decision of PM/Copilot for validity and severity of each filled issue will be final.
Final Submission Guidelines
Please find the defects and log them on Gitlab(which is provided on the forum) in the format given here https://gitlab.com/topcoder-consulting/dragonet/frontend-app/-/issues/28. When you are done with your reporting, please submit a .txt file in Direct using the "Submit" button before the submission phase ends. In this file please include the following details:
TopCoder Handle: <>
Gitlab Username: <>