Readme
Mobile Center
Software Version: 2.60
Publication date: February 28, 2018
Software release: February 28, 2018
Mobile Center 2.60 can be installed as a full installation where there is no previous installation of Mobile Center, or as an upgrade on top of an existing installation of Mobile Center 2.53.
This Readme contains up-to-date information on Mobile Center 2.60 limitations.
This section contains limitations in the following areas:
Mobile Center general limitations
AWS server and Amazon Device Farm
Testing tools - UFT Pro (LeanFT)
In Windows 8.1, if you are using Internet Explorer version 11.0.23 as a non-admin user:
These limitations result from Internet Explorer not allowing local storage access. These limitations do not apply if you launch the browser as an administrator.
General
When connecting to Mobile Center over a proxy, it must allow WebSockets traffic in order to record in UFT.
When recording a packaged hybrid app that is not designated as the Startup app, make sure that the hybrid app is included as one of the extra apps. This same guideline applies to the MC Browser.
Before recording or performing a Spy operation on a web page, make sure that the web page has finished loading.
Device Remote View
When working with fingerprint simulation, the fingerprint authentication dialog box may not trigger on certain Samsung Galaxy Note devices, due to the unique location of the touch sensor.
To check if there is a touch sensor on your device, run the Android SDK's custom application call isHardwareDetected(). If a touch sensor is present, and the Fingerprint Authentication dialog box is not triggered, this indicates that the device is not supported. Instead, you will be prompted for a password.
Android:
Photo and video simulation require that the application under test be able to access external storage. In certain devices, you need to manually enable this capability. To enable it, select the app in the Settings section, and under Permissions, select Enable storage.
Record & replay of the Android app chooser system widget is not supported. An example is the selection of an email app when prompted by the device, if a default email app was not set.
SMS simulation is not supported for Android 6 and above.
iOS:
iOS 10.3 and higher: For applications bigger than 50MB, there is a need to change the following configuration for a longer timeout -
server\jetty\webapps\hp4m-connector\WEB-INF\classes\application.properties
For Linux & Mac:
connector.mac.ios10.timeWaitForInstall.in.millis=10000
connector.mac.ios10.waitForInstall=true
For Windows:
connector.win.ios10.timeWaitForInstall.in.millis=5000
Replay is not supported when a page is opened in a new tab within a native browser.
Packaged apps
Non-packaged apps
Android:
Non-packaged apps built with Crosswalk projects framework are not supported.
For MobileList, Childobject only retrieves the child objects that are present on the screen.
iOS:
Record and replay may fail for pages using dynamic URLs.
Workaround: Begin recording the page again to get the right MobileWebView.
When viewing the Mobile Center console located on an AWS machine, you may experience a delay in the refreshing of the data.
When trying to execute a new test after leaving UFT open for an extended period of time, the system attempts indefinitely to allocate a device. Workaround: Close the test and reopen it.
Whitelisted on-premises server
The following items apply when working with an on-premises server with a whitelisted connector:
When working with an on-premises server with a whitelisted connector, you are limited to running 100 concurrent tests with the ADF devices.
Only Chrome and Safari are supported as native browsers.
Recording is not supported for auto-completed URLs. For example, if you begin typing a URL and an auto-complete drop down list opens, your selection will not be recorded. On iOS devices, nothing will be recorded. On Android devices, it will record the previous selection. Workaround: Manually type in the whole URL or navigate via the drop down list to the next page you want to test.
For Android native browsers used with non-packaged hybrid apps: The WebSocket connection may fail, preventing the steps from being recorded by testing tools. Once you reinstate the WebSocket connection, the recorded steps, which were stored by the agent, will be added to the script.
The following test object methods are not supported:
Browser.Back
On certain devices, a memory leakage issue may cause hybrid apps to become unresponsive after several replay sessions.
The following limitations apply when using testing tools with Mobile Center and Windows Phone.
Native browsers are not supported.
MC Browser is not supported with TruClient.
Web parts on hybrid apps are not supported for TruClient.
In UFT's Record and Run settings, Launch on Start for a system app is not supported.
In UFT's Record and Run settings, the Restart application before recording or running option is not supported.
Device orientation, event simulation, and metrics are not supported.
For devices with a hardware Back button, a long press on the button is not supported.
For devices with an on-screen Back button, a long press on the button is only supported in Idle mode, but not in Record mode. If, while in Idle mode, you perform a Spy on the Task Switching, the device may disconnect.
When using the soft keyboard for recording, the steps are recorded as a Tap actions on MobileButton instead of an EnterKeys action.
Replay and Spy functionality may be slower within the MC Browser app on Windows Phone devices.
The RadioButtonGroup object is recognized as a MobileObject test object, and not MobileRadioGroup. Replay this object using the Tap method on the MobileObject object.
Spying from UFT may fail due to timeout. To prevent this, increase the Spy timeout in the Windows registry key on the UFT machine HKCU\Software\Mercury Interactive\QuickTest Professional\MicTest\Packages\MobilePackage\Settings\SpyMsgTimeout
.
Workaround: The default timeout in UFT 12.53 is 6 seconds. Increase it to 30 - 60 seconds and restart UFT.
Swipe gestures on web elements are not supported.
Text checkpoints are not supported on web elements.
Running the media player in a website causes the app to become unresponsive and the Agent shows a status of connecting.
The following are additional limitations when using the ALM Mobile Center extension:
Note: Some of the UFT limitations may also apply to the Sprinter testing tools.
The following are additional limitations when using Unified Functional Testing (UFT) with Mobile Center.
Getting started | |
General | |
Editing tests | |
Web testing | |
Specific types of apps | |
ALM |
If you have upgraded your version of Mobile Center and continuing to work with UFT 14.00, you may need to re-select your apps in the Record and Run Settings dialog box.
To do this, clear your app selections and either refresh the drop-down to show the updated options, or use the Mobile Center wizard to re-select your apps.
UFT also has newer versions available. For details, see Unified Functional Testing (UFT) and What's New in UFT.
If either your UFT or Mobile Center sessions are invalid, due to license issues or timeout from the Mobile Center server, when pressing the Test Connection in the Mobile pane of the Options dialog in UFT gives you an operation timeout.
Workaround: Exit from UFT and Mobile Center as necessary and make sure your licenses are correctly installed for the correct products. Then reconnect to UFT and Mobile Center.
Running UFT tests with Mobile Center
Switching between the Device Capabilities and Specific Device tabs
Device filtering in test runs: Multiple steps with different device filters
Switching back from StormRunner Functional
If your Record and Run Settings are defined to use StormRunner Functional on the Mobile tab, UFT may show an error when selecting the Open Application in Mobile Center option.
If this occurs, update your Record and Run Settings to use Mobile Center, and try again.
Selecting devices and launching browsers
To avoid errors, ensure that the methods used to lock your device and launch a browser on the same device are consistent between your Record and Run Settings and your test steps.
Record and Run Settings | Test Step Method |
---|---|
Specific device selected | Use the same device ID in your test step with the LaunchMobileBrowserWithID method. |
Device capabilities defined to lock any matching device | Use the same device capability parameters in your test step with the LaunchBrowser method. |
For more details, see the LaunchBrowser and LaunchMobileBrowserWithID method documentation in the UFT Object Model Reference.
Step results for failed fingerprint simulations may show differently, depending on the app's configured behavior.
Switching between the Device Capabilities and Specific Device tabs
Sometimes, when configuring the Record and Run Settings in UFT, if you switch between the Device Capabilities and the Specific Device tab, and then click the Open in MC button to open the Mobile Center wizard, the Mobile Center wizard opens the Device capabilities tab.
Workaround: Do one of the following:
With the specific device tab open, click OK to close the Record and Run Settings tab. Then open the Record and Run Settings dialog box again and click the Open in MC button to open the Mobile Center tab.
Select the specific device from the Specific device tab in the UFT Record and Run Settings dialog box
Unexpected issues may occur when you are running a test with a MobileWebView test object on multiple devices.
If so, remove the accessibilityid description property from the test object and run the test again.
Device filtering in test runs: Testing multiple devices
If you have multiple steps in your test that use the same device filtering criteria defined by description properties, and also have multiple devices connected to Mobile Center that match the filtering criteria, all relevant steps use the same device used by the first step in your test.
To use a different device in a specific step, modify the filter for that step.
Device filtering in test runs: Modifying your filter
If your device filter is defined by description properties, and you modify those properties before running the test a second time, the device remains locked from the first run, and the second test run will fail.
Unlock the device in Mobile Center before running the test a second time.
Device filtering in test runs: Multiple steps with different device filters
If your test has separate steps with different device filters for each step, where the device filters do not conflict (the same device matches each filter), and:
To use the same device, modify the filter so that the properties match in all relevant steps.
For example, if you have a single device connected that matches the filters in both of the following steps, the test will fail on the second step.
Device("osversion:=8.4","ostype:=iOS").App("name:=MC Browser","identifier:=com.hp.HPMobileWebBrowserINJ").MobileEdit("nativeclass:=UITextField","mcindex:=0","ispassword:=False","class:=Input","accessibilityid:=url").Set "AAA"
Device("ostype:=iOS").App("name:=MC Browser","identifier:=com.hp.HPMobileWebBrowserINJ").MobileEdit("nativeclass:=UITextField","mcindex:=0","ispassword:=False","class:=Input","accessibilityid:=url").Set "BBB"
Modify the steps as follows to run the test:
Device("ostype:=iOS").App("name:=MC Browser","identifier:=com.hp.HPMobileWebBrowserINJ").MobileEdit("nativeclass:=UITextField","mcindex:=0","ispassword:=False","class:=Input","accessibilityid:=url").Set "AAA"
Device("ostype:=iOS").App("name:=MC Browser","identifier:=com.hp.HPMobileWebBrowserINJ").MobileEdit("nativeclass:=UITextField","mcindex:=0","ispassword:=False","class:=Input","accessibilityid:=url").Set "BBB"
Browser steps |
Device information is not included in the HTML run results for Browser steps run on specific devices. |
Local system monitoring | If both Device Metrics and Local System Monitor are enabled for your UFT test or component, the run results show mobile device metrics only. |
If you start recording with the Logs option cleared in the Device Metrics and then stop recording, but resume recording with the option selected, the Download device logs button (in the device Options panel) is not available.
Workaround: Press the Refresh button in the remote access window.
Visual Relation Identifier steps
If the first step in your test uses Visual Relation Identifiers (VRI) to identify an object, your app is not launched, installed, or restarted, even if defined to do so otherwise.
Workaround: Ensure that your app is launched, installed, or restarted before using VRI to identify a test object.
Releasing devices | If you have stopped the parallel execution by pressing CTRL+C, mobile devices are not released automatically. |
Device system monitoring |
Device system monitoring is not displayed in HTML run results graphs. Instead, to view system monitoring data for device tests run in parallel, check the log file linked from the run results. |
Spying and highlighting with Mobile Center
When using the Object Spy, hovering over an object when using the Object Spy to view object properties is not supported. Click the object instead to view the properties.
For native browsers and the MC Browser: When using the Object Spy on the web objects: Back, Forward, Refresh, and URL box, UFT generates Device.app.xx, instead of Browser.page.xx. Workaround: Modify the code manually.
When highlighting an object from the object repository, any non-default identification properties with incorrect values are ignored. This enables UFT to highlight the control in the application.
UFT may not highlight a test object in the object repository in the following scenarios:
Scenario | Workaround |
---|---|
This is the first editing session after installing UFT. | Define the relevant device and application in the Mobile tab of the Record and Run Settings dialog box. Then start and stop a recording session. |
This is the first editing session after restoring factory defaults in the Options dialog box. | Define the relevant device and application in the Mobile tab of the Record and Run Settings dialog box. Then start and stop a recording session. |
The Mobile tab of the Record and Run Settings dialog box is empty, and no device or application is selected. | Define the relevant device and application in the Mobile tab of the Record and Run Settings dialog box. Then start and stop a recording session. |
The remote access window displays a different device than the one defined in the Mobile tab of the Record and Run Settings dialog box. |
Do one of the following:
|
If an object's description properties contain a space at the beginining or end of the property name, UFT and Mobile Center cannot highlight the object.
Workaround: Do one of the following:
Remove this property from the object description in the Object Repository in UFT
Add a regular expression for the property ".*"
When working with Web tests, spying is not supported on iOS devices in non-mobile optimization pages.
Recording and highlighting on certificate related dialogs (from a Web page in a Mobile Web application) is not supported.
Workaround: Add a step using descriptive programming to identify and perform user actions on the certificate dialogs in the test.
In addition, you need to manually install the needed certificate on the device running the test before running the test.
UFT text recognition and Mobile Center
If you use wildcards in your WebUtil.LaunchBrowser steps to perform a fuzzy search for devices, you must also provide an operating system.
For example, the following step may generate errors:
WebUtil.LaunchBrowser "MOBILE_SAFARI","iPhone","",""
Prevent errors by providing an operating system. For example:
WebUtil.LaunchBrowser "MOBILE_SAFARI","iPhone","","iOS"
Uploading media files using drag and drop actions into a SimulateCamera or SimulateVideo operation is not supported.
If the specified files required for the SimulateCamera or SimulateVideo methods are not correct in the test steps, the remote access window gives no indication of the operation being performed successfully or the failure or success of the step.
Workaround: View the step details in the test results.
Business Process Testing and Mobile Center
Using the Capture toolbar is not supported.
When recording a business process test, if you press the Stop button when recording, you cannot start recording again.
Running business process tests of Web applications on mobile devices is not supported for devices on Amazon Web services or Windows Phone.
If you started the HPE Mobile Web app from the HOME screen and started recording, operations performed on the page are recorded when no recorded steps are expected.
The steps are recording using the following syntax:
Browser(XXX).Navigate "XXX"
Creating multiple application areas one right after another with settings defined on the Web or Mobile tabs retains the information from the earlier application area. Clear these settings to define your subsequent application area details from scratch.
BPT does not support multiple application areas in a single test or flow.
For example:
Add the following components to your test or flow, each with a separate application area defined:
Component 1 / Application area 1 |
iOS device AMB app |
Component 2 / Application area 2 |
Android device UiCatalog app |
During your test run, UFT will not be able to find the correct app to install on your second device, the Android.
MobileView object |
The MobileView object is not recorded on Android apps. Instead, you can create it manually in the object repository and do the following:
|
Scrolling |
Scroll and horizontal scroll on Android is not recorded on UFT. |
Mobile Stepper test objects |
The Mobile Stepper test object is not supported for non-packaged apps on iOS devices. On Android devices, these objects are recognized as MobileButton or MobileLabel objects. |
MobileList.Delete method |
The MobileList.Delete method is not supported for non-packaged apps. Instead, swipe left on the list item and tap the Delete button to perform this step. |
MobileDropdown.Select method | Replay is not supported for the MobileDropdown.Select method on non-packaged apps. |
ChildObjects method |
The Container property is not supported for non-packaged apps on iOS. The NativeClass and hint properties and not supported for non-packaged apps on Android. |
Required object description filter | When testing non-packaged apps using the ChildObjects method, you must add a filter to the object description before the ChildObjects step. For example, see Object description filter - example. |
Standard checkpoints, iOS devices |
Existing tests with standard checkpoints may fail if the following properties are included in the checkpoint properties:
If you have these properties in tests created before UFT 14.02, and are running your test on iOS non-packaged apps, avoid errors as follows: Update your test to include a Null value for these properties instead of a Boolean value (True / False) |
Object description filter - example
Set oDesc = Description.Create()
oDesc("class").Value = "Button"
Set Buttons = Device("Device").App("UICatalog_2").ChildObjects(oDesc)
NumberOfButtons = Labels.Count()
For i = 0 To NumberOfButtons - 1
Buttons(i).Tap
Next
Testing SAP Fiori apps with Mobile Center
If your test was created for a desktop version of a Fiori application, you may need to modify the test to ensure it runs correctly on the mobile version.
Additionally, different resolutions on different devices may cause differences in an object's properties and behavior. You may need to manually edit the test script to support multiple devices.
Tip: Add an Exist statement to ensure that an object is completely loaded on a page in a Fiori mobile application before running steps on that object.
Specific SAP objects and methods
SAPUIRadioGroup |
The SAPUIRadioGroup test object is not supported for Fiori applications. |
SAPUITextEdit / SAPUIButton |
Sometimes, when using SAPUITextEdit and SAPUIButton objects, the test steps are recorded in the incorrect order. If this happens, change the order of the steps manually. |
SAPUITextEdit |
The SAPUITextEdit test object html tag identification property now uses the parent DIV element (instead of the INPUT element). You must update any:
|
SAPUIDialog.Close |
The SAPUIDialog.Close button works only when a dialog contains a X close button. |
Standard checkpoints and output values in SAP Fiori apps
When inserting standard checkpoints and output values to an already recorded test, and running standard checkpoint and output value steps on Fiori mobile applications, the test object must be fully visible in the Mobile Center remote access window.
This is relevant when editing the test, and not when recording it.
Fiori 1.6x client freezes
The remote access display does not support apps using the Android FLAG_SECURE window flag. For details, see WindowManager.LayoutParams.html. To use such apps with Mobile Center you need to remove the flag. See Manually package your android app for more details.
Using the MC Browser app with UFT
Running mobile tests on Shadow Dom web apps and iOS devices is only supported for:
Using the Chrome emulator with UFT
Multiple tabs |
Multiple tabs are not supported, as well as the Browser.OpenNewTab and Browser.CloseAllTabs methods. Unsupported methods may cause unexpected behavior when run in the emulator. |
Object Spy |
The Object Spy and Highlight in Application (from the Object Spy) are not supported for the emulator. Test objects added while recording using the emulator cannot later be highlighted from the object repository. |
Checkpoints and output values |
Checkpoints and output values cannot be added during recording and must be added manually when editing test steps. |
Maintenance mode |
Maintenance mode is not supported. |
Test objects |
|
UFT on Windows Server 2012 R2 |
Native browsers are not supported when running UFT on Windows Server 2012 R2. |
Test object description properties |
Native browsers, including Chrome on Android and Safari on iOS, do not relate to test object description properties. Therefore, data driving on native browsers relates to data defined in the Data table or test parameters only, and will not search for test objects with matching test object property values. |
Device logs |
When running a test via UFT on a native browser or the MC Browser app, device logs are generated only when users:
|
WebAudio / Web Video objects |
|
Define an initial URL |
Test runs may fail if the same script is run multiple times without an initial URL to start the test with. To avoid errors, define a URL for your test in the Record and Run Settings dialog. |
iframe objects |
UFT cannot record on iframe objects in iOS devices when the code of objects inside the iframe use document.write(). |
Bitmap checkpoints |
On iOS native browsers, bitmap checkpoints inserted while recording, and after having scrolled to a following page, are not supported. Such checkpoints will fail. |
Switching devices |
UFT cannot switch devices while running a single native browser script. |
UFT cannot record or run steps on native mobile controls, such as a native date picker when working in a native browser or the MC Browser.
Workaround: Add the native mobile control to the object repository manually, and then manually add a step to operate the control.
For example:
Spy on a date picker control, and add the corresponding WebEdit object to the Object Repository.
Then add a step similar to the following to your test:
Browser(“Reservations”).Page(“Your Reservation”).WebEdit(“check-in-date”).Click
The following features are not supported when testing hybrid applications:
Mobile optimization
The following are supported only for web pages that are optimized for mobile:
Certain hybrid apps may issue an error "This test was created using an earlier version of UFT and therefore requires a different Javascript engine".
This can happen if the app is launched by another app or from HOME.
Workaround: Have the app launched by the testing tool. Stop the recording, restart the app, but do not reinstall. Begin recording again. Alternatively you can use this Javascript code:
Device("<Device>").App("<appname>").Launch DoNotInstall,Restart
Note: Some features not supported for mobile in general are supported when working with hybrid applications. For details, see Unsupported features, test objects, and methods.
Additional limitations:
Keyword View |
In the Keyword View, you may not be able to use the Insert run-time object option in the Select Test Object dialog box to insert a Workaround: Enter the |
Text checkpoint and output value steps |
When recording and running text checkpoint and output value steps, the test object must be fully visible in the remote access window. |
WebList steps |
Sometimes, when recording a WebList test object step, steps are added for both MobileDropDown and WebList test objects. This may cause the MobileDropDown step to fail. To avoid this, delete the extra MobileDropDown step. |
Recording date and time |
Sometimes, when recording the date and time on MobileWeb test objects, native application steps are added in addition to hybrid application steps. This may cause the step to fail during a run session. Workaround: Delete the extra native application steps. |
Run results |
CSS elements may be displayed erroneously in the Captured Data pane of the Run Results Viewer (not relevant for HTML report). |
Using the Spy | If your application does not have a view port defined for the application, if you scroll the page in your application, the area that the Object Spy highlights is offset. |
Working with ALM and Mobile Center
Asset Comparison tool |
The Asset Comparison tool does not compare changes in the Record and Run Settings for Mobile tests. |
Test object icons |
Test object icons for Mobile objects are not displayed in the Test Plan module or for object repositories saved in ALM. |
Only proxy servers that support the WebSocket protocol are supported. For Apache servers, use version 2.4 or later.
Basic authentication must be permitted on the port used by the proxy server.
Apache configuration example:
###forward basic authentication### ProxyRequests on AllowCONNECT 8108 8080 80 7002 443 8443
If the Camera or Video Simulation windows do not display the media files for sensor simulation steps when uploading media files from a URL, make sure to set the proxy settings in the Mobile pane of the Options dialog in UFT (Tools > Options > GUI Testing tab > Mobile node).
Commas as decimal points |
Your localized operating system may use commas as decimal points. This is not supported by UFT, and you may need to manually fix recorded steps to use periods as decimal points instead. It is recommended to always use the period character as a decimal point, regardless of the locale of your operating system. |
Suggested characters |
Steps that include Japanese/Chinese characters that were added from the suggested characters line above the keyboard may not run correctly. |
Tests created in earlier versions of UFT
Tests created prior to UFT 12.51
For tests that were created on hybrid applications prior to UFT 12.51, only the text, isEnabled, and isFocused properties are supported for checkpoints and output values.
Additionally, you must make sure that UFT re-installs or restarts the app before running steps on the app.
You can:
Use the Record and Run Settings (for GUI tests).
Add a step that uses the App.Launch
method.
For details, see the Mobile section of the Object Model Reference in the UFT Help Center.
Tests created in UFT 12.02 Patch 1 or earlier
When working with an object repository in a test created in UFT 12.02 Patch 1 or earlier, the following commands are not supported:
Highlight in Application
Locate in Repository
Instead, update the test object descriptions from the application (select the test object and click Update from Application).
Caution: If you are working with MobileLabel test objects that are part of a MobileList test object, updating the description from the application can cause your test to behave unexpectedly.
To update the description of a MobileLabel test object from the application, replace it with a MobileList test object.
In the relevant test steps, replace the steps containing MobileLabel.MakeVisible and MobileLabel.Tap with a single step containing MobileList.Select <index>.
For example, replace:
Device("Device").App("UICatalog").MobileLabel("ListViewActivity").MakeVisible
Device("Device").App("UICatalog").MobileLabel("ListViewActivity").Tap
with:
Device("Device").App("UICatalog").MobileList("list").Select 5
Tests created with Mobile Center versions prior to 1.51
If you have a test of containing steps on hybrid application which was created using Mobile Center versions prior to 1.51, this test is not supported on Mobile Center version 2.01 and later.
Unsupported features, test objects, and methods
The UFT Mobile Add-in only supports recording and running steps on mobile applications.
When working with mobile objects, the following UFT abilities are not supported, or are only partially supported:
Active Screen.
Assistive properties in the Object Identification dialog box.
Bitmap checkpoints on an App test object.Supported for hybrid applications only.
Device.SetOrientation method: Only the LandscapeRight and Portrait parameters are supported.
Exist property for Mobile objects, when the object is not found, and the customer uses a default timeout value, or timeout value greater than 30 seconds (applicable to UFT 14.01 and earlier).
Workaround: Add a timeout value of less than 30 seconds. For example:
Device("Device").App("UICatalog").MobileList("list").Exist(3)
Insight is supported only with image quality set to 100%.
LaunchBrowser. Although only the Browser argument is required, to prevent errors, you must define at least one other argument for this method. For details, see the LaunchBrowser documentation in the UFT Help Center Object Model Reference.
Local System Monitors. Instead, you can instruct UFT to collect Mobile vitals in the Record and Run Settings dialog box. This data is then presented in the Local System Monitor pane in the run results.
Low-level recording
Maintenance Run Mode. Supported for hybrid applications only.
Tapping on a MobileStepper object (a MobileStepper.Tap method)
Navigate and Learn, including adding children of a parent test object to the object repository.
Ordinal identifiers. Supported for hybrid applications only.
Recovery scenarios: The following trigger events and recovery operations are not supported for mobile:
Trigger events |
Popup window Object state Application crash |
Recovery operations |
Keyboard or mouse operation > click button with label Close application process |
SetFingerprintSimulation. The SetFingerprintSimulation method is not supported as the first step in a script. To avoid errors, ensure your script includes another step before the SetFingerprintSimulation method.
Smart identification. Supported for hybrid applications only.
Update Run Mode. Only the option for updating checkpoints and output values is supported. Supported for hybrid applications only.
Virtual objects
Visual Relations Identifiers (VRI) with multiple remote windows opened, or in Web tests on hybrid apps.
WebVideo and WebAudio.Play
Testing on the SAP Fiori native browser is currently not supported when parallel test execution is enabled (default) in LeanFT:
Workaround: If you want to run tests on the SAP Fiori native browser, disable parallel testing on mobile devices.
To disable parallel testing on mobile devices:
In a text editor, open a new file.
Copy and paste the following code:
{ "labManager" : { "useLocalLabManager": true, "environments": ["web"], } }
On Windows, when selecting a device using the Mobile Center dialog, the device is not released when the dialog is closed.
Workaround: To release the device, you must manually restart the LeanFT runtime engine.
When connected to an iOS device, you cannot use the Object Identification Center to spy on a Mobile TabStrip object.
Workaround: Create the object description or application model test object manually. See the UFT Pro (LeanFT) SDK Reference for a list of available identification properties.
The following methods are not supported on iOS devices:
Label.Tap() | Stepper.Up() |
Label.LongPress() | Stepper.Down() |
Pager.Set() | TabStrip.Select() |
RadioGroup.Select() | Table.Tap() |
Slider.SetPosition() | Device.Shake() |
Device.SimulateIncomingSMS() and SimulateIncomingCall() are not supported.
The Web.Frame object is not supported in Mobile browsers.
Validate on iOS devices only works if the test object properties used for validation do not include MobileCenterIndex or Container.
When running a Web test on a mobile device, if a modal dialog box displays on the browser, then the test will pause and eventually timeout without completing.
Radio button controls that are not defined as part of a radio button group are not supported in LeanFT.
When opening several tabs in a browser on a mobile device, only the first tab opened is recognized by the LeanFT engine.
The following are additional limitations when using TruClient with Mobile Center:
To generate transaction response time information for your test, you must specify a packaged version of your native app and define Object Exists end events in your TruClient script steps.
Certain versions of software and/or documents (“Material”) accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by , a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.
The only warranties for products and services of Micro Focus and its affiliates and licensors (“Micro Focus”) are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Micro Focus shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice.
Contains Confidential Information. Except as specifically indicated otherwise, a valid license is required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.
The code signing certificate for Mobile Center was changed from Verisign to Comodo starting on January 1, 2017.
If you are installing this product on a computer with an older version of Windows, or on a computer without automatic Windows updates, the Comodo root certificate may not automatically be included as a trusted root certificate.
In such cases, we recommend manually configuring Comodo as a trusted root certificate.
For more details, see: https://technet.microsoft.com/en-gb/library/dn265983.aspx.
© Copyright 2014-2018 Micro Focus or one of its affiliates
Adobe™ is a trademark of Adobe Systems Incorporated.
Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.
UNIX® is a registered trademark of The Open Group.
Oracle and Java are registered trademarks of Oracle and/or its affiliates.
Red Hat® is a registered trademark of Red Hat, Inc. in the United States and other countries.
Apple and the Apple logo are trademarks of Apple Computer, Inc., registered in the U.S. and other countries.
iPad® is a trademark of Apple Inc.
iPhone® is a trademark of Apple Inc.
Google™ and Google Maps™ © 2012 Google Inc. All rights reserved. Google and the Google Logo are registered trademarks of Google Inc.
Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.