The last year has been an exciting one for Orasi, as we developed and debuted a comprehensive palette of solutions and services around streamlining software delivery — and the DevOps pipeline in particular. This spring, we had the opportunity to share the many insights we gleaned during our research and exploration in this area, beginning with Micro Focus Universe in Vienna and culminating with the ADM Summit in Chicago.
Continuous Testing Blog Posts
Over the past few weeks, I have been introducing Eye on Quality readers to some of the protocols for running LeanFT (UFT Pro) and UFT tests with Jenkins. (Learn more about both products at https://software.microfocus.com). Using Jenkins to execute your UFT and LeanFT tests is a great way to enhance your CICD pipeline. Today, I’ll share instructions for running LeanFT tests with Jenkins.
As a follow-on to our recent post about setting up Jenkins to execute tests built with Micro Focus UFT and LeanFT, this article will outline the process for running and viewing UFT tests in Micro Focus ALM. (See Running Test Sets from ALM on the Jenkins Wiki for additional information.)
Increasingly, I am seeing companies use Jenkins to execute tests for UFT and/or LeanFT, two automated testing tools from Micro Focus (formerly HPE) that can accelerate quality and release cycles compared to manual testing. This is a sensible approach, given that UFT and LeanFT, when run with Jenkins, can streamline the continuous integration/continuous delivery pipeline. (Learn more about both products at https://software.microfocus.com).
This post will show how to iterate through an XML response that has an array of items. This will use several UFT nodes that most people do not use normally. The system will use the sample Fight API tool to assist in demonstrating how to iterate an array, make conditions based on iterations of array, and count responses. This test will ask for all flights from London and Paris on a date. Then the response will be iterated and count all the flights for one of the airlines (“AA”).
In one of my automation engineer positions, I found that we needed to run the exact same tests in multiple different environments. Part of the process (documented here) involved passing parameters from ALM to UFT. In that article, I did not go into detail about how to set up UFT to accept and use the parameters. This article gives those details.