Key Information

Register
Submit
The challenge is finished.

Challenge Overview

Background

Hewlett Packard has developed a set of JSON-based REST API’s which enable “Big Data”-type processing capabilities allowing developers to process information embedded in unstructured text and images in previously inaccessible formats.  This platform is called IDOL OnDemand and at this point is in the Early Access release phase, open for all Innovators to use.  

http://www.idolondemand.com

The HP IDOL September 2014 Bug Hunt Challenge

The HP IDOL Team recently released a set of updates and enhancements to the API's.  You can find the complete Change Log here.  

You will be testing the API's right on IDOL OnDemand site with the "try" functionality.   There isn't a formal test plan here.  You'll simply try valid combinations of the API parameters and various inputs to see if you generate expected results.  Alternatively, you can write JSON REST Queries in code to test the functionality but this is not required.   Please test the following API's:

Create Connector
Delete Connector
Retrieve Config    
Start Connector
Update Connector
Add to Text Index
Create Text Index
Delete Text Index
Delete from Text Index
Index Status
List Indexes
Entity Extraction

The HP IDOL OnDemand platform does have other API's available but the ones listed above are new to the public or have be enhanced in the most recent release.

Getting started up with IDOL OnDemand

Before you can use the API’s you’ll need to sign up for an IDOL OnDemand developer account:

http://www.idolondemand.com/signup.html

Please indicate that you heard about IDOL OnDemand through [topcoder] in the “How did you hear about IDOL OnDemand?” field:

Once your account has been verified you’ll be assigned a developer account and API Key that will allow you to make API calls.   Complete information about available IDOL OnDemand API’s can be found here: 

https://www.idolondemand.com/developer/apis

You’ll need to register for a developer account with HP in order to get access to additional Try functionality in the API console.  Use of the APIs is free and restricted to non-commercial use at this time. Commercial use and pricing will be announced in the near future.

Before you compete in an IDOL-related challenge on [topcoder] please create a topcoder-specific key in your IDOL OnDemand Account.  You can do this by Clicking on Account->API Keys from the developer home page.

Simply generate a new key and rename it to “topcoder” as shown above.   This should be the key that you use in [topcoder] challenge completion.  This will also give you visibility to Preview API’s which may not yet be in public release.  Employees and direct and indirect subcontractors of Hewlett-Packard Company and its subsidiaries and other affiliates (“HP”), and employees and direct and indirect subcontractors of HP’s partners (including TopCoder and its affiliates) are not eligible to participate in the challenge.

You should be all set!

Contest Guidelines

The guidelines for this contest are given below:

  • As issues are identified they need to be logged in JIRA.
  • Issues must include clear descriptions, test cases and steps to reproduce and expected vs. actual results in order to be counted.
  • First competitor to find an issue gets credit, duplicates will not be counted.
  • Reviewers will accept, reject or mark the issues as duplicate.
  • Please DO take a look at the reported bugs, duplicated bugs cost your work time and the reviewer's time.
  • Please focus on functional testing with the actual requests and responses to the the IDOL On Demand API's. We don't need bug reports on typos, spelling errors and any trivial issues like this, all such issues will be rejected and will not count

Important Notice:

You must also be the first person to report the issue and submit it while submission phase is open.  JIRA will allow you to file issues before and after the submission phase, but these will NOT be counted.

 

 



Final Submission Guidelines

Bug Report Format

For each report of a limitation or bug, we need the following information:

  • The issue name should start with the API Name (e.g. Entity Extraction:  Place entity did return expected results)
  • Steps to reproduce, including any needed information
  • Screen shots (if applicable)
  • Expected results after the bug is fixed
  • Current results, before the bug is fixed
  • Please log only one issue per JIRA ticket.

 Important Notice:

  • If you do not properly document your bug reports, they will likely be rejected due to lack of information or documentation. 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.

Ticket Logging

You will log your tickets here: https://apps.topcoder.com/bugs/browse/IDOLSeptBugHunt.  Please start the issue title with the name of the API.  (e.g. "Entity Extraction: Can't retreive person name from file") 

Scoring

  • For scoring, the submitter with the most accepted bugs will win. There's no second place winner.
  • For submitters who submit but don't take first or second, if they submit bugs that aren't covered in the first place submission, they will receive $5 for each unique bug reported up to a maximum of half the 1st place prize

 Important Notice:

If two submitters submit the same bug report, the submitter who submitted the report first into JIRA will get credit for the bug. The second submitter will not. 

Some of the tips helpful for the contest are:

  • Submitting what is obviously the same issue multiple times with small variations will only annoy the reviewer that has to sort through all the issues and will only count as one issue anyway. If it's less obvious if it is the same issue or not, use your best judgment and the reviewers will do the same.
  • Put an eye on the issues being submitted by other members to minimize the time you may be spending on duplicate efforts. Knowing what has already been reported will allow you to better focus your time on finding yet undiscovered issues.
  • Double check your steps to reproduce and test cases to make sure they are clear. Make sure your steps include creation of any necessary data.
  • 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.

REVIEW STYLE:

Final Review:

Community Review Board

Approval:

User Sign-Off

SHARE:

ID: 30045595