Readme

HPE Mobile Center

Software Version: 1.51

Publication date: 21 December 2015

Software release: 21 December 2015

This Readme provides information about Mobile Center 1.51 such as system requirements, integrations information, and known issues:

• How to install
• Server requirements
• Supported devices
• Connector requirements
• Network requirements
• Multi-language support
• Integrations
• Limitations

How to install

Mobile Center 1.51 can be installed in one of the following ways:

• A full installation where there is no previous installation of Mobile Center
• An upgrade on top of an existing installation of version 1.50, 1.50 Patch 1, and 1.50 Patch 2 of Mobile Center.

See the Install Guide for detailed instructions on how to install Mobile Center.

Server requirements

The Mobile Center server can also be run on a virtual machine.*

Linux server

Windows server

*Hosted virtualization hypervisors are supported. Mobile Center has been certified with:

• VMWare Workstation 10.0.3. and 11.1.2
• Microsoft Hyper-V 2012 R2. Certified for server installation only. Devices should not be connected directly to the Hyper-V machine, but should be connected using a connector on a different (non-Hyper-V) machine.

Supported devices

For the most up-to-date list of certified devices, see supported devices.

The following devices are supported by Mobile Center:

Android

Devices running on Android 4.1 OS and higher. Remote access is supported only on devices with an ARM CPU*.

The following devices have been tested and verified with Mobile Center:

iOS

Devices running on iOS 7.x OS and higher.

The following devices have been tested and verified with Mobile Center:

Emulators

(Android 4.1 and higher):

Google SDK

Genymotion

Connector requirements

When you install Mobile Center, both the server and the connector are installed. However, the connector is designed as a lightweight piece of software for connecting devices to Mobile Center, that can also be installed as a standalone component. You can install the connector on multiple machines in distributed locations, or on your testing-tool machine. The connector can be installed on a Windows or Linux machine. For details, see Install the connector on a Windows machine or Install the connector on a Linux machine.

Every mobile device connected to Mobile Center requires 900mA - 1.5A per port, depending on the device. To optimize power consumption and provide better utilization of USB ports, we recommend using a USB hub with an independent power supply that can sustain power consumption.

Network requirements

The following ports are required:

Multi-language support

• Non-English apps are supported for record and replay by Mobile Center.
• Mobile Center's user interface supports 7 languages (L10N) - English, French, German, Russian, Japanese, Korean and Chinese. The language used in the Mobile Center user interface is determined by the language used for the testing tool.
• Device OS is supported for 7 languages (L10N) - English, French, German, Russian, Japanese, Korean and Chinese.

Integrations

For a complete list of products that integrate with Mobile Center, check out My Product Matrix.

Limitations

Upgrade

In a non-distributed environment (devices are connected directly to the server machine only), where the Mobile Center server has been configured to work with testing tools over SSL, remote access fails after upgrading the server to Mobile Center 1.51.

Workaround: Uninstall Mobile Center and install Mobile Center 1.51 as a full installation.

Connector Names

• When a connector is stopped or disconnected, the list of connectors in the Filter section will show the connector ID instead of its name.
• If there are no devices registered to a connector, the filter's Connector drop down list will show the connector ID and not its name.

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:

• You will not be able to save your filter preferences.
• The check box to hide certain message pop-up windows, will not be effective.

These limitations result from Internet Explorer not allowing localStorage 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 200MB.

Remote access

• For the remote access display to have the same orientation as the device, the initial orientation of the device must be set to portrait when starting a recording session.
• Android. 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 details, see Manually package your android app.

• When connecting to Mobile Center over a proxy, it must allow WebSockets traffic in order to record in UFT.

Record and Replay

• Crosswalk and Mono (sponsored by Xamarin) frameworks are not supported.
• In some cases when a device that is turned off is connected to the server, when it is turned on and used for recording, it may become unavailable after recording begins.

Android:

• When recording, the Recent Apps button in the Mobile Center remote access display behaves like the Home button, and brings the device to the Home screen. When the test is replayed, Recent Apps functions correctly.
• Certain Samsung devices do not connect after rebooting the server.
  Solution: Connect through a USB 3.0 port. To determine which port is 3.0, look for a blue marking on the port, an SS notation indicating Super Speed (HP machines), or refer to your manufacturer's manual.
• The Back, Home and Recent Apps buttons in the Mobile Center remote access display can't be recorded in analog mode. Change orientation can't be recorded in both analog and non-analog mode. This action should be added manually to the script.

iOS:

