Challenge Overview
Overview
The CloudSpokes has its own contest types like First2Finish, Code etc. We have updated the Cockpit and Online Review to host these new contest types. In this bug hunt contest, you will verify in detail that whether the two new contest types are implemented as required and can be running without problem phase by phase. More important, we want to make sure the code change does not break the launch and hosting of existing contest types on Cockpit and Online Review. See the following section for details.
Bug Hunt Requirements
· Hunt the bugs of launch flow of new contest type First2Finish on Cockpit
· Hunt the bugs of launch flow of new contest type Code on Cockpit
· Move the created First2Finish contest phase by phase in Online Review and find out bugs of the following test cases
o Test the multiple submissions
o Test the iterative review
o Test the case when there is no passing submission at the end of the contest.
o Test the case when there is finally a passing submission and see if the contest ends automatically.
· Move the created Code contest phase by phase in Online Review and find out bugs
· The Finish2Finish only allows the 1st place prize to be set. The Code allows multiple prizes to be set (up to 5).
· Test other contest types of all 3 contest categories, especially the prize setting and change between contest types in the launch flow.
· Test different prize settings with different billing accounts to check whether the contest fee is calculated correctly, there are 3 types of contest fees
o Default contest fee in contestFees.xml will be used, if there is no setting for the billing account.
o Fixed contest fee setting for billing account
o Percentage contest fee setting for billing account
Reference
· Detailed Requirements of First2Finish contest type can be found in http://apps.topcoder.com/wiki/x/BQAbBw and http://apps.topcoder.com/wiki/x/D4CdBw
· Detailed Requirement of Code contest type can be found in http://apps.topcoder.com/wiki/x/gYCoBw
Browser to Test
· Major browser like IE8+, FF 3.6+, Safari 5+, Chrome
· For Firefox, Safari and Chrome, we'd like to test on both Windows and OSX platform.
Final Submission Guidelines
Bug Hunt Test Environments
VM Environment
We have deployed the latest Cockpit and Online Review on the VM: 54.243.20.215. Put this into your hosts file
54.243.20.215 cockpit.cloud.topcoder.com tcs.cloud.topcoder.com
Then you can access Cockpit via: https://cockpit.cloud.topcoder.com/direct/ , access Online Review via http://tcs.cloud.topcoder.com/review/
Guides on using the VM
· http://apps.topcoder.com/wiki/display/projects/Direct+VM
· http://apps.topcoder.com/wiki/display/docs/VM+Image+2.5
Local Deployment Environment
You can deploy the changes (attached to the contest forum) to local environment following the guides below
o http://apps.topcoder.com/wiki/display/docs/TopCoder+Databases+Setup+Guide
o http://apps.topcoder.com/wiki/display/docs/Online+Review+Setup+Guide
o http://apps.topcoder.com/wiki/display/docs/TC+Direct+Setup+Guide
Submission Requirements
Log issue in JIRA: https://apps.topcoder.com/bugs/browse/TDEDBH/component/13432
· Project is TopCoder Cockpit Bug Hunt
· Component is CloudSpokes Competitions Integration
For every issue found, you should following the format here http://apps.topcoder.com/wiki/display/tc/Bug+Hunt+Competitions+-+Issue+Report+Template
1) Steps to reproduce, including any needed information
2) Screenshots (if applicable)
3) Expected results, after the bug is fixed
4) Current results, before the bug is fixed
5) Browser version
Note that for all the typos and text related grammar errors found, you should document all of them in one ticket. We will use the ticket with most text errors found, if two tickets have the same number, we will use the first created one. So please make sure you don't create a single ticket for just one typo, otherwise the ticket will be considered as invalid.
Review
The submitter with the most accepted bugs will win. The submitter with the second most accepted bugs will receive second place. For submitters who submit but don't take first or second, if they submit bugs that aren't covered in the first or second place submission, they will receive $4 for each unique bug reported up to a maximum of the 2nd place prize. 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.