Challenge Overview
Project Overview
Marathon Match Web Interface is the website used mainly for Marathon Matches.Contest Objective
The goal of this competition is to clearly identify the limitations of the Marathon Match Web Interface. it is expected to fully test the functionality.
Things to test in the current competition are:
- you are expected to test against https://qa.arena.topcoder.com/longcontest/?module=ViewActiveContests
- It is a separate system, you are expected to setup your own account through http://tcqa1.topcoder.com
- Please use 14.10 Release QA MM - 14.10 Release QA for testing.
- Sample solutions are provided for your convenience, 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.
- Beside the general tests, following are the regression test scenarios. You can find Regression scenarios here Only Test Cases starting with LongContest : are in scope.
-
So here are few things to consider :
a) For issue found specific to the functional stories mentioned above, please include Story # in the issue name and mentioned issue link (github) in the "ISSUE NAME/LINK" column mentioned in spreadsheet.
b) For general issues, just post issues in github.
c) For regression test plan - Any member who fill up the sheet and return it to us gets a $100.00 bonus, If you are just providing a dummy sheet with some fill up, you will not get this bonus (Copilot and PM will judge that, so please fill the sheet properly with your testing steps)
- d) Any issues found while doing the tests for the sheet can be logged in github, and will be paid just like any other issues.
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
- Screen shots (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.