HP LeanFT Readme

Software Version: 12.52

Document Release Date: January 25, 2016

Software Release Date: January 2016

This file provides the following information about LeanFT 12.52:

• What's New in LeanFT 12.52

• Minimum and Recommended System Requirements and Supported Environments

• Installing LeanFT 12.52

• LeanFT Help Center

• Notes and Limitations

• Security Information

• HP Support

• Legal Notices

What's New in LeanFT 12.52

LeanFT now offers the following major new features:

• Application models are now supported in Eclipse

• Checkpoint-style verifications for values and images

• Object identification configuration

• New Settings dialog box for runtime engine preferences

• Call UFT API Tests

• Data-drive your LeanFT tests from ALM

• Microsoft Edge support (technology preview)

• JavaScript SDK (technology preview)

For details on these new features and for information on additional new functionality and enhancements, see http://leanft-help.saas.hpe.com/en/12.52/HelpCenter/Content/HelpCenterRoot/WhatsNew.htm in the LeanFT Help Center.

Minimum and Recommended System Requirements and Supported Environments

This section includes:

• Minimum System Requirements. To successfully install and run LeanFT, your computer must at least meet these requirements.
• Recommended System Requirements. Performance may be improved by using systems with these stronger/later setups.

For a complete list of all supported operating systems, browsers, and development environments, see the LeanFT Product Availability Matrix (requires an HP Passport).

Installing LeanFT 12.52

To install LeanFT manually, follow the instructions below.

For details on silent installation, see Installing LeanFT Silently.

1. Prerequisites:

   • Make sure your computer meets the system requirements.

   • If you plan to use the LeanFT IDE plugin, make sure the relevant IDE is already installed.

     For supported IDE versions, see the LeanFT Product Availability Matrix (requires an HP Passport).

   • Make sure you have the required permissions on the computer.

2. Run the LeanFT installation and follow on-screen instructions.  While you install, consider the following:

   • In the Custom Setup screen:

     • LeanFT runtime engine only. Select for computers where you plan to run existing LeanFT tests.

     • Full installation. Select for computers where you plan to develop and run LeanFT tests.

       • If you select the Eclipse IDE, a path field is displayed.  Click the Change button to browse to the folder where your Eclipse IDE is deployed.
       • When the full installation is complete, a new LeanFT menu is added to Visual Studio and/or Eclipse and new LeanFT project templates are available in the IDE.
       • If you select Full installation, but do not select any IDEs for the LeanFT plugin, the Java and .NET versions of the LeanFT SDK are still installed in <LeanFT installation>\SDK
3. If you plan to test Web-based applications, open your browser and make sure the HP Functional Testing Agent extension is enabled. For additional details, see the topic on setting up Web browsers in the LeanFT Help Center.

4. If you plan to run LeanFT tests from ALM on your computer:

   1. Set the required DCOM permissions for the Remote Agent and open the DCOM port (port 153): 

      Open the command line and run <LeanFT installation>\Tools\Remote Agent\LFTDcomPermissions.exe -set.

      Caution: Configuring these DCOM settings may expose the LeanFT computer to security risks.

   2. Configure the Remote Agent to allow ALM to run tests on your computer: 

      In <LeanFT installation>\Tools\RemoteAgent\LFTRemoteAgent.exe.config, change <remoteAgent allowRun> to true.

      Note: There are additional values that must be set in LFTRemoteAgent.exe.config before you run LeanFT tests from ALM.  For details, see Run LeanFT tests from ALM in the LeanFT Help Center.

5. If you plan to work with the JavaScript SDK (technology preview), you must run a command line to add the SDK to your node testing module. For details, see Working with the JavaScript SDK in the LeanFT Help Center.

Additional Installation Information

This section includes:

• Enterprise Deployment
• Installing LeanFT Silently
• Setting Required Access Permissions

Enterprise Deployment

When installing LeanFT in an enterprise business model across many computers in a network or company, note the following:

Installing LeanFT Silently

A silent installation (or quiet installation) is an installation that is performed in the background. You can install LeanFT silently on your computer or on a remote computer.

You must have administrator privileges to run the silent installation.

To install the default full installation silently:

<extracted setup folder>\setup.exe /s

You can also append any of the following options:

• Specify a Functional Testing concurrent license server: LICSVR=<server name or IP>

• Specify specific components to install: ADDLOCAL = <component name>, where <component name> is one or more of the following, separated by commas:

  • LeanFT runtime engine: LeanFT_Engine

  • LeanFTClient (SDK): LeanFT_Client
  • Visual Studio 2012, 2013, 2015 Plugin: RegVS2012, RegVS2013, RegVS2015
  • Eclipse Plugin and location: RegEclipse ECLIPSE_INSTALLDIR=<path>

