Challenge Overview
Challenge Objectives
- Manually test the Function and UI of Firefly Subpoena app.
- Log defects on GitLab
About the Application
Firefly is an insurance company and currently they are utilizing 2 separate systems for processing Subpoenas. The Documents Team has one system and the Subpoena Team has another. A Subpoena is a legal document from the court stating that some particular documentation is required for a legal case. The Documents team receives the request and enters the necessary data into the system. They then create an assignment for the Subpoena team. The Subpoena team then goes in and sees that some of the fields have been filled out by the Documents team. They can see what the request is, for example, a person’s medical records might be needed by a certain due date. The problem is that once the Documents Team sends the request over to the Subpoena Team, they have limited visibility. They can see the documentation and information that they entered, but they can’t see who it’s been assigned to or what the status is. We would like to create 1 cohesive system.
Assets/Design
Please check forum.
What to Test (Scope)
- Perform Exploratory Testing on the prototype to looking for functional issues (ref. the requirements from UI Prototype challenge)
- Refer the Design Links and verify the UI
- GitLab Repo to log defect: https://gitlab.com/firefly-prototype/subpoena/issues
- Accepted types of bugs:
- Functional
- UI
- UX
- Primary target device(s):
- Desktop Only
- 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 GitLab:
- Bug Hunt Label
- 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)
- 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 GitLab. 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)
- GitLab handle used to raise the issues. (Login to GitLab and click on the Profile picture > Your Profile. Check the URL 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