Challenge Overview
Welcome to the Brivo Website Bug Hunt Challenge! The goal of this challenge is to find bugs in the newly created Brivo website|http://xtranetbrivo.wpengine.com/ and report these bugs in our GitLab project
Challenge Objective
We want to check for aesthetics/design and functionality bugs in the Brivo website - http://xtranetbrivo.wpengine.com/.
- Admin pages are out of scope
- External pages that links from this website are also out of scope
Browser Requirements
Page's design and Functionality should be tested in all mainstream browsers.
- IE9 to IE11
- Latest Safari
- Latest Firefox
- Latest Chrome
- Tablet browsers (Chrome and Safari)
- Mobile phone browsers (Chrome and Safari)
Ticket Logging
We will be using GitLab as the issue management, here's the outline of the process:
- You will need to create an account in GitLab if you haven't had yet
- Once you register for this challenge, send us GitLab login to jamesmarquez@gmail.com
- We will add you to the developers group on a repo in GitLab. This will give you access to work on issues, create branches, and pull requests
Scoring
- Topcoder will compensate members with first place submissions.
- The winner will be the member with the most accepted reports of valid bugs.
- For non-winning members, there will be a $5 prize for each valid bug found that isn't in the winning submission.
- If two submitters submit the same bug report, the submitter who submitted the report first into GitLab will get credit for the bug. The second submitter will not.
- If two or more bugs that belongs to same submitter and has only slight changes, only 1 issue will be counted
- If the submitted issue is already existing or logged in GitLab, then it will be considered duplicate.
Final Submission Guidelines
For each bugs, we need the following information:
- Detailed description of the bug or at least a description that make sense
- Steps to reproduce, including any needed information
- Screenshots or screencasts
- Expected results
- Current results
- OS, Browser and version
Important Notice:
- If you do not properly document your bug reports, they will likely be rejected due to lack of information or documentation. Also, make sure your bug reports are reasonably general.
- If you submit the same bug that is seen in multiple screens, for instance, you will likely only get credit for the original bug report. The others will all be closed as duplicates.
- You need to report your issues in GitLab and you MUST submit a text file with a list of your reported bugs as your submission file into OR during the submission phase, for review purposes. If you do not do this, you will not get credit for any logged bugs!