Challenge Overview
Project Overview
This project, the CSFV Community Gaming website project will provide the web site infrastructure and integration of the games. This will be a web site that is available on the Internet, and also will be delivered in a form where the server and the games can be installed and used behind a firewall.
Contest Objective
The goal of this bug hunt is to find UI, Functionality, and Content bugs in the CSFV websites in the staging server (development environment).
The websites in scope of this challenge :
- verigames
- circuitbot
- xylem
- flowjam
- ghostmap
- stormbound
- use 'member/m3mb3r' to bypass nginx login dialog
Things to test in this challenge :
- User Interface and Styling issues :
- Chat is out of scope
- We did css cleanup for all websites and some areas were broken
- Functionality issues
- We did refactoring for javascript, and some functionality might be broken
- It should user and admin functionality
- Inconsistent functionality flow should be reported
- Testing should include scenarios that break the website
- Content issues :
- Dummy content should be reported
- Spelling and grammer issues
- Testing should cover broken links or content that may break the website
- Works in different browsers
- IEs are out of scope.
Browser Requirements
The given application must be tested in all latest browsers except IE browsers as it is out of scope.
Users
- You should create users via Register flow
- For admin role, post a request in the forums with the username you want to grant admin access to, Copilot will set that user as admin.
Contest Guidelines
The guidelines for this contest are given below:
- As issues are identified they need to be logged in JIRA.
- Issues must include clear descriptions, test cases and steps to reproduce and expected vs. actual results in order to be counted.
- First competitor to find an issue gets credit, duplicates will not be counted.
- Reviewers will accept, reject or mark the issues as duplicate.
- Please DO take a look at the reported bugs, duplicated bugs cost your work time and the reviewer's time.
- Issues will be classified via points system :
- 5 points for functionality issue
- 3 points for UI and styling issue
- 1 point for content issue
- The member who get most points will win first place prize, others will get $2 per point.
Important Notice:
You must also be the first person to report the issue and submit it while submission phase is open. JIRA will allow you to file issues before and after the submission phase, but these will NOT be counted.
Final Submission Guidelines
Bug Report Process
Bug Report Format
For each report of a limitation or bug, we need the following information:
- Steps to reproduce, including any needed information
- Screen shots (if applicable)
- Expected results after the bug is fixed
- Current results, before the bug is fixed
- Browser 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.
Ticket Logging
You will log your tickets here: https://apps.topcoder.com/bugs/browse/CSFV and when creating a bug you MUST select the "2014 - CSFV Websites Bug Hunt Series" Bugs will not be counted if a selection is not made.
Scoring
The Scoring guidelines followed for the contest are given below:
- Issues will be classified via points system :
- 5 points for functionality issue
- 3 points for UI and styling issue
- 1 point for content issue
- For scoring, the submitter with the most accumlated points will win.
- For submitters who submit but don't take first, they will receive $2 per point.
Important Notice:
If two submitters submit the same bug report, the submitter who submitted the report first into JIRA will get credit for the bug. The second submitter will not.
Tips
Some of the tips helpful for the contest are:
- Submitting what is obviously the same issue multiple times with small variations will only annoy the reviewer that has to sort through all the issues and will only count as one issue anyway. If it's less obvious if it is the same issue or not, use your best judgment and the reviewers will do the same.
- Put an eye on the issues being submitted by other members 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.
- Double check your steps to reproduce and test cases to make sure they are clear. Make sure your steps include creation of any necessary data.
Submission Deliverables
You need report your issues in JIRA. Please submit a text file contains the bugs you reported to OR.
Final Submission
- For each member, the final submission should be uploaded to the Online Review Tool.
- You must not include any identifying information, such as your handle, in your submission. Your submission should be anonymous and you will be scored down in screening for not complying.