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 My Project widget. 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 (provided in forum)
- Application use-case diagram (provided in forum)
- Application design specification (provided in forum)
- Application QA scenarios (provided in forum; appendix to the QA plan document)
Forums can be found here:http://forums.topcoder.com/?module=Category&categoryID=3033
Deliverables
This testing competition will provide the following deliverables:
- A full inventory of tests scenarios for the My Project widget (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.
Registration
This competition will be conducted through the Online Review tool like a normal component competition. Register and submit at:
Timeline
All submissions are required to be submitted by the end of Competition Phase.
| Phase |
Start |
End |
Days |
| Registration Phase |
02.19.2008 04:00 PM |
02.22.2008 04:00 PM |
3 |
| Test Submission |
02.19.2008 04:00 PM |
02.25.2008 04:00 PM |
6 |
| Test Case Screening |
02.25.2008 04:00 PM |
02.26.2008 04:00 PM |
1 |
| Winner Selection |
|
03.04.2008 04:00 AM |
|
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 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).
| Test ID |
ID number corresponding to inventory document. |
| Name |
Requirement Name |
| Description |
Test description |
| Requirement |
X.Y - Requirement Name |
| Automatable |
Yes/No |
| Preconditions |
1.
2.
3. |
| Setup |
1.
2.
3.
(any data or configuration if applicable) |
| Action Steps |
1.
2.
3.
(include specific data needed in each step)
(also alternate steps if applicable) |
| Expected Results |
1.
2.
3. |
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:
- *# User navigates to the Catalog Repository main page Automatable: YesSetup: None. Scenario 1 (FTC 65, 67, 68 ) Steps: # User selects all catalogs.
- User clicks on "Development Language" Category
- User clicks on "Java" Category
- User clicks on "JDK 1.4" Category
- User clicks on "Java File System Server 1.0" in the asset detail list section
- "Download Now" button is available and enabled.
- 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: |
- The user is able to download the file. Scenario 2 (FTC 66 ) Steps: # User selects all catalogs.
- User clicks on "Development Language" Category
- User clicks on ".NET" Category
- User clicks on "C#" Category
- User clicks on ".NET FTP Utility" in the asset detail list section
- "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: |
- The user is not able to click on the download button as there is no file to download.
