Framework Test Scenario Competition

Overview

The Client Cockpit application is an initiative to provide an entry point for TopCoder Customers to interact with the TopCoder Community directly. A registered TopCoder client will be able to launch and track projects, send/receive messages and monitor a variety of information sources via a customizable framework of widgets, which can be dragged and dropped into place in any order the customer wishes. 

This contest concerns (and is limited to) the framework governing the behavior of those widgets. It will use a set of given documentation to provide an inventory of test scenarios and detailed test cases to exercise those scenarios.  The deliverables of this competition (test inventory and detailed test scenarios) will be used in a future test implement competition. The materials needed to write these tests are:

• Application requirement specification (see attachment)
• Application use-case diagram (see attachment)
• Application design specification (see attachment)
• Application QA scenarios (see attachment)

Forums can be found here:http://forums.topcoder.com/?module=Category&categoryID=3007;

Deliverables 
This testing competition will provide the following deliverables:

• A full inventory of tests scenarios for the Framework Architecture portion of the application (extending and enhancing the list of scenarios already provided in QA documents the forum).  These should aim to cover all base, corner, and exceptional scenarios even if they are not specified already.
• A detailed step-by-step implementation plan for the test cases inventoried test in the above step (see Appendix A for sample).
  • Any automatable test should be noted (with technical notes if applicable).
  • All data needed for the test should be fully specified.
  • If a set of tests use the same data or setup, specify the rampup/setup needed for each set of tests.  Note that there will likely be a global rampup/setup steps applicable for all of the tests. You are not required to use the format used in the sample.  Use a consistent format of your choice that will be easily understandable by an implementation team.

Payment

TopCoder will compensate members with first and second place submissions that have scored at least 75.

Timeline
All submissions are required to be submitted by the end of Competition Phase.

Eligibility

You must be a TopCoder member, at least 18 years of age, meeting all of the membership requirements. In addition, you must fit into one of the following categories.
If you reside in the United States, you must be either: 

• A US Citizen
• A Lawful Permanent Resident of the US
• A temporary resident, asylee, refugee of the U.S., or have a lawfully issued work authorization card permitting unrestricted employment in the U.S.

If you do not reside in the United States:

• You must be authorized to perform services as an independent contractor. (Note: In most cases you will not need to do anything to become authorized)
  

Appendix A - Example Test Case Format

This is an example test case template.  Feel free to modify this template or change the approach completely (i.e. XML/YAML with XSL or a processing tool to create a readable document).

Appendix B - Example Scenario With Sample Data

2.7 Download Repository Item
2.7.1 Download Repository Item

Functional Test Case Numbers: <65 through 68 >

Precondition:

1. User navigates to the Catalog Repository main page Automatable: YesSetup: None. Scenario 1 (FTC 65, 67, 68 ) Steps:  # User selects all catalogs.
2. User clicks on "Development Language" Category
3. User clicks on "Java" Category
4. User clicks on "JDK 1.4" Category
5. User clicks on "Java File System Server 1.0" in the asset detail list section
6. "Download Now" button is available and enabled.
7. User clicks on the "Download Now" button. Sample Data:

   Field Name	Sample Value
   Catalog List Box	All Catalogs
   Browse Tree	Development Language
   Browse Tree	Java
   Browse Tree	JDK 1.4
   Asset Detail List	Java File System Server 1.0
   Download File	File_System_Server_1.0.jar	Expected Outcome:

8. The user is able to download the file. Scenario 2 (FTC 66 ) Steps:  # User selects all catalogs.
9. User clicks on "Development Language" Category
10. User clicks on ".NET" Category
11. User clicks on "C#" Category
12. User clicks on ".NET FTP Utility" in the asset detail list section
13. "Download Now" button is displayed but disabled. Sample Data:

    Field Name	Sample Value
    Catalog List Box	All Catalogs
    Browse Tree	Development Language
    Browse Tree	.NET
    Browse Tree	C#
    Asset Detail List	.NET FTP Utility
    Download File	null	Expected Outcome:

14. The user is not able to click on the download button as there is no file to download.