Challenge Overview
Challenge Objectives
-
Identify and log defects that were introduced after the Angular upgrade on the Binder Portal UI application.
About the Application
Recently, we upgraded our Binder Portal UI app to the latest version of Angular 8. This was a major upgrade and we had to replace some of the dependencies which is something that could potentially break the application.
What to Test (Scope)
In this challenge, you need to compare the latest version of the application with the original version that the client had provided before we do the Angular upgrade and identify any functional or UI issues that were introduced after the Angular upgrade.
-
Repo URL: https://github.com/tc-bluesource/binder-portal-ui You will find a link on the challenge forum that can be used to join our Github organization so you can access the repo in case you don’t have access already. Note: You need to have MFA enabled on your Github account in order to join our organization.
-
You will need to deploy the app locally. Follow the README.md for instructions and if you have any issues with deployment, please use the challenge forum.
-
You need to compare it with the very first commit on the repo.
-
Since you won’t have access to the actual APIs that our client is running, you will have to use our mock API (https://github.com/tc-bluesource/mock-api - develop branch) instead. You also need to run this locally.
-
Accepted types of bugs: We only target functional and UI issues for this bug hunt.
-
Primary target device(s): Desktop
-
Browser requirements: Latest Google Chrome, Firefox and Safari.
-
Content Bugs are OUT OF SCOPE/IN SCOPE [Spelling and Grammar, Text spacing issues inside a paragraph, Tooltips, Missing/Broken Images/Videos inside an article, Font mismatch, Broken links on news articles, blog posts, products details pages, FAQ, Privacy, Terms and Conditions and articles.]
-
Do not report edge cases. An edge case would be anything that does not reflect typical user behavior. They are accepted accordance to the impact to the end-user and based on the workarounds available.
How to Create New Bug Report
-
Create an account on GitHub (if you do not already have one): https://github.com
-
You can get access to the GitHub repo here: https://github.com/tc-bluesource/binder-portal-ui
-
Issues/Bugs found in this application/App must create here: (URL for creating Bugs) https://github.com/tc-bluesource/binder-portal-ui/issues. DON'T use any other link to create new issues OR submit a document, they won't be counted and won't be paid.
-
Please label issues with the appropriate browser type and mode, bug type, and platform type.
Issue Reporting Guidelines
For each report of a bug, we need the following information:
-
Steps to reproduce, including any needed information (Must list all the steps that need to reproduce the bug, DON'T list only the URL without test data)
-
Current results before the bug is fixed
-
Expected results, after the bug is fixed
-
Attach screenshots, videos (You can attach videos directly on Github, if not use services like www.screencast.com or https://monosnap.com Don’t use www.youtube.com to host the videos) & Crash - Console/Crash Logs that will be helpful to understand the bug.
-
Attach the high-level labels. If you are selecting multiple labels (Platform/Device); You have to provide screenshots for each and every Device/Platform you have selected; If not the Bug will be REJECTED. [Eg: If you select labels Device: iPhone, Device: Android you have to provide screenshots of all the device types you have selected]. Same applies to Platform.
-
Attach detailed platform, operating system (Window 7 64 bit, MacOS etc.), Frequency in the issue detail. The high-level labels aren’t sufficient for issue replication and diagnosis.
-
If it is a comparison, you must provide the URL and Screenshot/video of that location.
IMPORTANT NOTE:
Missing or Incorrect details to ANY of the above fields will mark the bug report as INCOMPLETE.
For example, Incorrect Steps, Missing Screenshot/Screencast, Incorrect Actual and Expected results etc.
Be careful when you are providing only the direct URL and not listing the steps to go to that particular page in 'Steps to reproduce' section. Sometimes the Provided URL with parameters won't load the page to the reviewer and the bug may get closed as 'CAN'T REPRODUCE'. So better to list all the steps till the end or double check the URL is loading or not.
Issue Weights and Scoring
-
Scoring will be based on the number of bugs by weight. Be sure to correctly attach a weight to your bug. The copilot has the right to change a severity at his discretion.
-
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 reject due to lack of information.
-
For challenge scoring, the user with the most verified issues will be selected as the winner. If two users submit the same issue, the user that submitted the issue first will receive credit.
-
Please focus on functionality/UI testing based on the requirements, all bug reports based on your own assumptions will be rejected.
In addition to the first place prize, we will be awarding the following prize money to other competitors.
-
Blocker/ Critical: $10 [10 Points]
-
Major: $8 [8 Points]
-
Minor: $5 [5 Points]
-
Enhancement: $2 [2 Points]
P1 - Blocker: This bug causes the app to fail. No workaround exists. E.g. app crashes, app freezes.
P2 - Critical: This bug causes the app to fail for some specific cases. No workaround exists.
P3 - Major: This bug causes the app to fail, but there’s a workaround to prevent that issue.
P4 - Minor: This is an annoyance, but won’t prevent the app from running normally.
P5 - Enhancement: Something noticed by testers that should be fixed, but isn’t considered a bug.
The additional prizes will be up to $200 for 2nd position, $100 for 3rd position and $50 for 4th position. No prizes will be awarded beyond the 4th position for any 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.
-
If Mobile and Tablet testing are available 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 Copilot for validity and severity of each filled issue will be final.
What to Submit
Submit all your bugs directly to GitHub. When you are done with your submissions please submit a .txt file using the “Submit” button before the submission phase ends. In this file include:
-
Your Topcoder handle (The one displayed in the top right corner near the Profile picture)
-
Your GitHub handle used to raise the issues.
- ALL SUBMISSIONS WITHOUT THE ABOVE INFORMATION WILL BE REJECTED AND WON’T BE PAID.
- IMPORTANT: Submit the above details before the Submission Phase ends.
- DON'T use any other link to create new issues OR submit as document, they won't count and won't be paid.