Readme
HPE Mobile Center
Software Version: 2.20
Publication date: 27 January 2017
Software release: 27 January 2017
Mobile Center 2.20 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.01 or Mobile Center 2.01 Patch 1.
This Readme contains up-to-date information on Mobile Center 2.20 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.
The maximum file size that you can upload is 200 MB.
General
When connecting to Mobile Center over a proxy, it must allow WebSockets traffic in order to record in UFT.
Recording of the Left and Right arrow keys within apps is not supported. The recorded Up and Down arrow keys are translated into a scroll during replay. In addition, when working with the MC Browser, none of the arrows are recorded.
Android:
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 on Android 6 and above.
iOS:
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.
iOS:
Record and replay may fail for pages using dynamic URLs.
Workaround: Begin recording the page again to get the right MobileWebView.
Hybrid non-packaged apps are not supported on AWS.
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.
When a UFT test on an iOS device fails to run, the screenshot from the previous run is displayed.
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.
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.
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
Selecting devices in the Record and Run Settings in UFT
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"
Device information is not included in the HTML run results for Browser steps run on specific devices.
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.
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:
|
When highlighting a WebArea object on an Android device, the area is offset.
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
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.
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
The MobileView object is not recorded.
Instead, you can create it manually in the object repository and do the following:
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:
|
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. |
LongPress method |
Using the LongPress method with a duration longer than 2 on iOS devices is not supported. Workaround: Set the duration value to between 1 to 1.9. |
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
Using the MC Browser app with UFT
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 are not supported when running UFT on Windows Server 2012 R2.
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.
When running a test via UFT on a native browser or the MC Browser app, device logs are generated only when users enable the Device Metrics Logs in the Mobile tab of the Record and Run Settings in UFT for the specific device and select the Use settings in Mobile tab option in the Web tab of the Record and Run Settings dialog box.
When running a test on a Chrome browser, ensure that you disable the Chrome setting Gesture requirement for media playback before running tests containing WebVideo and WebAudio objects.
The .Play method is not supported for WebVideo and WebAudio objects on iOS devices.
Sometimes, when running a test of an application on a native browser, the test fails with a general run error.
Workaround: Add the initial URL in the Record and Run Settings in UFT.
UFT cannot record on iframe objects in iOS devices when the code of objects inside the iframe use document.write().
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. 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 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. |
LongPress method |
Using the LongPress method with a duration greater than 2 on Android packaged apps is not supported. Workaround: Enter a duration between 1 and 1.9. |
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.
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.
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 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"], } }
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.
If two or more devices on the Mobile Center server have the same name, and one of them is locked, you cannot run a test on the other device with the same name. An exception is thrown and the test cannot run.
Workaround: To prevent this, it is recommended to give each device in Mobile Center its own unique name.
The Web.Frame object is not supported in Mobile browsers.
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.
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.
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.
HPE Software cares about security.
In accordance with best practices, and to ensure integrity and authenticity, we sign the code binaries delivered to our customers. To do this, we use an HPE code signing certificate issued by a known certificate authority (CA).
Until now, that CA was Verisign. To enhance our business capabilities, we are soon moving to a new certificate issued by Comodo.
Comodo is a part of the Microsoft Trusted Root Certificate Program. You can find a list of all the Microsoft Trusted Root Certificate Program providers here: https://aka.ms/trustcertpartners.
The Comodo Root Certificate was added to this list a few years ago and is distributed via Windows updates. However, on computers with older versions of Windows, or without automatic Windows updates, Comodo may not be included as a trusted root certificate.
In such cases, we recommend manually configuring Comodo as a trusted root certificate. For details about Microsoft trust list distribution and configuration, see: https://technet.microsoft.com/en-gb/library/dn265983.aspx.
This HPE Software code signing change begins on January 1, 2017. We encourage all digital certificate owners currently trusted by Microsoft to review the list of trusted providers, and take action as necessary in advance.
© Copyright 2014-2017Hewlett Packard Enterprise Development LP
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.