What's new in Lean Functional Testing (LeanFT) 14.50
Version 14.50 of LeanFT includes the following new features and enhancements.
The new LeanFT Grid feature enables LeanFT to recognize multiple node machines available for testing, and allocate a specific one for each test run.
When configured, the LeanFT grid selects a node for a test run, based on environment details specified in your tests, as well as each node’s capabilities and availability.
This enables you to:
- Run the same test on different environments by changing the test parameters that describe the required environment.
- Leverage the power of your testing lab: You can achieve distributed parallel test execution, by running all of your tests on the grid and letting it allocate nodes for all of the test runs, as needed.
With minor adjustments, you can run your existing tests using the LeanFT grid. For more details, see LeanFT Grid.
Note: The LeanFT Grid is currently supported only for tests written in Java.
Run more tests in parallel (Dynamic concurrent license consumption)
To enable you to run more tests in parallel, LeanFT can now consume more than one concurrent license at a time. Each license allows LeanFT to run four parallel test operations.
In the LeanFT runtime engine settings, define the maximum number of licenses this instance of LeanFT can consume. When running parallel tests, LeanFT will gradually consume and release licenses as needed.
Test Recorder enhancements
This version of LeanFT introduces an improved Test Recorder, whose look and feel resembles the Object Identification Center, and provides new capabilities:
Supported browsers and technologies
You can now record tests on additional browsers and technologies:
|Desktop applications on Windows||Standard Windows, Java, WPF, WinForms.|
Add verifications while recording
During a recording session, you can now add verification steps, which will be included in the code that you generate from the session.
When adding a verification step, click the object you want to check. A new graphical user interface opens for you to select the properties and values to verify.
Export step descriptions
In addition to generating code from the steps you record, you can now export the recorded steps' descriptions to a CSV file , creating a manual-test version of the recorded steps.
To learn more, see Test Recorder.
Mobile support enhancements
In this version, we've introduced the following mobile testing abilities:
Support for working with multiple Mobile Center workspaces
When configuring your Mobile Center connection credentials in the runtime engine settings, you can now specify a workspace as well. For details, see Mobile Center Settings.
Support fingerprint and facial recognition authentication
Support barcode and QR code simulation
Extended technology support
As in every version, LeanFT continues to extend its technology and browser support.
In this version, we've added support for the following:
- Headless Chrome
For more details, see Product Availability Matrix.
LeanFT for Selenium available in .NET
LeanFT .NET support for Selenium includes:
- IDE templates for Selenium-based projects in Visual Studio
- An extended Selenium .NET SDK with additional locators and utilities
C# code generation from the Selenium-specific Object Identification Center
For more details, see LeanFT for Selenium.
LeanFT now offers the following report capabilities:
Generate report per test or per class
In addition to the report for the whole run, you can now configure a LeanFT test to provide a report per test method or per class. For details on configuring this option, see the Report Settings section in Customize test settings.
View mobile device vitals in a graph
If a test collects mobile device vitals by calling the getVitals method, the report now includes a graphical representation of the device vitals data collected over time. Hover over an area in the graph to see the device vitals relevant to that point in time.
For more details, see Check device vitals.
Verification mode for reporting context
When creating sections in a report using the StartReportingContext and EndReportingContext methods, you can specify a context mode.
The context mode can be Normal or Verification, making it easier to distinguish verification sections from sections containing other types of steps.
Modified command for launching LeanFT (Windows only)
If you used to launch LeanFT by running LFTRuntime.exe from the <LeanFT installation>\bin folder, launch it now by running
For more details on launching LeanFT, see Start/Stop the runtime engine.
If you use the AutoPass licensing server, and are upgrading to LeanFT 14.50, you must also upgrade your AutoPass installation to version 10.7.
For details, see the AutoPass License Server page on the Micro Focus Marketplace.
Micro Focus rebranding
We've rebranded LeanFT 14.50 to the Micro Focus brand. If you are working on Windows, the following changes are relevant:
The LeanFT default installation folder is now under Micro Focus in the Program Files folder.
If you upgrade to LeanFT 14.50 from an earlier version, we'll keep the product settings and configurations that you previously defined.
However, user interface preferences will revert back to their defaults. For example, this includes recent LeanFT selections in your IDEs and the language for code generation in the Test Recorder and the Object Identification Center.
- If you need to access your config.json file, it is now located in the %localappdata%\LeanFT\config folder.
- For details on updating the application model color theme in Eclipse or Spring Tool Suite, see Application Model editor functionality.
Any new log files are stored in: %localappdata%/LeanFT/Logs
Help Center search enhancements
The help center now includes advanced site search functionality:
- Intuitive friendly Google-like search
- Search across all ADM help centers
- Filter search results by selected products
Get results from separate deliverables from the home page search, including both the Help Center and SDK references.
- New uniform SDK reference structure with improved search and navigation.
Additional improvements and fixes
This section includes a list of fixed known issues and additional feature improvements in LeanFT14.50.
Synchronizing tests with your application objects
We've introduced new WaitUntil API methods for basic synchronization between test steps and the application's state.
Use the new methods to wait for an object in the application to exist, become enabled, or become visible before performing the next step: WaitUntilExists, WaitUntilEnabled, WaitUntilVisible.
These methods are available in addition to the existing WaitUntil method, which supports waiting until the object meets a specific condition.
Disable idle shutdown
In the runtime engine configuration, you can now disable the Engine idle timeout. The LeanFT runtime engine continues to run even if it is not in use.
LeanFT now supports working with ALM 14 servers that require API Keys for authentication. When configuring the authentication settings in the ALM configuration tool, you can now use API Keys, which you obtain from your ALM site administrator.
- We've added ExtendSelect and SelectRange methods or overloads to many list and table test objects.
- We've extended the list of Mobile properties and identification properties to match those supported by UFT.
The Java add-in's UIObject test object now supports a text property.
LeanFT test runs
- Running LeanFT tests with ALM parameters that contain line breaks no longer causes exceptions.
- TestNG tests no longer get stuck in Running status after the test run ends.
- Running Desktop.launchAut with an incorrect file name as the parameter now marks the step as failed and does not shut down the runtime engine.
LeanFT runtime engine issues
- If you install only the LeanFT runtime engine, you can now run a test without manually running the engine first. The engine will run automatically.
- On a Mac, you can now shut down the LeanFT runtime engine using CTRL + C.