HP Service Test 11.20 – Patch 9 Released

Service Test Patch Alert

HP just released a new patch (SOAST_00097) for Service Test 11.20. This patch includes many feature updates and multiple fixes for known issues.

What ST Features have been updated?

  • Updates to the ALM Integration
  • REST Service changes
  • The Web Service’s Call Activity
  • Changes to the Remote Agent
  • Checkpoints
  • Property Sheet

What’s been fixed?

If you are experiencing any of these issue hopefully patch 9 will solve them for you:

  • Modifying the design of a REST service, and solving the conflict in the steps, throws an error.
  • When windows account with read-only permissions over C:\Windows\System32 folder starts a Service-Test Test an error is thrown
  • Service Test not able to connect to QC through proxy with a long username
  • Structural Validation fails with error: “…element is not declared”
  • Service Test Not Sending “Cookie” RequestHeader
  • Possible project corruption with integration with Service Test 11.20


How to Get Patch 9

Due to HP’s legal department I can no longer post these patches on my web site as I explained in my post “Another reason why HP sucks“. To get a copy of Service Test Patch 9 you will need to contact HP Support or you can download it from HP’s Patches support site.

If you are not sure how to download patches from HP be sure to check out my Video How to download UFT/QTP Patches from HP”

Patty - July 21, 2014

I’m having the same trouble as “Service Test Not Sending “Cookie” RequestHeader” but on HP UFT 11.50 while buiding an API Test. Is this also a bug on HP UFT 11.50? I’ve tried looking for more information but your site is the only one that comes even close. Thanks!

    Joe Colantonio - July 21, 2014

    Hi Patty – I just dbl checked HP’s Knowledge Base and I don’t see any known issues with UFT 11.5 API and cookies. Do you get any errors?

Patty - July 22, 2014

Hi Joe, thanks for your reply. I don’t see any errors on the Run Results Viewer in terms of UFT failing to add the cookie header to the HTTP request. I am able to set other header fields such as “Set-Cookie” or “X-CSRF-TOKEN”, but not “Cookie”. Perhaps I’m going about the test the wrong way?

My API test has two HTTP requests on the Test Flow. The first request returns with a JSESSIONID and a CSRF token that I have to extract and then include in the second HTTP request headers so that the server knows these requests are all from the same session.

I’m learning UFT on my own (but am supposed to go on the introduction course next month) so I’m wondering if I’m doing the HTTP sessions correctly. I have tried using HTTP Receiver and placing the two HTTP requests inside it, but that didn’t work either. If these topics are covered in your book, please me know and I’ll be happy to purchase a copy. Thanks again.

Patty - July 23, 2014

Update: I updated my UFT 11.50 to UFT 11.53 (uft_00044.exe) and the “Cookie” header problem has been resolved. Thanks, Joe.

    Joe Colantonio - August 2, 2014

    Awesome news – sorry that is usually the first thing I ask people to make sure they have the latest patch version, especially with service test since the older version were really buggy.

Click here to add a comment

Leave a comment: