Wednesday, September 29, 2010

HP Quality Center (ALM 11.0) and REST

We are currently using Quality Center 9.2 and one of my goals for this year is to upgrade it to the latest version. While browsing through the What’s New documentation for version 11.0 (seems like it has been rebranded to Application Lifecycle Management, or ALM), I saw this line:

There are now ALM REST resources available. For details, see the HP ALM REST API Reference.

That to me is something that stood out from all the other features. Of course, from 9.2 there have been other great features added as well, like version control and flows in version 10 and Sprinter and others in 11. But being able to write clients using the REST API is a great feature and something that I definitely will be exploring once we have this version installed. I went through their REST API reference and as expected, it exposes all the entities in a RESTful way that would make it easier to write the clients in Java or any other language.

Related: a previous REST-related post


  1. I believe only the Premier edition of HPQC it ALM with the starter and Enterprise editions still called HPQC...

  2. How has your REST API come along? I'm interesting in sending results back to our QC system from various test harnesses that aren't able to interact with the COM API currently provided.

  3. @Kevin We ended up having to roll back to 9.2 because we were having too many issues with ALM 11.0, the most critical of which was not being able to run any automated tests that use BPT components. The issue is still open with HP since last 2 months.

  4. Any updates on ALM 11? We are planning to upgrade to ALM 11 this year, would appreciate your comments.


  5. @Anonymous HP fixed the issue in a patch and I think ALM 11 should be fairly stable now that it's been out for more than a year. We haven't had time to retry the upgrade but need to do that soon.

  6. Trying to use HP ALM 11.0 REST API here too. Unfortunately there are a few key issues stopping us and we're unable to get anything more than a half baked response from API. Useless. It's just crappy we have to use this product.