• iOS v 8.4.1 and 9.0 devices are supported by Mobile Center only if the HP4M agent and launcher apps are re-signed with a developer certificate. For details, see Connect iOS mobile devices.

• Apps designed for iPhones are not supported by Mobile Center when running in compatible mode on an iPad.

Network Virtualization

When upgrading from Mobile Center 1.50, the NV_TEST_MANAGER field in the /opt/hpmc/conf/nv.properties file is not updated automatically with the correct data.

Workaround: When upgrading a Mobile Center environment where the nv.properties file was configured, reconfigure the NV_TEST_MANAGER field after upgrade.

Testing tools - UFT

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

• Opening Mobile Center
• Running tests
• Spying and highlighting
• Business Process Testing
• Testing Android apps
• Testing SAP Fiori apps
• Using the HP Mobile Web app
• Using Chrome's mobile browser emulator
• Hybrid applications
• Working with ALM
• Using Proxy servers
• Localization
• Tests created in earlier versions of UFT
• Unsupported features

Opening Mobile Center

After defining the connection information for Mobile Center in the Options dialog box, the remote access window opens every time a record or run session begins.

To prevent this window from opening when you are not testing mobile applications, select Do not record and run tests on mobile in the Mobile pane of the Record and Run settings dialog box.

Running tests

• When you run a test or component on a mobile device, the device remains locked by Mobile Center until the test or component is closed. This is true even if the test or component is no longer running.

• During a run session, if the description of a Device test object in the object repository is empty, UFT uses the description in the Record and Run Settings dialog box. To use programmatic descriptions with the Device test object, manually add "micclass:=Device" to the step, for example:

  Device("micclass:=Device").App(...

• Sometimes, snapshots are not included in the run results even though the Save still image captures to results option in UFT is set to Always. (Tools > Options > GUI Testing tab > Screen Capture node)

Spying and highlighting

• 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: 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. Set the id property in the Device test object description to the value of the device that is open in the remote access window.

Business Process Testing

• Using a component parameter to provide the value for a MobileCalendar object argument values may lead to unexpected results. 
  Workaround: Use a Data Table parameter for the MobileCalendar object argument values.

• Capture is not supported.

Testing Android apps

• The MobileView object is not recorded.

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

  • Set the isscrollable property to true.

  • Set the mcindex property.

  • Set the class property according to the actual type of scrollable control. (You can use the Object Spy to verify the class.)

  • Remove all other properties (do not leave blank, remove).

• The Swipe method is not recorded. Instead, manually add Swipe statements to a test or component.

Testing SAP Fiori apps

Supported in UFT12.51 Patch 1 only.

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.

Specific objects and methods

Standard checkpoints and output values

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.

Manually packaged mobile apps for Android devices

When working with manually packaged mobile apps for Android devices, you must:

1. Before recording or running a test, select the check box in the Mobile Hybrid tab of the Settings dialog box (File > Settings > Mobile Hybrid).

   In all other cases, this check box should be cleared.

2. In the Mobile tab of the Record and Run Settings dialog box, clear the Reinstall the application option.

Using the HP Mobile Web app

• The Object Spy and Highlight in Application (from the Object Spy) are not supported for mobile browsers.

• Checkpoints and output values cannot be added via the remote access window and must be added manually when editing test steps.
• If a test step navigates to an invalid URL, both the address bar and page are displayed as blank.

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

Running Web tests using the HP Mobile Web app

Supported in UFT12.51 Patch 1 only, and for GUI tests only.

• 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 micOK .Home .IsSiblingTab Browser("Welcome: Mercury Tours") .OpenNewTab

Using Chrome's mobile browser emulator

Supported in UFT12.51 Patch 1 only, and for GUI tests only.

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

• The Object Spy and Highlight in Application (from the Object Spy) are not supported for the emulator.

• Checkpoints and output values cannot be added during recording and must be added manually when editing test steps.

• Maintenance mode is not supported for the emulator.

• WebFile objects cannot be identified when replaying tests in the emulator.

Hybrid applications

The following features are not supported when testing hybrid applications:

Additional limitations:

Working with ALM

When using the Mobile Add-in with ALM:

• The Asset Comparison tool does not compare changes in the Record and Run Settings for Mobile tests.

• Test object icons for Mobile objects are not displayed in the Test Plan module or for object repositories saved in ALM.

Using Proxy servers

• 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

Localization

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

  Note: It is recommended to always use the period character as a decimal point, regardless of the locale of your operating system.

• Simulating events, such as an incoming phone call or SMS, is not supported.

• 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 Hybrid 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 Hybrid. 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:

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

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

Unsupported features

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: 

Send documentation feedback