UFT 12 was launched on March 20, 2014. This new version of UFT comes with a lot of new features and integrates all features that were incorporated for various patches of UFT 11.5. We will have a detailed look on all those features below.
UFT 12.00 comes with a new installation package, enabling you to install UFT more quickly and with greater security:
- The size of the installation package is 1.5 GB which is significantly smaller than in previous releases, speeding up the installation time.
- You can choose to install the UFT Add-in for ALM and the Run Results Viewer as part of the UFT installation.
- The installation process includes all of the configurations needed to run UFT. You no longer have to run additional post-installation programs.
- The installation is more secure, enabling you to install UFT without needing to temporarily disable the User Account Control (UAC) for your computer as was the case with UFT 11.5 and earlier versions of UFT/QTP on Windows Vista, Windows 7 and Windows 8.
- You can now install UFT in any supported language without the need to install a separate language pack in addition to the UFT product installation.
You can also perform a single silent installation without the need to run additional installations, including the following features:
- All installation prerequisites can be installed with a single command. (without the need to install each separately)
- All add-ins (including the ALM Add-in for UFT) installed with a single silent installation command and without the need to restart.
- All UFT configurations can be added to the silent installation commands.
- The silent installation can be run without administrator permissions.
For the first time ever in the history of QTP/UFT, HP has started to expand the testing capabilities of UFT beyond Windows. You can now run tests on Web applications on a Safari browser that is running on a remote Mac computer.
UFT 12 supports Safari 6.00 and 6.10 (on Mac OS Mountain Lion 10.8) and Safari 7.00 (on Mac OS Mavericks 10.9)
After you install the UFT Connection Agent (provided with the UFT installation) on your remote Mac computer, UFT can connect to the Mac computer remotely and run Web steps on the Safari browser.
Note that you must design the tests locally using a supported (Windows) browser, and that you can only run Web test object steps on the Safari browser. All other steps, including Utility object steps, such as SystemUtil.Run, run locally on the UFT computer.
Your ALM site administrator can now set a site parameter that instructs UFT to conditionally upload run results from a run session to ALM. You can set the parameter so that the results are always uploaded, or you can use site parameter arguments to specify the conditions for which the results will be uploaded.
Once this parameter is set, all projects on the site can use the parameter when running UFT tests. This feature is supported for ALM version 12.00.
UFT provides Business Process Testing from within UFT, using the native UFT user interface. This enables users to create, maintain, debug, and run BPT tests together with GUI and API tests, providing a single, one-stop-shop product for seamless functional testing.
Business process tests and flows are comprised of business components, which can be used to test specific parts of your application modularly. Business components include keyword GUI components, scripted GUI components, and API components.
If you are familiar with using BPT in ALM, you can use BPT in UFT as follows:
- Add components and flows to your tests and flows by dragging them from the Toolbox pane to the test or flow opened in the document pane.
- Manage component iterations in the Data pane.
- Link and promote parameters in the Component Parameters tab of the Properties pane. Use the other Properties pane tabs to view and modify various test, flow, component, or group details, such as descriptions, fields, and comments.
- Set parameter promotion options in the BPT Testing tab of the Options dialog box.
Using UFT, you can now run GUI tests as well as API tests that use a virtualized service. This enables you to run tests of your application using a service that would otherwise be inaccessible for test runs.
Using Service Virtualization, you design your virtualized service. Then, using UFT, you deploy the virtualized service on a Service Virtualization server. When the test runs, the application accesses the virtual service instead of the real service.
In addition, you can specify performance models for your virtualized service as well as different data models. In this manner, you can vary the responses and performance of your application and service to check its performance in a variety of different scenarios.
If you work with server-side execution using ALM Lab Management, you can now take advantage of the option to link the parameters of your GUI test to ALM AUT Environment parameters. The AUT Environment parameters are then used when running the tests using server-side execution.
In previous versions of UFT, AUT parameters were supported only for API tests.
What is server-side execution?
In server-side execution, you run tests on remote host machines at predefined times or on an ad-hoc basis, not requiring anyone to be logged in to the host to initiate and control the test runs.
When you work in integrated mode with SAP Solution Manager, you can use structure-type test parameters to pass complex values such as XML values or arrays from a Solution Manager test script to a GUI test, or vice versa.
You create and maintain the structured parameters in SAP Solution Manager. Then you can map action parameters to the structured parameters in your test. When you run your test, UFT receives parameter values from SAP Solution Manager; and resolves the mapped local parameter with the actual value from SAP Solution Manager.
The UFT automation object model also supports the new structure value type for test and action parameters. The UFT Add-in for SAP Solutions now supports SAP NetWeaver Business Client navigation objects.
To communicate with the Flex application during testing, UFT now selects an available port in the range 24654 – 24663 . This enables multiple Windows Server users to run UFT tests on Flex applications simultaneously without competing for use of the same port.
UFT can now use external authentication to connect to an ALM 12.00 server and project, instead of using the traditional model of entering the user name and password in the ALM Connection dialog box.
This enables users to use their installed external authentication certificates or single sign-on mechanisms instead of maintaining and remembering a separate user name and password for their ALM projects. If the ALM 12.00 server is configured to use an External Authentication system, such as CAC (Common Access Card) or SiteMinder, then UFT uses this authentication method when you open the ALM Connection dialog box.
A new RunDebug method is available in the Automation Object Model. This method instructs UFT to stop at breakpoints when running a test using automation, whether from ALM or in an automation run.
When you run a test that uses a virtualized service, you can now view the service’s details in the run results:
- The name of the service and location of the deployed service
- Deployment status of the service
- The performance and data models used in this test run-time agent mode
- The data simulation and performance simulation accuracy for the virtualized service in this test run.
- Testing Extensibility now supports Visual Studio 2010 and Visual Studio 2012.The sample applications have been updated:
- The Visual Studio 2003 samples were removed.
- New Visual Studio 2010 and Visual Studio 2012 versions of the QuickId and HoursReport samples are available.
- The new Testing Extensibility SDK includes new interfaces that enable you to:
- Add unrecorded steps to the test during a recording session.
- Add lines to a report during a run session. The report can be generic, or associated with a test object.
- Provide an image file for an active screen, instead of a rectangle
The Run Results Deletion tool is now incorporated into the Run Results Viewer. This enables you to automatically delete test results from tests and business process tests stored on ALM without needing to independently connect the Run Results Deletion tool to ALM.
The log setting options previously included in the ALM Remote Agent Settings dialog box were designed primarily to enable HP support engineers to generate logs during support calls. They are not needed for regular use. These options have been removed from the dialog box.
You can use the UFT Self Check Tool to see additional installation and configuration data for your UFT installation, including:
- Browser details
- UFT installation details
- UFT Add-in installation details
- UFT configuration settings
- SAP GUI installation details
- UFT tool dependencies information
You can define a shortcut key or key combination that stops the current recording session (for GUI tests only) or run operation, even if UFT is not in focus or is in hidden mode. In the Run Sessions pane in the Options dialog box (Tools > Options > General pane > Run Sessions node, click in the Stop command shortcut key field and then press the required key or key combination on the keyboard.
The default key combination is CTRL+ALT+F5.
- you open the application manually before you click Record or Run, the shortcut defined in the application is applied for its original purpose.
- you start a record or run session and UFT opens the application for you, the shortcut you define stops the session.
When working with an RDP connection, UFT can continue running GUI tests or (GUI-based) business process tests on a remote computer after you disconnect your local computer from it. Use this option to free up resources on your local computer so you can increase your overall productivity, or so you can close your computer and go home for the day, while UFT continues to run your test.
To enable this, configure the Allow UFT to continue running GUI or business process tests after disconnecting from an RDP computer option in the Run Sessions pane of the Options dialog box.
The Parameters pane of the Test Settings dialog box, in which GUI Test parameters were managed in previous versions of UFT and QuickTest, has been removed. You now perform all test parameter creation and maintenance operations for both GUI and API tests from the Parameters tab of the UFT Properties pane.
In previous versions of UFT, if you wanted to test Flex applications, you needed to first compile them specifically for testing. UFT 12 includes the UFT Flex Runtime Loader, which you can use to open most of your Flex applications for testing, without having to pre-compile the application.
You can use the new Flex tab in the Record and Run Settings dialog box to instruct UFT to open Flex applications at the beginning of a record or run session. In this tab, you specify whether you have prepared the application in advance for testing, or whether UFT should open the application using the Runtime Loader.
You can also configure the new Flex Record and Run settings using an automation script.
In addition to the Flex test object support that was introduced in 11.50, new test object methods and properties were added in UFT:
When using Insight to recognize objects, UFT searches for objects on your screen that match a stored test object image.
When modifying a test object’s image, you can now specify areas within the image that UFT ignores when searching for a match. This is useful if parts of an object do not always look the same. For example, if different icons are used on different operating systems to run a certain application.
The UFT Web Add-in now supports the following additional objects for HTML5 object recognition:
- WebAudio. Supports recognition of HTML audio objects.
- WebVideo. Supports recognition of HTML5 video objects.
- WebNumber. Supports recognition of HTML5 number objects. These objects may look like numeric edit boxes or up-down spin controls, depending on the browser.
- WebRange. Supports recognition of HTML5 range objects.
Previously, when calling an API test from a GUI test, you could view and set the run-time value only for the API test input parameters.
However, using the new RunAPITest method, you are able to see and use the output parameter and value of the output parameter from an API test in later steps of a GUI test. Thus, if the service (API) layer of your application returns a value that your application’s GUI then uses, you can easily and accurately test this instead of having to write complex functions to extract the information from the API test output.
The popular Save with Resources feature from QuickTest is now also available for GUI Tests in UFT.
It comes in handy if you need to open or run a test when you do not have access to a network drive or ALM. For example, you may need to create a portable copy of a test for use when traveling to other sites. Using the File > Save (Other) > Save with Resources command, you can save everything you need to a local drive or to another storage device .
When you use this option, UFT creates a copy of the test, its resource, and any external actions called by your test, and adjust the references from your test to the resources and external actions so that you can use them locally.
Standard VBScript provides the CreateObject function, which enables creating 32-bit COM object references. UFT has added the CreateObject64 statement, enabling you to create 64-bit COM object references.
The Action template and External Action Properties tab, which were available in QTP 11.00, but not yet available in UFT 11.50, are now available in UFT 12.
You may want to create an action template when you want to add the same element to each new action you create, such as the same comment, or the same ExecuteFile statement.
To create a new action template, create a text file containing all of the elements that you want to include in your template, and save it as ActionTemplate.mst, in the <UFT installation>\dat folder. The ActionTemplate.mst file must have the same structure and format as an action in the Editor.
External Action Properties
The External Action Properties tab enables you to specify the data source for the selected action. It is available only when viewing properties for external actions. The External Action tab provides the following options:
- Use data stored with the original action (read-only). Uses the original action’s data. If you select this option, the data is read-only when viewed from the calling test, and all changes to the original action’s data sheet apply when the action runs in the calling test.
- Use a local, editable copy. Uses an editable copy of the data in the test’s data table. If you select this option, a copy of the called action’s data sheet is added to the calling test’s data table and is independent of the original action.If the called action has parameterized steps that rely on new information in the original action’s data sheet, enter the relevant column names and required data to the action sheet in the calling test manually.
In UFT, you can map action parameters in you test to structured parameters defined in SAP Solution Manager. Now, UFT’s statement completion helps you use these structured parameters in your test by displaying the elements available in the structure.
If you type the name of a structured action parameter in a test step, followed by a colon (:), UFT displays the structure’s elements. If you type a structured parameter element, followed by a period (.), UFT displays the relevant sub-elements.
The InsightObject.Click method brings the Insight object’s parent test object into focus before performing the click.
In some cases, this change of focus may hide your Insight object in the application, making it impossible for UFT to find and click it. In those cases, you can use the new InsightObject.ClickSpecial method, which does not bring the parent test object into focus before clicking.
UFT 12 fully supports the .xlsx format of Excel files for importing data to the Data Table or when specifying an Excel file for use with ALM configurations.
When your test contains an unmapped repository parameter, the Errors pane displays the test name and path in the Item column.
You can now use the new Style/* notation to access the values of HTML5 CSS properties of Web-based objects.
For example, you could use the following programmatic description to identify all edit boxes on a page that had a red background color:
Set oDesc = Description.Create() oDesc("micclass").Value = "WebEdit" oDesc("style/background-color").Value = "rgb\(255, 0, 0\)"
New Supported HTML 5 Identification Properties for WebEdit
- pattern. The regular expression pattern defined for the edit box, which controls which values that the edit box will accept.
- placeholder. The hint text that is displayed in the edit box until a value is entered in it.
- required. Indicates whether the edit box must be populated before the form is submitted.
Mozilla Firefox only: A new method, DialogExists, is available for Browser test objects. The DialogExists method checks whether a dialog box is currently open in the browser. This can be useful before using the Browser.HandleDialog or Browser.GetDialogText methods.
UFT 12 supports IE 11, Firefox version till 24 and Chrome browser till v30. HP keeps on updating its support for various browsers using various patches it release from time to time. You can bookmark this page to keep yourself updated on the new patches.
You can check these step-by-step instructions to download and install UFT 12 on your machine.
Source: UFT ReadMe & Help Docs
If you want to keep track of further articles on UFT (QTP). I recommend you to subscribe by Email and have new UFT articles sent directly to your inbox.