HPE Mobile Center

Software Version: 2.01


Publication date: 14 November 2016

Software release: 29 September 2016

Mobile Center 2.01 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.00.

This Readme contains up-to-date information on Mobile Center 2.01 limitations.


This section contains limitations in the following areas:

Mobile Center general limitations

Record and replay

Native browsers

AWS server and Amazon Device Farm

Windows Phone


ALM Mobile Center extension

Testing tools - UFT

Testing tools - LeanFT

Testing tools - TruClient

Mobile Center general limitations

Installation and upgrade

Multi-Language support

Mobile Center server does not support non-English OS servers.

Saving filter preferences

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.

Uploading apps

The maximum file size that you can upload is 200 MB.

Record and replay




Packaged apps

Non-packaged apps



AWS server and Amazon Device Farm

Whitelisted on-premise server

The following items apply when working with an on-premise server with a whitelisted connector:

Native browsers

Windows Phone


ALM Mobile Center extension

The following are additional limitations when using the ALM Mobile Center extension:

Testing tools - UFT

The following are additional limitations when using Unified Functional Testing (UFT) with Mobile Center.

Running UFT tests with Mobile Center

Multiple devices in test runs

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"

Run results

Device information is not included in the HTML run results for Browser steps run on specific devices.

Spying and highlighting with Mobile Center

UFT text recognition and Mobile Center

Text recognition in UFT for devices does not support the Tesseract OCR text recognition engine.

UFT regular expressions and Mobile Center

Regular expressions are not supported for the class property in ChildObject methods when testing native apps.

Business Process Testing and Mobile Center

Testing Android apps with UFT

The MobileView object is not recorded.

Instead, you can create it manually in the object repository and do the following:

Non-packaged apps and UFT

Device.SetOrientation method Orientation is not supported when testing non-packaged apps on iOS devices.

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

Only the following ChildObjects method properties are supported when testing non-packaged devices on iOS devices:

  • accessibilityid
  • class
  • hint
  • ischecked
  • ischeckable
  • isenabled
  • isfocusable
  • ispassword
  • iscscrollable
  • isvisible
  • nativeclass
  • text
  • value
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.

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

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


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.


The SAPUITextEdit test object html tag identification property now uses the parent DIV element (instead of the INPUT element).

You must update any:

  • Tests that include checkpoints, output values or GetROProperty("html tag") steps on the SAPUITextEdit test object.
  • SAPUITextEdit objects you have in your object repositories.


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. For packaged apps, see Manually package your android appfor more details. For non-packaged apps, see the section on how to manually enable content debugging in Enable remote content debugging.
  • Using the MC Browser app with UFT

    Invalid URLs

    If a test step navigates to an invalid URL, both the address bar and page are displayed as blank.

    Run Results Viewer

    When tests are run on the MC Browser app, CSS elements may be displayed erroneously in the Captured Data pane of the Run Results Viewer (not relevant for HTML report).

    Network virtualization and the MC Browser app

    When using Network Virtualization and testing the Mobile Web app without enabling mobile testing on the Mobile tab of the Record and Run Settings dialog box, you must add the device ID in the object repository, or use descriptive programming to identify a device.

    This limitation does not apply when testing is enabled on the Mobile tab.

    Running Web tests using the MC Browser app
    • If a test step navigates to an invalid URL, both the address bar and page are displayed as blank.
    • In the Record and Run Settings dialog box, the Restart Browser before Run and Uninstall Browser when Run Ends options are not supported when the test is run from a specific step.
    • Some Browser methods are not supported.

      Test steps that include unsupported commands are skipped, and do not cause the test to fail. Instead, relevant warnings are displayed in the run results.

      Unsupported methods include:

      • .ClearCache
      • .Close
      • .CloseAllTabs
      • .DeleteCookies
      • .DialogExists
      • .FullScreen
      • .GetDialogText
      • HandleDialog
      • .Home
      • .IsSiblingTab
      • .OpenNewTab

    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

    The WebFile object is not supported.

    Native browsers and UFT

    Hybrid apps and UFT

    The following features are not supported when testing hybrid applications:

    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. Workaround: 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 .Object statement for a selected test object.

    Workaround: Enter the .Object statement manually.

    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).

    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.

    Using Network Virtualization with UFT and Mobile Center

    When using a mobile proxy, starting NV from UFT (for example by sending Device("Device").StartNV "3G Good") results in a second test being opened on the device, and a timeout error.

    Using Proxy servers and UFT

    Apache configuration example:

    ###forward basic authentication###
    					ProxyRequests on
    				AllowCONNECT 8108 8080 80 7002 443 8443


    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 do the following to enable your test or component to run properly:

    1. Select the Test was created prior to UFT 12.51... check box before running the test.

      For tests

      Select the File > Test Settings > Mobile Advanced tab.

      Select the Test was created prior to UFT 12.51 and contains steps on a hybrid mobile app check box.

      For components

      Open the application area, and in the sidebar, select Additional Settings > Mobile Advanced.

      In the Mobile pane, select the Test was created prior to UFT 12.51 and contains steps on a hybrid mobile app check box.

    2. Make sure that UFT re-installs or restarts the app before running steps on the app.

      You can:

    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:

    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").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.

    Unsupported features, test objects, and methods

    The UFT Mobile Add-in supports only recording and running steps on mobile applications.

    The following UFT abilities are not supported, or are only partially supported, when working with mobile objects:

    Testing tools - LeanFT

    Testing tools - TruClient

    The following are additional limitations when using TruClient with Mobile Center:

    Legal Notices


    The only warranties for Hewlett Packard Enterprise Development LP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HPE shall not be liable for technical or editorial errors or omissions contained herein.

    The information contained herein is subject to change without notice.

    Restricted Rights Legend

    Confidential computer software. Valid license from HPE 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.

    Copyright Notice

    © Copyright 2016Hewlett Packard Enterprise Development LP

    Trademark Notices

    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.

    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™ © 2012 Google Inc. All rights reserved. Google and the Google Logo are registered trademarks of Google Inc.

    Send documentation feedback