History has many cunning passages, contrived corridors and issues —T.S. ELIOT, Gerontion
UFT API Confusion
I just wanted to take some time to briefly go over the history of HP UFT API. One of the reasons UFT API testing can be a little confusing is that if you’ve done a little research on HP UFT API testing, or are trying to get started, you may not know where to start because of its history.
UFT API’s history
Understanding UFT API’s history, I think, will clear things up a little bit, so that you understand why you are seeing different versions and different technologies/names for UFT API testing.
Service Test VUGEN 9.x
Service Test 9.x (around 2009) was basically built on top of LoadRunner. Because of this, all development was done in the Virtual User Generator (VuGen), and tests could be run from VuGen for debugging purposes.
There also was a special VuGen interface designed to make testing web services easier.
Service Test 11
Around September of 2011, Service Test 11 was released. It was the first version that was built from the ground up utilizing SharpDevelop, and had a modern drag-and-drop user interface.
LoadRunner was no longer used. To distinguish between the two versions; HP began to refer to the older LoadRunner version as Service Test VUGEN, and the newer version as Service Test VTD.
In December of 2012, HP merged QuickTest Professional into the new user interface technology along with Service Test. QTP is now known as GUI Test, and Service Test is known as API test.
UFT 11.5 also includes new features that aren’t available in the previous version of QTP or Service Test.
Service Test 11.5
To make things even more confusing, there is still a standalone Service Test 11.5 that is strictly for API testing. This option is not available for GUI testing. So the functionality that you have in UFT 11.5 API Testing that is specific to API testing is also available in the standalone Service Test tool. Consequently, any information you may find in a book on API testing with UFT API (like my book The UFT API Manifesto) should still work in the standalone Service Test 11.5 version.
More UFT API Automation Awesomeness
For more UFT API Automation Awesomeness, tips, tricks and how-tos, check out my new book, The UFT API Testing Manifesto – A step-by-step, hands-on testing guide for the masses, available on Amazon.com!
Don’t own a Kindle? No Problem — you can still read my UFT API book!
I’m aware that some of you have had trouble accessing my books in the past. The truth is that you don’t need a Kindle! There are a variety of free ways you can read a Kindle eBook:
- Read it on your PC or Mac (Kindle Cloud Reader)
- Read it on your iPhone or iPad (iTunes App)
- Read it on your Android (Kindle for Android)
- Read it on your Blackberry (Kindle for Blackberry)
In short, it’s really simple to read Amazon Kindle books, no matter what type of device you use to access the Internet.