Challenge Overview
Challenge Objectives
-
Manually test the Function and UI of Topcoder’s New Navigation on Desktop and Mobile
-
Log defects on github
About the Application
We are in the process of migrating many of the legacy pages of our platform to the new Community App repo based on a newer technology stack and improve the overall user experience. In this challenge, we are going to test the Function and UI of the New Navigation Top Bar.
Assets (provided in the forum)
-
New Navigation UI Design
-
A Google document which has a quick overview of what the navigation should do
What to Test (Scope)
-
Perform Exploratory Testing on the New Navigation Top Bar. Do not test any other part of the application. Refer the Google document provided in the forum for the functions to test.
-
Refer the Design Links and verify the UI
-
Make sure to turn on the Handoff mode in the Marvel Design and verify in the application that attribute of each element in the nav is as per the design
-
Test URL and User Credentials: Posted in Forum
-
Github Repo to log defect: https://github.com/topcoder-platform/community-app/issues
-
Accepted types of bugs: Functional, UI and UX
-
Primary target device(s): Desktop, Mobiles and Tablets
-
Browsers in scope: Latest Google Chrome, Firefox, Safari on Mac, Internet Explorer (Edge) and IE11 on Windows
-
Issue Label: Set the following 4 labels for each issue you log in the Github
-
“Bug Hunt” Label
-
“Navigation” Label (without this we will not be able to find the issues you have logged for this Bug hunt. So make sure you add this without fail)
-
One of the Labels: “Functional” or “UI” or “UX”
-
One of the Priority Labels:
-
“P1”- urgent (to be resolved within 24 hours.)
-
“P2”- important (to be resolved within 3 days. Assign to yourself or someone so they are aware)
-
“P3”- normal (to be resolved within 7 days. Assign to someone or open for pickup)
-
“P4”- low (to be resolved within 3 weeks. Assign to someone or open for pickup)
-
-
-
Known Issues: Issues with the label ” Navigation” are the known issues. Please do not duplicate them.
-
If the same issue is found on some other elements/levels/screens, club it into one single bug with all the details of the issue occurrence and log as one single bug.
-
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.
For New Bug Hunt Participants
If you are new to Bug Hunt Challenges, Please read this before starting to work: New Bug Hunter's Guideline
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 delivery team has the right to change a severity at their 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. Issues that do not follow these guidelines may get rejected.
-
For challenge scoring, the user with the most verified points will be selected as the winner. If two users submit the same issue, the user that submitted the issue first will receive credit.
-
Functional Issues - 10 Points
-
User Interface Issues - 5 Points
-
Usability/UX Issue - 2 Points
Submitters that do not take 1st or 2nd place will be paid $5 for each non-duplicate and verified issue up to a maximum of the 2nd place prize. To earn the 1st and 2nd place prizes, you need to find issues worth atleast 100 points. You will receive half prize if the total points of the issues >= 50 and < 100.
Final Submission Guidelines
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)
-
GitHub handle used to raise the issues. (Login to GitHub and click on the Profile picture > Your Profile. Check the URL https://github.com/[Your Username] | https://gitlab.com/[Your 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.