Challenge Overview
Project Overview
Previously, we have run a Release Assembly - Social Login Linking for Existing User contest, which allows existing user to link their social login account to their TopCoder accounts. So in the further, they can use their social account to login easily.
For initial stage, we are going to support 5 social providers, Google, Facebook, Twitter, Github and Salesforce.
The scope of this contest is to hunt bugs for adding or removing Social account with different state of the social accounts and in different browers.
Contest Objective
The goal of this competition is to clearly identify the limitations of current functionality for adding/removing social account . The testing of login using social account is out of scope yet.
The functionality is avaliable at My TopCoder page (http://community.topcoder.com/tc?module=MyHome). Don't use production environment for testing, please use VM instead.
Things to test in the current competition are:
- Register/Update the social account with different state, like missing emails, has many verified emails, missing username etc, then do testing with the adding/removing social account functionality.
- Test the adding/removing social account functionality with different browers, For UI Issues, The auth0 login widget and My TopCoder page are only in scope for this contest.
- Check with database, making sure the saved social account info is proper and precisely.
- the corresponding tables are user_social_login and social_login_provider tables under common_oltp database.
- You can directly login into the VM for database checking or use IBM Server Studio to connect the database, you can check http://apps.topcoder.com/wiki/display/docs/TopCoder+Databases+Setup+Guide for detail reference.
- test with different combinations, which you think is invalid, like associating one social account with different users, or different social accounts with same email linking to different user etc.
Browser Requirements
The given application must be tested in all mainstream browsers.
- IE 7+
- latest FireFox
- latest Chrome
- Safari on Mac
VMs
VMs will be assigned to each member.
VM specific information is found here: http://apps.topcoder.com/wiki/display/projects/Direct+VM and http://www.topcoder.com/wiki/display/docs/VM+Image+2.5.
Upon registration as a submitter or reviewer you will need to request a VM based on the new TopCoder Cockpit/Direct image. To request your image, please use the forum.
Before requesting your VM, you need to ensure that you have an SSH key created and in your member profile. Instructions to do so are here: http://www.topcoder.com/wiki/display/projects/Generate+SSH+Key, and instructions to connect afterwards are here: http://www.topcoder.com/wiki/display/projects/Connect+Using+SSH+Key.
Users
For VM environment, there is a preset of users to user, you can also register your own user account to test.
see Credentials for Website login section in http://www.topcoder.com/wiki/display/docs/VM+Image+2.5
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
Example:
- Java
- Auth0
- HTML
- Informix
Provided Resources
SVN
Example:
The following table summarizes the details about various SVN trunks needed for the current project.
| SVN | URL |
|---|---|
| TopCoder DB script | https://coder.topcoder.com/internal/database/scripts/trunk |
| TopCoder Website��� | https://coder.topcoder.com/internal/web_module/trunk |
SVN Request:
Please email support@topcoder.com to get read access to the SVN, include the SVN links, Contest title, and your handle.
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: https://apps.topcoder.com/bugs/browse/MDF2JBH and when creating a bug you MUST select the Linking Social Account component. Bugs will not be counted if a selection is not made.
Scoring
The Scoring guidelines followed for the contest are given below:
- For scoring, 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 $5 for each unique bug reported up to a maximum of the 2nd 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.
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 to the Online Review Tool.
- You must not include any identifying information, such as your handle, in your submission. Your submission should be anonymous and you will be scored down in screening for not complying.