Challenge Overview
Project Overview
Arena Applet is the main tool used for current Single Round Matches.Contest Objective
The goal of this competition is to clearly identify the limitations of the Arena Applet. it is expected to fully test the functionality.
Things to test in the current competetion are:
- please setup the following in your hosts file
- 54.174.228.90 qa.arena.topcoder.com
- You can download the latest arena applet from https://qa.arena.topcoder.com/clients/arena-qa.zip
- unzip it.
- change to qa.arena.topcoder.com in arena.sh or arena.bat files.
- It is a separate system, you are expected to setup your own account through http://tcqa1.topcoder.com
- Before logging issues, please do quick keyword search, make sure no similar issue reported. duplicate issues will not be considered as valid.
- Every 4 hours, a match will be setup for your testing, the first match will be avaliable at 12:00am Eastern time on Saturday
- Sample solutions are provided for your convience, you can revise the sample solution to reproduce every cases, like wrong input, exceptions etc.
- Any issue related to spelling and grammar will not be considered as valid issue.
Users
you are expected to setup your own account through http://tcqa1.topcoder.com
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.
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
- Screenshots or Screencast (if applicable)
- custom sample solution to reproduce the case.
- Expected results after the bug is fixed
- Current results, before the bug is fixed
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.