Test automation with HP UFT 11.5: also for HP's R&D and IT

Remember, a month ago, when HP announced its new “HP Unified Functional Testing 11.5”? It may be hidden by all the products launched during HP Discover 2012 in Frankfurt, but this is actually big news. Big news for you if you are in the testing space, and big news for HP IT and R&D - the people behind the HP products and services.

 

HP QuickTest Pro and HP Service Test have gained quite a bit of popularity in trecent years amongst HP's development and test community. It is a fact that many HP products and services leverage QTP for their test automation. Service Test has also gained momentum in the area of headless testing (without user interfaces) for the many HP's SOAP and REST based web services. This is an important user base, they use QuickTest Pro and Service Test on a daily basis.

 

UFT: new log tracking

 

UFT 11.5 is no minor version change for HP's R&D and IT. First, test automation engineers will not have to install two tools because they are now unified. Also, the many enhancements and improvements (already described in Michael's blog) will definitely help write better automated tests, in a much easier way. From my standpoint, one of the most exciting feature sis image-based automation. It provides a nice complement to automated tests which use object-based recognition (which is reliable, but requires the technology to be supported by the test tool).

 

I'm not with those who suggest that image-based automation allows casual testers to create automated tests with much less scripting or coding knowledge. Instead, I am convinced that test automation requires first-class coding skills. But image-based test automation will certainly help in some of our most difficult scenarios. I do not want to forget about UFT's new development environment (IDE). Big improvements were requested in this area by many HP testers, and it looks like they have reasons to be happy with new editing and debugging capabilities; which are at par with other IDEs out there. My real favorite is the ability to add references to your test solution: you can benefit from any DLL or Library that would achieve a complex task and leverage it in your test script.

 

UFT IDE: Add references to your test solution

 

Being from the same mother ship, we (HP IT) work a lot with the HP Software team which creates UFT. Many HP internal developers and testers are actually design partners with HP Software and collaborate to create an even better UFT product. In fact, in addition to beta testing, I got my hands on the RTM (release to manufacturing) version of UFT 11.5 a month or so ago. Despite not having the time to do real work with it yet, I am very happy to see that it installed smoothly and that we did not have to upgrade our UFT license server. My internal customers – HP IT and R&D - will be able to benefit from UFT immediately.

 

Have a fruitful HP Discover, and let's take the opportunity to meet in one of my sessions "TB1076 - HP IT: Managing the application lifecycle across the enterprise" or "meet the expert" Tuesday or Wednesday. If you are not going to HP Discover, I'm on Twitter too: @ojacques2

Labels: automation| testing| UFT
Comments
| ‎02-13-2013 10:59 AM

 

| ‎02-14-2013 03:08 AM

Hello CPTLaura,

 

Thanks for your comment.

In my opinion, the decision to go with BPT (Business Process Testing) to link complex tests with API and GUI depends mainly on how your team is structure and how you work with your business partners or customers.

 

Team structure: the fact is that automated testing requires first class development skills. You really want your automated testers to be good developers. But testing often requires a different set of skills than development. With BPT, you can have business analysts or Subject Matter Experts (SME) create the tests - by re-using or defining BPT test components - which really make sense for the customer. Then, BPT gives you the framework within which the test automation team will automate those test components. It does not matter if some components are API or GUI tests: the business analysts or the SME will be able to pick from them anyway they want. This allows you to nicely separate - and scale - test case creation from test script creation.

 

Business partners: In some cases, you may have business partners or customers who are very involved in the testing process. For them, BPT allows them to create meaningful tests from existing test components, with a nice user interface. Then, the automation team can code the logic behind those components. Some components can be manual, some can be automated (GUI/API) - and they can all leave in the same "test". This is quite powerful, as business partners can create tests themselves which can all be eventually automated.

 

All that said, out of the box API & GUI tests integration in UFT could be the fastest path and provide the best return on your investment. But, if you have access to BPT or consider buying it, BPT could scale your test automation in a big way.

Leave a Comment

We encourage you to share your comments on this post. Comments are moderated and will be reviewed
and posted as promptly as possible during regular business hours

To ensure your comment is published, be sure to follow the Community Guidelines.

Be sure to enter a unique name. You can't reuse a name that's already in use.
Be sure to enter a unique email address. You can't reuse an email address that's already in use.
Type the characters you see in the picture above.Type the words you hear.
Search
About the Author
HP IT Distinguished Technologist. Tooling HP's R&D and IT for product development processes and tools.


Follow Us
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation