Connect App Bug Hunt

 

Welcome all to the Connect New Internal Catalog Release Bug Hunt.

 

Challenge Objectives

 

• Manually test the Connect - Project creation flow with the new Internal Catalog

• Log defects on GitLab

 

About the Application

 

Topcoder Connect app is a Project Management Tool used by Topcoder Customers, Copilots and other users to create new projects, add Teams and Topcoder members with different roles, share assets and send messages. 

 

 

What to Test (Scope)

• Perform Exploratory Testing on Connect Project Creation flow. The Connect catalog has been updated to improve its presentation.

All 3 screens of the Connect catalog have been updated:

            Screen 1: Solutions vs. On Demand options

            Screen 2: Full List of Solution Options

            Screen 3: Full List of On Demand options (TaaS/Capacity)

Make sure to perform e2e testing. All the data entered in the project creation flow must be carried over to the corresponding project details page.

• Refer the Design Links and verify the UI as well as its Function Design https://marvelapp.com/cc9e4j1/screen/62801529

• GitLab Repo to log defects: https://github.com/appirio-tech/connect-app/issues Create new bugs you find in this repo.
  Please make sure to check if the issue is not already logged here.

• Test URL and user credentials : Available in the forums

• Accepted types of bugs:

  • Functional

  • UI

  • UX

• Target device(s):

  • Primary - Desktop

  • Secondary - Mobile and Tablet

• Browsers in scope: 

  • Google Chrome

  • Firefox

  • Safari on Mac

  • Edge

  • IE11

• Issue Label: Set the following 4 labels for each issue you log in the GitHub:

  • Bug Hunt Label “BugHunt”

  • One of the Labels: 

    • Functional

    • UI

    • UX

  • One of the Priority Labels:

    • P1 - High (break the user experience and need to be fixed ASAP)

    • P2 - Normal (functional Issue with medium impact in user experience)

    • P3 - Low (minor functional issue or visual/layout issue)

Add the following comments to the issue to add or remove labels 

@bug-hunt-helper add label: Label Name 1, Label Name 2

@bug-hunt-helper remove label: Label Name 1, Label Name 2

Use the following comment to get help on the bug-hunt-helper

@bug-hunt-helper help

 

• 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.
   

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 at least 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.

• 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