HP Service Test 11.50 Released


HP Service Test 11.5 Released

Lost in my excitement over the release of the highly anticipated UFT 11.50 last month, I failed to mention that Service Test 11.50 was also released.

I know. “WTF”, right?! You thought UFT 11.50 was supposed to be a new product that replaced both QTP and Service Test, essentially integrating both tools into the same user interface and renaming them to GUI and API test.

As it turns out, if you need just API testing, you can still purchase a standalone version of HP Service Test. GUI testing, however, does not have this option, so long time QTP engineers had better get used to the idea of using UFT going forward.

Service Test 11.50

I can’t say that Service Test 11.5 is a major upgrade from the previous version, at lease in my opinion, but it does include the following enhancements:

  • JSON Support – This is probably the biggest enhancement. Service Test now has the ability to test REST APIs and SAP systems that are JSON-based.
    • REST: Now you can test REST services that use JSON by generating JSON payloads and perform checkpoints on their response.
    • For SAP, you now have the ability to import IDocs and RFC definitions , issue RFC calls and add checkpoints.

  • Run Step – As I wrote in my post “Top 5 Features you are going to Love in UFT 11.5,” it may seem insignificant, but this feature is an absolutely killer enhancement that’s going to save me a lot of time. It will afford me (and you!) the ability to run any step on the canvas areas using the new “Run step” command.
  • Array Checkpoints – this feature adds advanced array checkpoint validation capabilities to Service Test, which will allow you to check whether or not an element exists in an array, and also verify that every element contains a specific value.

Some things to keep in mind as you migrate from Service Test or QTP to UFT:

  • Most of the existing documentation you may have for QuickTest Professional and HP service Test will still apply to Unified Functional Testing. So, if you purchased some of my favorite books() from last year, most of those examples should still work.
  • If you have previous QTP or ST licenses, they should still work with UFT (with some restrictions).
  • If you open a script in UFT 11.50 and make changes to it, it should still work with QTP 11.
ramu - November 8, 2013


I am facing one problem in HP Serv ice 11.5 . Can you please help me on this.

In my Project OFM middleware is using .
i am giving request to ofm getting response.but in response i am having array of elements and i want to store in excel , i have to compare with some other response.

Can you please help me on this.


itemdetails are repeating ie., an array

Please reply me as early as possible.


Akbar - January 18, 2015

Hi Joe,

I have just started doing my first API testing project . finished your book and start applying it , it’s a great resource , Thanks!
I have question about the error handling in API testing :
If we have successful service run we will get code 200:OK . What I am trying to achieve here is if one of my step did not pass I just wanna report and go next like we do in GUI , instead of just stopping test there since there is no dependency.
I am trying to access ExcutionStatus in custom code so that I could do some error handling , but never succeed .
Could you please explain how error handling work in API testing?

btw , big fan of your blog,podcast and book!


Click here to add a comment

Leave a comment: