• Home  / 
  • ST
  •  /  Review of HP Service Test 11

Review of HP Service Test 11

Unlike QTP 11, Service Test 11 is a major upgrade from Service Test 9.53. HP is touting ST 11 as “an extensibility framework for construction and execution of functional test of headless systems that do not have a user interface.” Some of the notable changes:

  • Visual Test Designer — A canvas that creates and configures a visual representation of the steps in a test. Tests are created by dragging activities from a toolbox, and configuring their properties.
  • Multiple Technologies — Support for a variety of technologies such as Web Services, REST, .NET, Java, and more.
  • Flexible Data Handling — The ability to link to a variety of data sources, or store data locally with a test. Support for Excel data sheets.
  • Extensibility — The behavior of existing activities can be customized using event handlers. For greater control over the flow of a test, program code activities can be programmed at any point during a test.
  • My thoughts are that Service Test is no longer built on Loadrunner’s Vugen. Instead, it has been re-designed from the ground up, beginning with a new “modern” drag-and-drop user interface.

    Unlike QuickTest Pro, which uses wimpy VBScript, ST 11 uses C#, which is a full-blown, “real man’s” programming language. HP has even revamped the famous Mercury Tours web site sample to utilize web services.

    I have to be honest here — I’m personally on the fence about HP’s decision to move away from Vugen. I kind of liked having a one-script solution (LR) that used the same protocol for both functional and performance testing. ST 11 scripts can still be used for load tests, but since it uses C#, I’m not clear as to how scalable tests will be compared to the Vugen equivalent.

    I also like the ST 9.53 “business component” script functionality that could be integrated with Quality Center; ST 11 does not have this feature. So, it appears as though testers who have built up a large test suite of web service business components will be out of luck if they move forward with ST 11.00.

    In any case, I can see why HP decided to make the change. After working with the new version, I have to admit that it’s considerably more user friendly. QTP engineers will most likely need a minimal learning curve to get up to speed with it. QTP 11 has the ability to call ST 11 scripts, making it easier to do end-to-end testing of an application. I’ll need a little more time to evaluate the changes, but so far I say, “Well done, HP.”

    To see a video demo of HP Service Test 11 check out my post http://www.joecolantonio.com/?p=131

    68 comments
    Click here to add a comment

    Optin Architect