The Future of Testing Blog
Business innovation thrives with software innovation and quality matters now more than ever. Application teams are running to keep up with business demand by embracing the technologies and methodologies that will help them build faster with confidence to engage consumers, go mobile and release continuously. How does a modern testing team keep up? This blog will focus on the importance and role of the tester, the innovations in testing processes, test tools, test automation solutions and best practices and discuss how to balance speed with quality through Agile, mobile, web, composite and cloud application testing.

4 tips to improve the performance of your HP UFT tests

p2.pngHP Unified Functional Testing (UFT) and QuickTest Professional (QTP) have been integrated with HP Application Lifecycle Management (ALM) and Quality Center (QC) right from the beginning.  You can store your tests in ALM/QC, and when it’s time to run them, QTP/UFT downloads them from ALM.  There are a number of factors that affect the time that it takes to open and run these tests.


Continue reading to learn four tips that could help you significantly improve that time.


(This post was written by Amir Wigelman and Slavik Muravetskiy, from the UFT R&D Team, and Yossi Camjalli, from the Performance Center of Excellence Team)

New HP UFT Best Practices Document: "Cross-Browser Functional Testing Best Practices"


A new HP Unified Functional Testing best practices document has just been published, called "Cross-Browser Functional Testing Best Practices".  It provides concepts and guidelines for designing and executing functional tests that involve different browsers, and some best practices for developing portable cross-browser tests using HP Unified Functional Testing.


Continue reading for more information about this document.

3 new HP technical white papers on automated testing now available

Three new HP technical white papers on various aspects of automated testing are now available.  They are:


  • Building an Efficient Component-Based Test Automation Framework
  • Automated Testing and Continuous Integration
  • Getting Started with API Testing

Continue reading for links to the documents, and a brief summary of each one.

Register now for the R&D Expert Panel: Tips on accelerating test automation

lobb.jpgHear an HP R&D panel discussion on strategies for accelerating test automation. Get tips from the experts and learn more about HP Unified Functional Testing 11.5. Web Event on April 30th @ 10am PT/1pm ET/5pm GMT.  Click here to register now.


Continue reading to find out more about this event.

3 Reasons Why Functional Testing Must Change

38846_7318.jpegBy Phil Nguyen, HP Software Community Director


Haste is the enemy of quality. As IT organizations adopt new technologies and processes to speed up innovation, quality assurance can sometimes end up being seen as roadblocks. Here are three trends that are forcing QA organizations to evolve.

Multi - Layered Testing with 'Unified Functional Testing'

During the last few years SOA-based / distributed applications have become more and more common. Applications that were built as silo entities are today interconnected, integrated, sharing components and services. A modern business process can begin with a transaction request on a web application, connect to the billing system, register a new transaction on an ERP system, send an email notification through the exchange system and once all steps are verified go back to the web application to finish the process with a confirmation message. Modern End-to-end business processes not only span across multiple applications but also have rich and complex steps that are happening below the Graphical User Interface (GUI) within what is sometimes called the ‘business layer’ through API calls and data bases interfaces. The business layer can consist of web services, dll files and other GUI-less entities.

This means few potential changes for the modern QA teams.

The good news:

·         The testable interfaces have expanded and allow for more elaborated testing and root cause analysis.

·         While traditional Functional Testing is mostly done on the GUI layer, modern functional testing can leverage the business layer to test earlier in the process (while the GUI is not ready or stable yet) and find bugs earlier than what was possible before.

However this also brings new challenges:

·         Sharable components and services create dependencies between applications and projects that impact how QA reacts to change

·         Testing on the business layer requires new skill sets that the QA engineer needs to acquire such as understanding WSDL files and web services.

Although the majority of functional testing is still done on the GUI layer, I see more and more of our customers complementing it with ‘head-less’ testing on the business layer. This is done by acquiring new skill sets by the QA teams, or bringing the SOA testers under the same group as the GUI test automation. Whatever the choice is, the trend is clear – the two worlds of GUI and headless testing are slowly merging.

This merge impacts the testing methodologies. Many of our customers (including HP IT itself) have today test scenarios where they interact with the GUI and the business layer within the same test scenario. For example: the first step of a test would fetch some data via a web service or an API interface to a DB and this data would be used during the rest of the test scenario on the GUI layer. Sometimes there are multiple shifts from the GUI layer to the business layer within the same test scenario. We call this ‘Multi-Layered Testing’. All of these techniques open new frontiers to the QA and automation teams, allowing them to test more, test earlier, enhance coverage and find bugs easily that were very hard to find before. However, all enterprise test tools of today (manual and automated) address either the GUI layer or the business layer. This does not allow the QA to perform multi-layered test scenarios and creates a separation between the testing methodologies of GUI and headless.

In order to address this challenge we in HP decided an integrated test automation solution that can address GUI and headless testing, is needed. Our current plans and what we are currently looking into is leveraging QuickTest Pro (the leading test automation tool in the world today) and integrating it with the innovative HP Service Test (HP’s tool dedicated for testing services). The integrated package will allow unifying the testing capabilities of both stand-alone functional testing tools, enabling multi-layered testing with both tools within the same test scenario like never before. We will call the package Unified Functional Testing (UFT).

Stay tuned for more about UFT in future posts to come. The more we speak with our customers about the UFT direction, the more use cases for it we see.

If you experience some of the multi layered testing challenges written above, I’d love to hear from you – feel free to comment below and I will follow up on anything interesting.

Roi Carmel

Showing results for 
Search instead for 
Do you mean 
About the Author(s)
  • This account is for guest bloggers. The blog post will identify the blogger.
  • Malcolm is a functional architect, focusing on best practices and methodologies across the software development lifecycle.
  • Michael Deady is a Pr. Consultant & Solution Architect for HP Professional Service and HP's ALM Evangelist for IT Experts Community. He specializes in software development, testing, and security. He also loves science fiction movies and anything to do with Texas.
  • HP IT Distinguished Technologist. Tooling HP's R&D and IT for product development processes and tools.
  • WW Sr Product Marketing Manager for HP ITPS VP of Apps & HP Load Runner
HP Blog

HP Software Solutions Blog


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.