Challenge Overview
Project Overview
The community site is the portal for all topcoder members to find news, challenges, member profiles, etc... We keep making changes and enhancements to this site to make it better.
Contest Objective
The purpose of this bug hunt is to test some new features we built for the community site:
- We added new features (profiles and dashboard) to the site and we need these tested
- Please make sure you check the detailed feature documentation we posted in the forum so you can thoroughly test the site
- Although our main focus is to have the testing for Profile/Edit profile/Dashboard features but if you see the issues during registration/login also, you can report them too.
- Please do NOT report issues already in the known issues list.
- Please focus on functionality test
- Please test this on various browsers
- Screenshots are mandatory for this bug hunt, any bug report without screenshot will be rejected.
For more details you should check the documents we post in the forum.
Browser Requirements
The given application must be tested in all mainstream browsers:
- Firefox latest on Windows / Mac
- Safari latest on Windows / Mac
- iPhone 5 and above
- Chrome can be used as secondary browser but Firefox and Safari are the primary ones
- Testing on IE is not in scope
Users
You should use your own handle to test this.
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.
- 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.
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.
Technologies
- Wordpress
- Javascript
Provided Resources
Documentation Provided
- Requirements documents
Contest Prize Eligibility
The submitter with the most accepted bugs will win the contest. The submitter with 2nd most accepted bugs will get 2nd place prize (half of the 1st place prize).
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 (REQUIRED), if you don't provide a screenshot your ticket may be rejected
- 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: https://apps.topcoder.com/bugs/browse/TCAPP
Scoring
The Scoring guidelines followed for the contest are given below:
- For scoring, the submitter with the most accepted bugs will win and the submitter with 2nd most accepted bug will win 2nd place.
- For submitters who submit but don't take top two, 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 half of the 1st place prize.
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.
- Do not report trivial issues like typo / grammar issues / color issues / etc... these will all be rejected
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 via the challenge detail page on topcoder.com.
- You must not include any identifying information, such as your handle, in your submission. Your submission should be anonymous