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.
Challenge Task Overview
We are forcing HTTPS protcol in CSFV staging website : https://verigames.org, the goal of this challenge is to identify all issues in the pages and functionality affected by this change.
Testing
- You are provided with test scenarios of the website, you will use them to test website pages, ui and functionality.
- You need to register new accounts (if you have not already from past bug hunts) to use it for testing.
- You also need to verify emails sent to users are rendered properly and the links are rendered correctly.
- Blocked and mixed content should be reported, everything loaded should be https, we still use http in some areas and we need to identify that.
This is staging website so we might have some misconfiguration that affect some functionality, you can report that to forums and Copilot will fix it.
Browsers in Scope
Latest Chrome, FireFox, and Safari browsers. IE browsers are out of scope.
Website Link
Staging website link is : https://www.verigames.org
The following minisites are out of scope :
- circuitbot.verigames.org
- xylem.verigames.org
- flowjam.verigames.org
- ghostmap.verigames.org
- stormbound.verigames.org
Conflicts
If there are any test scenarios that conflict with the deployed staging website application, we will follow the staging website, not the scenario. It will be better if you confirm conflict in challenge forums.
Existing Documents
Test scenarios are provided in challenge forums.
Self Signed Certificate
We are using self-signed certificate in staging website, so some links will be blocked, i.e. you might get warning page that the website you are about to access is not safe, you need to accept that warning and proceed to website.
Chat and web sockets might be blocked as well, so you need to manually access the following links and accept the warning :
https://chat-statics.verigames.org
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.
- Members who submit duplicate reported bugs will lose 1 point/duplicate bug from their overall points.
- 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 :
- 4 points for functionality issue
- 2 points for UI and styling issue
- -1 point if you submit a duplicate issue
- -1 point for irrelevent and out-of-scope issue.
- The member who get most points will win first place prize plus $2 per point, 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 Format
For each report of a limitation or bug, we need the following information:
- Title must have a prefix tag with requirement name and case number. i.e. [Home Page][29] <title of bug>
- 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 and you will lose 1 point for each duplicate reported bug.
Ticket Logging
You will log your tickets here: https://apps.topcoder.com/bugs/browse/CSFV and when creating a bug you MUST select the "Https Bugs" 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 :
- 4 points for functionality issue
- 2 points for UI and styling issue
- For scoring, the submitter with the most accumlated points will win.
- All submitters will recieve $2 per point for each 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.