Release Assembly - CSFV Forums Frontend Revamp Part 2

Project Overview

This project, the CSFV Community Gaming website project will provide the web site infrastructure and integration of the games. This will be a web site that is available on the Internet, and also will be delivered in a form where the server and the games can be installed and used behind a firewall.

 

This challenge is to hunt bugs in the winning submission from Assembly - CSFV Forums Frontend Revamp Part 2 Challenge.

Competition Task Overview

The goal of this competition is to identify all issues in the pages and functionality of all requirements listed in the assembly spec page or for any clarifications/changes made in the challenge forums, you simply need to make sure all these are implemented and functioning properly :

• Specs http://community.topcoder.com/tc?module=ProjectDetail&pj=30041678
• Discussions related to the assembly challenge http://forums.topcoder.com/?module=Category&categoryID=22165

Things to test in this challenge :

• Functionality Issues (mainly functionality in the frontend)
• User Interface Issues - UI prototype is provided in the forums http://forums.topcoder.com/?module=Category&categoryID=21821

Testing

Winning submission is checked in github.com/topcoderinc in minisite1_forums_ux branch.

You are required to setup the application locally :

• Follow this page to setup the CSFV environment https://github.com/topcoderinc/csfv_frontend_module/wiki/Setup-Guide
• Setup test data :
  • Checkout test data generator https://github.com/topcoderinc/csfv_test_data_generator/tree/forums_ux (must be forums_ux branch)
  • run npm install
  • run node app.js
• Setup forums applicaion :
  • Checkout https://github.com/topcoderinc/csfv_minisite_frontend_module/tree/minisite1_forums_ux (must be minisite1_forums_ux branch)
  • update config/setting-dev.js (set cluster field to 0 as clustering not needed in dev environment)
  • Remove this line from config.js

     app.use(express.session({
                cookie: { domain: settings.main.cookieDomain}, <-- remove this line
                store: sessionStore,
                secret: chatConfig.sessionSecret,
                key: chatConfig.sessionKey
            }));

  • run npm install
  • run node app-theme-1.js
  • Open http://localhost:8901/ and start testing!

If you have any issues during setup, please post in challenge forums and Copilot/Winner will help you.

Documentation Provided

UI Prototype is provided in forums.

Github Code

The code is in http://www.github.com/topcoderinc if you don’t have access, please request it in the contest forums.
 

Browsers requirements

Latest browsers from chrome, firefox, and safari, and IE8+ browsers.

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.
• Issues will be classified via points system :
  • 4 points for functionality issue
  • 2 points for UI and styling issue
• The member who get most points will win first place prize plus $2 per point, others will get $2 per point.

Final Submission Guidelines

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

You will log your tickets here: https://apps.topcoder.com/bugs/browse/CSFV and when creating a bug you MUST select the "Assembly - CSFV Forums Frontend Revamp Part 2" Bugs will not be counted if a selection is not made.

Scoring

The Scoring guidelines followed for the contest are given below:

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.