Example:

The following command installs the LeanFT runtime engine, client, and installs the LeanFT plug-in on Visual Studio 2012 and on the Eclipse IDE in the specified folder:

When you use the setup.exe /s command, there is no visual indication of the installation progress. To verify completion, monitor the process in the Windows Task Manager or check the installation log file.

Alternatively, you can use any of the following to install specific elements of the installation silently.

When you use msiexec /qb as shown for the UFT below, a progress bar displays during the installation.

Setting Required Access Permissions

Make sure the following access permissions are set to run LeanFT .

Permissions Required When Working with LeanFT

You must have the following file system permissions:

• Full read and write permissions to the C:\Temp folder

• Read permissions to the Windows folder and to the System folder

• Full read and write permissions to the folder on which you are saving solutions, tests, or run results
• If you are working on Windows 7 or Windows Server 2008 operating systems: Full read and write permissions to the <Program Data>\HP folder
• Full read and write permissions to the User Profile folders
• Full read and write permissions to the <Windows>\mercury.ini file

• Full read and write permissions to: %appdata%\Hewlett-Packard\

  Note: Read/write permissions to these folders should also enable permission to any subfolders contained in the folders listed above. If not, the system administrator must grant administrative permissions to the subfolders contained in these folders.

You must have the following registry key permissions:

Permissions Required When Working with ALM

You must have the following permissions to use LeanFT with ALM:

LeanFT Help Center

The LeanFT Help Center teaches you how to use LeanFT to create and run C# or Java-based LeanFT tests and provides the LeanFT .NET and Java SDK References.

Access the LeanFT Help Center at: http://leanft-help.saas.hpe.com/en/12.52/HelpCenter/Default.htm.

Notes and Limitations

This section includes important notes, known issues, and limitations that are relevant for LeanFT version 12.52.

This section includes:

• Backward Compatibility
• Plugins
• Web Technology
• Mobile Technology
• .NET Windows Forms and WPF Technologies
• Standard Windows Technology
• SAP UI5 Technology
• What's New in LeanFT 12.52

Backward Compatibility

12.50. The following changes may be required to tests that were created in LeanFT 12.50: 

