Module Assembly - TopCoder NodeJS Open Bugs API

Project Overview

TopCoder and the TopCoder community have worked hard to get the platform to its currently level of maturity, but we're far from done. It's time to take the platform to the next level. TopCoder is going to start taking some steps to open up the platform API to the outside and community developers so they could incorporate it in their websites, applications or build their own applications (web, mobile or desktop).

The ultimate goal is to open up and build an "API" that is targeting all different type of audiences - Software and Studio Competitors, SRM/MM competitors, Copilots, Admins and TopCoder partners - each audience will have different interests and usages of the API, so it will be a huge project and we need to make sure that we are in the right direction from the beginning.

This contest is going to implement the Open Bugs API, which will return similar data as displayed on page - http://community.topcoder.com/tc?module=ViewActiveBugRaces

Competition Task Overview

Please raise questions as quick as you can, I am familiar with related database and code base, I can provide as much support as I can.

The updated code must still deploy and work on heroku - any submission which can't be deployed on heroku successfully will be failed in screening phase - primary reviewer must check this.

The implementation will base on the node.js version of TC platform API - https://github.com/cloudspokes/tc-api. Please follow the existing actionhero pattern for your development.

For this contest, you are expected to implement the Open Bugs API, by communicating with JIRA, and write tests.

Open Bugs API

This API is going to communicate with JIRA by soap, and retrieve the active bug races. We are using an old version of JIRA (4.1.2), so Restful API is not avaiable yet. We have to use soap to communicate with JIRA, and retrieve the data.

The API path will be 

/:apiVersion/bugs/{jiraProjectId}/{status}

Status is the staus of the ticket, it can be OPEN/CLOSED or ALL

jiraProjectId is the Jira Project ID, for instance BUGR. For now only BUGR will be supported

/:apiVersion/bugs/{jiraProjectId} - Assume status = OPEN

/:apiVersion/bugs - Assume jiraProjectId = BUGR, and status = OPEN

The data format will be like

[

{

  name: "CSFV - Convert Newsletter Email Template to MailChimp Template",

  JiraUrl: "https://apps.topcoder.com/bugs/browse/BUGR-10531",

  Payment: 200,

 TcoPoint: 20,

 StartDate: "01.23.2014 06:40 EST"

}

.....

]

Please investigate how to communicate the JIRA by soap, we have JiraRpcServiceWrapper which is used in TopCoder direct to communicate with JIRA server. You can learn from that.

If you are forbbiden to access the following link, please send request to subversion@topcoder.com for svn access.

You can also learn from the following

• Personal-Jira - Your personal Jira search
• node-soap - A SOAP client and server for node.js.
• You can use https://apps.topcoder.com/bugs/browse/Test to verify your implementation first, then you can test with https://apps.topcoder.com/bugs/browse/BUGR

Update API Doc

the apiary.apib  should be updated to show description for the Open Bugs API.

Standarize Query Naming Convension

we like to use the underscore approach in all SQL queries under the queries directory, please follow same approach.

Notes, for the JSON data returned, we will use camelCase approach.

Testing

The API Framework supports tests. Use supertest with mocha. Don't install mocha globally.

you must use mocha BDD style (which is the default), within that, you can optionally use chai.

Note: Tests must follow this standard - Tests Creation Guide.docx

Code Format

All code must pass jslint. You may use "nomen: true".

Winner Only

Winner will create pull request against the main github repo in final fix phase and help merge with master. The changed files should be unix style, you can use dos2unix command to convert it before commiting.

Reviewer Responsiblities

Reviewers need to write/update Supertest tests for the these APIs.

There are three roles:

• Accuracy - Tests the implementation on the accuracy of the results when using the component.
• Failure - Tests the implementation's ability to handle bad data and incorrect usage.
• Security - Tests the oauth, sql inject and other security related requirements.

Reviewer could send preferred role by Contact Manager after system selected the reviwer.

Copilot will assign the role to reviewers if reviewer didn't send the preferred role information.

Reviewer must create pull request from GitHub for the tests.

Virutal Machines (VMs)

VM specific information is found here: http://www.topcoder.com/wiki/display/docs/VM+Image+2.5

Upon registration as a submitter or reviewer you will need to request a VM based on the TopCoder systems image. The VM will be active through aggregation review, after which it will be terminated except for the winner's and the reviewers'. To request your image, please post in contest forum.

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.

Please realize that VMs are currently issued manually. We make every attempt to issue the VM as soon as it is requested, however, there may be delays of up to 12 hours depending on time of day when you request. We encourage everyone to request a VM as soon as possible to minimize any such delays.

Technology Overview

• JavaScript
• Node.js 0.10.x
• actionhero.js framework
• supertest
• mocha

Documentation Provided

Please check the deployment guide in codebase for reference.