Challenge Overview
Challenge Objectives
Welcome to yet another Bug Hunt(Exploratory testing) challenge for Suite of Services website testing. All you need is to explore the website and report the discrepancy in the Gitlab. The format for reporting the bugs are given in the Gitlab.
This challenge will open for 24 hrs registration period and then 72 hrs for bug hunting and submission. Information about the submission phase is posted in the forum.
ABOUT THE APPLICATION
This is an application of suite of service, the all in one toolbox to accelerate the digital transformation. Through this portal, the company offers a variety of services from knowledge to Assets and services to the Executives, digital Leads, Project Managers and many more within the organization.
Assets
Application Testing URL/ Test User credential : Please find on forum section.
Note : Don't create your own test user, because new user need to get approval from client. Use only given test user credential.
WHAT TO TEST
Perform the exploratory testing as being an End user of this application.
Scope of Testing: Functional, UI and UX.
OTHER DETAILS
Browsers: Latest stable Chrome, IE11, Edge, Firefox and Safari
Platforms: Windows, Mac, Android, iOS - any model and OS of the platform version
Bug Repository: Gitlab
SCORING
-
Scoring will be based on the number of bugs by weight. Be sure to correctly attach a weight to your bug. The delivery team has the right to change a severity at their discretion.
-
Scoring is directly proportional to weight: Weight 1 = 1 point, Weight 10 = 10 points.
-
The participant with the highest score will win the 1st place - $600, the member who gets the 2nd most points will win $300 and third place will win $200.
-
Only verified issues will be counted. Tickets created for enhancements or that are not bugs will not 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 be rejected due to lack of information.
-
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 place will be paid $5 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.
ISSUE WEIGHTS
-
Functionality Issues - 10 Points
-
User Interface Issues - 5 Points
-
Usability/UX Issues - 2 Points
HOW TO PARTICIPATE
-
Create new test user from given Application Test URL at External Visitors section (you will find test application on forums)
-
Create an account on GitLab (if you do not already have one): https://gitlab.com.
-
You can get access to the GitLab repo using ‘Ragnar’ tool specified in the challenge forum thread to create new bugs OR If you are still getting 404 error, request access to the repo using correct forum thread.
-
There is an issue template whenever you click New Issue in GitLab. Please use these template to report your issues.
Let us know if you have any questions in the challenge forum!
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.
-
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 screen shots 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
For each report of a limitation or bug, we need the following information:
-
Issue Title
-
Device: The type of device used.
-
Operating System: OS being used. Only Windows, MacOS, Android and iOS are in scope.
-
Browser: Latest stable Chrome, IE11, Edge, Firefox and Safari
-
Steps to reproduce, including any additional information (Must list all the steps that need to reproduce the bug.)
-
Actual result: What actually happened
-
Expected results: What should happen
-
Bug Reproduction Ratio
-
Bug Priority : High/Low/Medium
-
Bug Type : Functional/UI/UX
-
Testing collateral: Screenshot(s) with issue highlighting
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: <>