Overview:

Welcome to "TC Direct Rebranding Bug Hunt 2" contest. topcoder Direct is the central place where client, topcoder PM and copilots used to manage projects developing within the topcoder. Recently, we've done with the rebranding work which reskin the Direct to match the look & feel of the brand new www.topcoder.com

In this bug hunt contest, you will quickly test the dashboard, admin and reporting related features to make sure nothing was missed and/or broken.

Contest Scope

Dashboard and Admin related pages requirements are described here: http://www.topcoder.com/challenge-details/30039553

• When testing, please make sure you check all the types of dashboards. There are some dashboard can only be accessed by certain roles, you need to add roles to the user account you use for login to test.
• When testing, please make sure you check all the types of admin features. There are some admin features can only be accessed by certain roles, you need to add roles to the user account you use for login to test.
• See the assembly challenge details on roles.

Reporting related pages requirements are described here: http://www.topcoder.com/challenge-details/30041084 Section B only

SVN Branch to use
Use the SVN Branch https://coder.topcoder.com/tcs/clients/cronos/applications/direct/branches/rebranding_R1 to test

Browser to Test

• Major browser like IE8+, FF 3.6+, Safari 5+, Chrome
• For Firefox, Safari and Chrome, we'd like to test on both windows and OSX (Mac) platform.

Format

1.    To test, a TopCoder VM which has the TopCoder Rebranding branch deployed is needed. Upon registration as a submitter you will need to request a VM based on the new TopCoder Direct image. To request your image, please use the forum.

VM specific information can be found here: http://apps.topcoder.com/wiki/display/projects/Direct+VM andhttp://www.topcoder.com/wiki/display/docs/VM+Image+2.5.

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.

2.    Documentation: For every issue found, you should following the format here http://apps.topcoder.com/wiki/display/tc/Bug+Hunt+Competitions+-+Issue+Report+Template

1) Steps to reproduce, including any needed information
2) Screenshots (if applicable)
3) Expected results after the bug is fixed
4) Current results, before the bug is fixed
5) Browser version

Besides that, it's better for you to provide the link on your VM for the issue you described.

Note that for all the typos and text related grammar errors found the in enterprise dashboard, you should document all of them in one ticket. We will use the ticket with most text errors found, if two tickets have the same number, we will use the first created one. So please make sure you don't create a single ticket for just one typo, otherwise the ticket will be considered as invalid.

3.    Document both positive and negative things you have found in the new enterprise dashboard. Make sure your issue reports are reasonably general. If you submit the same issue that is seen in multiple screens, for instance, you will likely only get credit for the original issue report. The others will all be closed as duplicates. You will log your issues here: https://apps.topcoder.com/bugs/browse/TDEDBH/component/13533 - Make sure the issues are put under component Rebranding #2

4.    Scoring, For scoring, the submitter with the most accepted bugs will win the prize. For submitters who submit but don't win, if they submit bugs that aren't covered in the first place submission, they will receive $5 for each unique bug reported up to $100 prize. 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.

Test Data

You can use the TopCoder System Test Data Generator to generate the test data. You can download the tool here TopCoderTestDataTool.7z

OR Submission

You MUST submit a file with a list of your reported bugs and all the test data you used to test into OR during the submission phase, for review purposes. If you do not do this, you will not get credit for any logged bugs! 

Final Submission Guidelines

Check the requirements section above.