Challenge Overview
Project Overview:
The TopCoder Cockpit application is increasingly getting more usage and hosting more and more projects from different customers. Now TopCoder is going to add a new "Asset View" into new TopCoder Cockpit. Currently, everything in Cockpit is very focused on displaying and aggregating contest information within projects. However, it's very difficult for a user to access their latest deliverables and assets for the project.
The main goal is to have a central place for the cockpit project users to upload and manage assets / deliverables within a project. The assets / deliverables of a project can be any latest deliverables and assets produced by the contests of the project. They can also be any documents related to project that the customer wants to upload and share.
The benefits can be achieved by this project:
- Users has a central place to get the latest documents of a project so people always know where to get the latest version of the asset / deliverable. Now customers often say they have no idea how to find the latest version.
- The assets / deliverables can be included by the upcoming contests so there is no need to upload them to contest requirements specification again.
- The document versioning can help user to track the history of the documents.
This is an integration project, which provides a new module for the Cockpit Asset View and integrates into an existing application, namely the TopCoder cockpit.
Contest Scope:
We rhave completed two assembly contests to implement partial functionality of the Asset View page. The goal of this contest is to clearly identify and log all the defects/issues in the implemented assembly. This is the first on the series of upcoming similar contests.
The major difference in this bug hunt is the way of logging issues. We are using IBM's Jazz environment for change management of this project and hence would like to log the defects in that environment. Please carefully follow the details provided in software guidelines to make successful submissions.
Available Resource:
Source code of the assembly and its deployment guide are provided in the forum.
VMs will be provided for testing purpose.
Jazz Environment Setup:
- To get access, please request in forum. You will be provided with username and password for your own login.
VM Setup
- Please request your instance in a forum post.
- VM specific information is found here: http://www.topcoder.com/wiki/display/docs/VM+Image+2.5 and http://www.topcoder.com/wiki/display/projects/Cockpit%2CDirect+VM
- 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.
Logging Defects/Issues
- Once you get the username and password, go to: https://vhost1442.site1.compute.ihost.com/ccm/web/projects/TC-Cockpit%20Asset%20View%20(Change%20Management)#action=com.ibm.team.workitem.viewWelcome
- Enter your username and password. You should see a Welcome Work Items Page.
- Click on create a work item (1st option) to log the defect.
- On the defect page, fill the following details:
- Summary, Severity, and Filed Against ( Select the requirement against which the defect is filed)
- In the description, provide steps to reproduce the issue (include all necessary information), results before the fix and expected result after the fix.
- Attach screenshots wherever applicable.
Reference Resources:
- To access the cockpit asset requirement specification, go to: https://vhost1442.site1.compute.ihost.com/rm/web#action=com.ibm.rdm.web.pages.showArtifact&artifactURI=https%3A%2F%2Fvhost1442.site1.compute.ihost.com%2Frm%2Fresources%2F_UfO3MZ_lEeK3xo_kxU17YQ
- Enter the provided username and password. You should see the Requirement Index page.
- Navigate through the links to the specific requirments.
- To access the input resources and the details that were used in two assembly contests, go to:
Release Assembly - TopCoder Cockpit Asset View And Basic Upload
Release Assembly - TopCoder Cockpit Asset View Release 3 - Batch Operations and Multiple File Upload
Final Submission Guidelines
For scoring, the submitter with the most accepted bugs will win. The submitter with the second most accepted bugs will receive second place. For submitters who submit but don't take first or second, if they submit bugs that aren't covered in the first or second place submission, they will receive $10 for each unique bug reported up to a maximum of the 2nd place prize. If two submitters submit the same bug report, the submitter who submitted the report first into JIRA will get credit for the bug.
Please note that this is not conventional bug hunt where you need to post defects on JIRA. The posting is to be done in JAZZ environment as described above. Please properly fill up all requred defect details, they will likely be rejected due to lack of information. Also, make sure your bug reports are reasonably general. If you submit the same bug that is seen in multiple screens, for instance, you will likely only get credit for the original bug report. The others will all be closed as duplicates.
OR Submission:
You MUST submit a file with a list of your reported bugs into OR during the submission phase for review p