Challenge Overview
Project Overview
TopCoder is implementing a Web-based Arena by using Web Socket protocol, AngularJS Framework (http://angularjs.org, http://docs.angularjs.org/guide) and Bootstrap 3 (http://getbootstrap.com/getting-started).
The frontend application is using AngularJS Framework (http://angularjs.org, http://docs.angularjs.org/guide) and Bootstrap 3 (http://getbootstrap.com/getting-started), and using web socket protocol to exchange data with backend web socket listener.
The backend web socket listener is ready for exchanging messages over web socket protocol.
Contest Objective
The goal of this competition is to clearly identify the limitations of the Challenges and Challengers Feature by the web arena in different browsers.
Things to test in the current competetion are:
Notes, you are expected to use my server and setup your own data, the backend listeners will be provided by allocating an Arena VM for each competitor.
- You are expected to test the Challenges and Challengers Feature, only issues related to this will be considered valid.
- Challenges and Challengers Feature in Division X page are out of scope.
- Please do challenges in web arena and arena applet randomly to see if there is any problem.
- Visit by different roles, like competitors, admins and guest ( not SRM registrants) to see the results
- Verify the page layout in different browsers
- Existing issues should not be reported again, please check
- TC - Web Based Arena - TopCoder Issue Tracker
- Bug Hunts for Web Based Arena - TopCoder Issue Tracker
- github issue tracker
Browser Requirements
The given application must be tested in all mainstream browsers.
- IE10
- IE11
- Latest Safari
- Latest Firefox
- Latest Chrome
Users
There is a pre-defined list of users, you can see VM Image 2.5 - TopCoder Wiki
Arena VM
You are expected to have your own VM to setup different data for testing.
Before asking your own VM, you need to have a public key on your profile before asking for the VM.
You can find more details on how to generate a key http://apps.topcoder.com/wiki/display/projects/Generate+SSH+Key and how to connect using it http://apps.topcoder.com/wiki/display/projects/Connect+Using+SSH+Key.
To use the Arena VM, please follow http://apps.topcoder.com/wiki/display/docs/Competition+Engine+VM+Setup
Web Arena Setup
Use the one common server I setup for you all. Just use different Arena VM.
107.170.118.6 arena.cloud.topcoder.com
If you want to setup by yourself.
You are expected to have Linux env for setup, you can check https://github.com/cloudspokes/arena-web. an export version will be attached in forum since you may don't have access to it.
For setup, please check the README.md file.
It seems possible to setup in Windows 7, based on some competitors' submission, but we didn't have a clear guide now. You can try then.
SRM Problem Guide
The SRM Problem Guide will be attached in forum, so you can easily follow to setup different data.
Contest Guidelines
The guidelines for this contest are given below:
- As issues are identified they need to be logged in github issue tracker.
- Issues must include clear descriptions, test cases and steps to reproduce and expected vs. actual results in order to be counted.
- Please provide screenshots, beside browser info, and screen resolution etc.
- First competitor to find an issue gets credit, duplicates will not be counted.
- Reviewer 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.
Important Notice:
You must also be the first person to report the issue and submit it while submission phase is open. any issues before and after the submission phase will NOT be counted.
How to Setup
Please edit your hosts file and add the following entries.
<<your arena vm>> tc.cloud.topcoder.com
<<your ip or my server>> arena.cloud.topcoder.com
Then you can visit in browser by http://arena.cloud.topcoder.com:3000
Additional Resources
Some of the additional resources helpful for the project are
Contest Prize Eligibility
The submitter with the most accepted bugs will win the contest.
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: Github Issues.
Scoring
The Scoring guidelines followed for the contest are given below:
- For scoring, the submitter with the most accepted bugs will win.
- For submitters who submit but don't take first placement, if they submit bugs that aren't covered in the first place submission, they will receive $5 for each unique bug reported up to a maximum of the 1st place prize.
Important Notice:
If two submitters submit the same bug report, the submitter who submitted the report first into Github Issues 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 Github Issues. Please submit a text file contains the bugs you reported to OR.