• WPF. The WPF Slider.Value (C#) and Slider.getValue (Java) statements from LeanFT 12.50 are obsolete.  They have been replaced with: WPFSlider.Position (C#) and WPFSlider.getPosition (Java).
  If you have tests that used this obsolete property or method, you must modify those tests to use the new name.
  

• SAP UI5.

  • The names of the following SAPUI5 test objects were changed as follows:

    • IToolbar (C#) and Toolbar (Java) were renamed to IToolBar (C#) and ToolBar (Java)

    • ITextEdit (C#) and TextEdit (Java) were renamed to IEditField (C#) and EditField (Java)

    • ITree (C#) and Tree (Java) were renamed to ITreeView (C#) and TreeView (Java)

  • In the SAPUI5 Calendar and TextEdit (now renamed to EditField) objects, the Name property (C#) and getName method (Java)  were renamed to Title property (C#) and getTitle method (Java).
    

  If you have tests that used these obsolete test objects, properties, or methods, you must modify those tests to use the new names.
  Additionally, if you have SAPUI5 test objects in your existing application models that use the obsolete type names, you must update those application models to use the new names.

12.51. The following changes may be required to tests created in LeanFT 12.51: 

• The SwipeDirection enumeration moved from the Mobile namespace/package to the SDK namespace/package. If you have any tests that explicitly reference ...SDK.Mobile.SwipeDirection, you need to adjust those tests for the new location.

Plugins

General

• When using the Highlight option in the application model for a test object with VRI objects defined, the highlight operation succeeds only if exactly one object matches the description (including the VRI definitions). If multiple objects match, nothing is highlighted.

  Workaround: Use the VRI Preview option to check the description.

Eclipse

• To use the Eclipse IDE for Java EE Developers or Eclipse Standard editions with the LeanFT plugin, you must deploy the Google Gson plugin to your Eclipse folder:

  1. Download the Google Gson plugin, version 2.1 or later, from maven central repository.

  2. Copy the downloaded .jar file to your <Eclipse deployment>\plugins folder and reopen Eclipse.

Visual Studio

• If you have an application model open in Visual Studio with changes that have not been saved, the generated code is updated with the unsaved changes. If you close the unsaved application model in Visual Studio without saving, the generated code will not be reverted back to the last saved application model.

  Additionally, if you have an application model open in Visual Studio with saved changes, but then edit and save the file outside Visual Studio, even after you confirm reloading the .tsrx file in Visual Studio, the generated code for the application model is not updated with the external changes.

  Workaround: Build the project containing the application model or close and reopen the application model.

• Web-based AUTs only. If your IDE is in front of your browser when you click the Highlight option from the Application Model editor or from the Object Identification Center, the Highlight rectangle appears, but sometimes the IDE window stays in focus and may block the object.

  Workaround: Arrange your screen so that the IDE does not block your application.

Web Technology

• The FireEvent OnBlur event is not supported in Chrome.

• When using Internet Explorer 11 on a computer with UAC enabled: If a step in the test navigates from a permitted zone to a non-permitted zone, the navigation step succeeds, but any subsequent step will fail.

• If a Chrome browser is open and has an alert message box displayed prior to the start of a LeanFT test run, you must manually close the message box before starting the run.
• In some cases, the Attributes collection returned by Attributes property (C#) or getAttributes (Java) may be different between Internet Explorer and other browsers such as Chrome or Firefox.

• If you perform a step that navigates to a new page immediately followed by an image capture operation such as OCR operations, image verifications or comparisons (VerifyImageMatch, VerifyImageExists, CompareImage, LocateImage) or the GetSnapshot method, the step may fail.

  Workaround: Add a browser.Sync() step before your image capture operation.

• If the SAPUI5 add-in is loaded (selected in the add-ins list of the Engine tab of the Settings dialog box), LeanFT cannot recognize Web TreeView, Menu, or TabStrip test object types.

Microsoft Edge

• LeanFT can work with Microsoft Edge browser only when launched with the Edge Agent for Functional Testing (Start > All apps > HP Software > Edge Agent for Functional Testing or using a BrowserFactory.Launch step to launch the Edge browser).

• You cannot open more than one instance of the Edge browser. This includes multiple BrowserFactory.Launch methods without closing the previous instances, or other methods that create a new browser instance such as Browser.OpenNewTab

• You cannot spy on or run steps on Frameor iFrame objects, or any elements inside these objects, using Microsoft Edge.

• The following methods are not supported in Microsoft Edge:

  • FullScreen()

  • DeleteCookies()

  • File.SetValue()

Mobile Technology

For notes and limitations related to the LeanFT-Mobile Center integration, see Considerations and Limitations in the Mobile Center 1.52 Help.

.NET Windows Forms and WPF Technologies

• You cannot use Items, SelectedItem, or SelectedItems C# properties, or the corresponding getItems, getSelectedItem, getSelectedItems methods in Java to create the test object descriptions of WPF ComboBox or WPF List test objects.
• LeanFT cannot identify a WinForms Button test object if WindowId is the only property in its test object description.
• Before performing a Select operation on a WinForms edit object, you must first perform a Click operation on it.

Standard Windows Technology

• The ListViewItem.EnableLabelEditing method works only if it is preceded by an ActivateItem step.

SAP UI5 Technology

• When spying on a SAPUI5 list box, the Object Identification Center displays the control type as "Unknown".

Security Information

LeanFT can potentially be used to simulate user actions on the host machine via the network. Therefore, it is strongly recommended to run LeanFT on dedicated test machines that do not contain or provide access to sensitive information. In addition, you should also thoroughly review your lab network topology and access permissions before using LeanFT.

For additional security information about LeanFT, see the LeanFT 12.52 Security Reference, available in the <LeanFT installation>\help folder after you install LeanFT or download the latest version from the HP Software Support site (requires an HP Passport).

HP Support

You can visit the HP Software Support web site at: https://softwaresupport.hp.com

This web site provides contact information and details about the products, services, and support that HP Software offers.

HP Software support provides customer self-solve capabilities. It provides a fast and efficient way to access interactive technical support tools needed to manage your business. As a valued support customer, you can: search for knowledge documents of interest, submit and track progress on support cases, submit enhancement requests online, download software patches, and more.

To access the self-solve knowledge base or to search for the latest versions of HP Software manuals, visit the Knowledge and Manuals Library.

Most of the support areas require that you register as an HP Passport user and sign in. Many also require a support contract. To register for an HP Passport ID, go to: https://softwaresupport.hp.com and click Register.

To find more information about access levels, go to: https://softwaresupport.hp.com/web/softwaresupport/access-levels.

Send documentation feedback to HP