Key Information

Register
Submit
The challenge is finished.

Challenge Overview

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.

We hope you enjoy this contest and good luck!

Challenge Requirement

This challenge will update the CSFV Gaming Website User Test Scenario, it will include some additional test scenarios to ensure we have addressed everything recently updated in the verigames.com website. Note the following :

  • The Requirement Specification document may not cover all functionality we have in the website, so you need to use the live staging server you can playaround and fully understand how everything works.
  • The test scenarios are targeting bug hunters, the purpose is to force bug hunters to follow a well documented scenarios when testing the website GUI, functionality, performance .. etc so you need to replace the REQ column with a more clear guide to bug hunters as they should not refer to ARS to understand what the functionality the test scenario is referring to. It is preferred to place the functionality list at the top of the sheet, and use the numbering in REQ column, and also add NEW column with the URL of the target page to be tested in the scenario. (We provided some samples from past challenges in the challenge forums)
  • Chat, forums, wiki are out of scope of this challenge.

    (Note that additional functionality may be exposed during the requirements gathering process.)

This competition will define the test scenarios for the verigames website, the pages and functionality in scope (they are documented in the RS as well - but not everything) :

  • Home pages (Home, My Home and /games pages)
  • News and related pages
  • Header and all functionality exposed in it
  • Footer and all functionality exposed in it
  • Searching functionality and it's subpages
  • Public and Private User profile and all related subpages
  • Login
  • Register
  • Forget password
  • Reset password flow
  • Notifications
  • Subscribe to newsletter
  • CMS related pages (FAQ, about us, privacy policy, terms of use .. etc)
  • Contact Us
  • User Info popup
  • Everything else in ARS not mentioned here and any functionality you find during testing the live stage website that is not mentioned above or in ARS.

Tips for success:

  •  Asking questions early and getting feedback is very important for the success of this competition.
  • Raise questions if you feel anything is confusing, or if you have any questions on the provided documentation (Copilot and PM will be available to answer questions).

Contest Objective

The goal of this competition is to develop a quality assurance plan and test scenarios to ensure that the requirements are met and the application works correctly. The plan and scenarios should test the application requirements for both positive and negative cases.

You must prepare the plan and scenarios document by considering all pages/screens present in the staging website.

Test Type Descriptions

Only the following types of tests are in scope for the current contest. So please prepare the test scenarios document for the current application by considering the following tests.

  • Functional Test
  • Performance Test
  • Integration Test
  • GUI Test

Provided Resources

Live Staging website

The staging website http://www.verigames.org/

  • You will be prompted with a username/password dialog, the credentials will be posted in challenge forums
  • You can register new users
  • Request in forums to get admin access, it is better to have multiple accounts to test regular vs. admin features.
  • You are allowed to post and delete content in the website, it is staging and used mainly for testing.

Documentation Provided

The following documentation will be available in the contest forum:

  • ARS
  • Gaming Website User Test Scenario


Final Submission Guidelines

 

Submission Deliverables

Document Name Document Type                         Must be compatible with
Test Scenarios Document Word Document Microsoft Word
QA Plan Document Spread Sheet Microsoft Excel
     

 

Final Submission

  • Your final submission must contain a single .zip file with all the submission deliverables.
  • 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.

ELIGIBLE EVENTS:

2014 TopCoder(R) Open

REVIEW STYLE:

Final Review:

Community Review Board

Approval:

User Sign-Off

SHARE:

ID: 30043390