StormRunner Functional

Transcription

1 StormRunner Functional Software Version: Powered by Mobile Center 2.70 Mobile Lab User Guide Go to HELP CENTER ONLINE Document Release Date: June 21, 2018 Software Release Date: June 2018

2 StormRunner Functional Legal Notices Disclaimer 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 Micro Focus, 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. Warranty 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. Restricted Rights Legend Contains Confidential Information. Except as specifically indicated otherwise, a valid license is required for possession, use or copying. Consistent with FAR and , 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 Micro Focus or one of its affiliates. 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. 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. StormRunner Functional (Powered by Mobile Center 2.70) Page 2 of 88

3 StormRunner Functional Contents StormRunner Functional 1 View and manage devices 6 Device display 6 Finding specific devices 7 Device management 8 View and manage connectors 9 Upgrade connectors 9 View and manage device reservations 10 Troubleshooting 11 Connect devices to StormRunner Functional 11 Supported devices 11 Certified devices 11 Physical device connectivity 17 Best practice guidelines for devices 18 Initial device setup 18 Android initial device configuration 19 ios initial device configuration 20 Before you start 20 Connector requirements 20 Install the connector on a Windows machine 21 Install the connector 21 Prepare devices 23 Connect devices and verify the connection 23 Start, stop, and restart the connector 25 Modify a connector 25 Enable localization 25 Troubleshoot the Windows connector 25 Uninstall a connector 27 Install the connector on a Linux machine 27 Install the connector 27 Connect and verify devices 29 Start and stop the connector 30 Enable localization 30 Uninstall the connector 31 Change the configuration of the connector 31 Install the connector on a Mac machine 32 Set up your Mac machine 32 Install the connector with Terminal 33 Verify device connection and connect devices 34 StormRunner Functional (Powered by Mobile Center 2.70) Page 3 of 88

4 StormRunner Functional Start or stop the Mac connector 35 Reconfigure the Mac connector 35 Uninstall the Mac connector 36 Troubleshooting and tips 36 Troubleshooting Android devices 36 Troubleshooting ios devices 38 View, upload, and manage apps 45 View app details 45 System apps 45 Options toolbar 46 Device provisioning information (ios only) 48 Upload an app 48 Troubleshooting 49 App packaging and signing 49 When to use a packaged app 49 Considerations when using non-packaged hybrid apps 49 StormRunner Functional packaging and signing tools 50 Certificates required when signing ios apps 50 Re-sign the Agent apps 51 More about the Agent apps 51 Obtain a development certificate of an Apple Developer account 51 Obtain a development provisioning profile 53 Re-sign and deploy the Agent apps 53 Package an Android app manually 60 Prerequisites 60 Run the enabler on your app 60 Enable remote content debugging of Android apps 62 Manually enable remote content debugging 62 Troubleshooting 64 Package an ios app manually on a Mac machine 64 Prerequisites 64 MC Enabler on Mac 65 Test generated files 69 Repackage apps for specific ios devices 69 MC Browser Apps 70 Gestures 72 Android native apps 72 Android hybrid apps 73 Android mobile web apps 73 ios native apps 74 StormRunner Functional (Powered by Mobile Center 2.70) Page 4 of 88

5 StormRunner Functional ios hybrid apps 74 ios mobile web apps 75 Apple Development Certificates and Provisioning Profiles 76 Generate a development certificate using a Mac 76 Obtain a development provisioning profile 80 Send Us Feedback 87 StormRunner Functional (Powered by Mobile Center 2.70) Page 5 of 88

6 View and manage devices View and manage devices On the MOBILE LAB tab, click DEVICES to view and manage the devices in your lab. These can be devices from a hosted lab, or a local device that you have connected to StormRunner Functional using the device connector. In this topic "Device display" below "Finding specific devices" on the next page "Device management" on page 8 "View and manage connectors" on page 9 "Upgrade connectors" on page 9 "View and manage device reservations" on page 10 "Troubleshooting " on page 11 Device display The following details are displayed in the Devices page and device card: Number of devices. The number of devices that match the current filter, out of the total number of connected devices. Operating System and version. Device name. Click the name to edit it. The default is the model number of the device. Manufacturer and Model name. StormRunner Functional (Powered by Mobile Center 2.70) Page 6 of 88

7 View and manage devices Connector latency. When you hover over the latency icon, StormRunner Functional shows the connector's latency. This is the latency between the client and the connector to which the device is connected, for example Remote view latency: 18 ms. For optimal remote screen viewer performance, select a device with good latency. The latency is considered good if it is less than 100 ms (green), mediocre if it ranges between 100 and 200 ms (yellow), poor if it ranges between 200 and 300 ms (red), and bad if it exceeds 300 ms (gray). Note: The latency display is not supported for Internet Explorer or Edge browsers. Reservations. The reservations for the device. For example, Available or Reserved by... Until. Click this section to view and create reservations. A triangular emblem at the bottom right of the device indicates its status: Reserved for you Reserved and in use by you Reserved for someone else Reserved and in use by someone else Note: To use ios devices with StormRunner Functional you must re-sign the Agent apps with a development certificate of an Apple Developer account. For more details, see "Re-sign the Agent apps" on page 51. Finding specific devices You can find a specific device in one of the following ways: Search. In the right pane, click the Search button. In the text box, specify the name, device ID, model, or manufacturer of the device. Filter. Use the left panel filter in the Devices page to limit what items are displayed, so that you can focus on the information that is important to you. Using the filter panel, you can specify your criteria in the following areas: OS. Operating System: Android, ios. Use the slider to select an OS version. Note that Windows Phone devices are not supported for StormRunner Functional. Features. Physical or Emulator device, and Phone or Tablet. Note that emulators are not supported for StormRunner Functional. Availability: Available Available devices StormRunner Functional (Powered by Mobile Center 2.70) Page 7 of 88

8 View and manage devices Reserved for me Reserved for others Disconnected Devices reserved for you, or that are currently in use by you. Devices that have been reserved for someone else, or are currently in use by someone else. Devices that were once connected to StormRunner Functional, but are no longer connected. Disconnected devices are displayed faded. Connector. The connector whose devices you want to display. Tip: Use the Clear link in the upper right corner of the filter panel, to remove all of your device filters. Device management When you hover over a specific device, the following options are displayed : Remove device. Remove a Disconnected device. To remove a device with another status, it must first be disconnected from StormRunner Functional. Unlock device. Release a device that is locked. For example, if a device was not automatically unlocked when the test finished, or if a specific device is required by another tester for performing some urgent validation of an app on a specific device model, the administrator may need to unlock a device. More Information: Opens the Device Information window. This window has three tabs: Details. Device information such as the agent version, connector, storage, OS, and so forth. Reservations. A list of current reservations for the device, and an option to create a new reservation. Actions. Interact with the device: Restart device: For an admin user, restarts all devices, including devices that are in use. Reconnect device: Re-launch the agent on the device. If this does not succeed, you may need to access the actual device. Tip: You can also access the Device Information window by clicking the lower section of a device card (for example, where it says "Available"). StormRunner Functional (Powered by Mobile Center 2.70) Page 8 of 88

9 View and manage devices View and manage connectors Click MOBILE LAB > CONNECTORS to see a list of all of the connectors and their properties. The grid displays the connector details such as its name and version, status, the machine hosting the connector, and the number of connected devices. Admin users can view all connectors. Testers can view only their own connectors. To add a new connector, click. Follow the instructions in the dialog boxes and wizards. For more details on installing connectors, see "Install the connector on a Windows machine" on page 21, "Install the connector on a Linux machine" on page 27 or "Install the connector on a Mac machine" on page 32. To view the devices associated with a specific connector, click the X Devices link in the row of the desired connector. The Devices view opens with the devices filtered for the selected connector. To remove a connector, hover over a connector name and click Remove. This button is only enabled when the connector is disconnected (The service has been stopped on the connector machine.) The button removes the connector from the connectors view only, it does not delete the physical connector installed on a remote machine. When a connector that has been removed is restarted, it will be displayed again in the grid. Upgrade connectors As your devices connect to the mobile lab, the lab detects the version of your connector. If the mobile lab detects a new recommended version of the connector, it saves it on your connector machine to the <installation>/upgrades folder. It automatically detects your operating system and downloads the relevant installation file package. The mobile lab sends a notification to the Device and Connector views indicating that you should upgrade your connector. In some cases, after a mobile lab upgrade, your connector will no longer meet the minimum version requirement. In this case you will be unable to connect to the mobile lab until you install the downloaded connector. Run the connector installation To upgrade your connector, you need to run the downloaded installation program. 1. Move the downloaded archive file to a temporary location. Do not run the setup from the upgrades folder. 2. Extract the archive file's contents and run the setup. The installation detects that you are running an upgrade and will retain all of the information from your previous connector installation. For details, see "Install the connector on a Windows machine" on page 21, "Install the connector on a Linux machine" on page 27 or "Install the connector on a Mac machine" on page Start the connector at the end of the installation. StormRunner Functional (Powered by Mobile Center 2.70) Page 9 of 88

10 View and manage devices 4. Verify that your connector upgrade succeeded. On the MOBILE LAB tab, click Connectors and check that there is no longer an upgrade notification for your connector. 5. For ios devices, you will need to re-sign all packaged apps, including the Launcher, Agent, and WebDriverAgent-Runner apps. For details, see "Re-sign the Agent apps" on page Delete the downloaded archive file after you have successfully upgraded your connector. View and manage device reservations Click MOBILE LAB>RESERVATIONS to view and manage reservations for a device. This page also provides details about the current reservations: Running Now, Coming Up (next 24 hours), and Future Reservations. By hovering over a reservation, you can edit or delete it. For a new reservation, click a device, it will be locked for you at that time. to open the Create Reservation window. Once you reserve Here are some guidelines to remember: You can specify an end time for your reservation, an open-ended reservation with no end time, or a reservation until the end of the test. By default, reservations are active for 30 minutes and extendable for 5 minute intervals. Your administrator can modify these values or edit specific reservations. After you reserve a device, the Reservations page indicates that you reserved it, and shows the start and end times. A triangular emblem at the bottom right of the device indicates its status. For details, see Device display - Reservations. StormRunner Functional (Powered by Mobile Center 2.70) Page 10 of 88

11 View and manage devices Troubleshooting Why can't I see all my devices? Check the filter panel to see what options are selected. StormRunner Functional displays only the items that fit the filter conditions. To display all items, select all the filter options and clear the search field of any text that you have entered. Connect devices to StormRunner Functional You can connect devices to StormRunner Functional by installing a device connector. The connector manages the physical USB connection to the device. Supported devices Before connecting a device, check that the operating system of your device is supported by StormRunner Functional. StormRunner Functional supports all devices that meet the following OS requirements: OS OS Version Android ios 7.x to the latest version, including Apple public beta versions. Certified devices StormRunner Functional supports any device that meets the minimum required OS. In addition, the most popular devices have been tested and verified with StormRunner Functional as follows: Android These devices have been tested and verified with StormRunner Functional: Smartphones Manufacturer Model Asus Asus ZenFone 2 Coolpad Coolpad S6 Google Nexus 5, 7, 9, 10 Google Pixel, Pixel 2, Pixel XL, Pixel XL 2 StormRunner Functional (Powered by Mobile Center 2.70) Page 11 of 88

12 View and manage devices Manufacturer HTC HTC HTC HTC Model One A9 One S, 8S One M8, M8X One M9 HTC HTC 10 HTC Desire D816H HTC Desire 620 HTC U Ultra * Huawei Huawei P8, P9, P10 Huawei Huawei Mate 8 Huawei Huawei Huawei Nexus 6P Huawei Ascend P7-L10 4G Known limitation: USB debugging needs to be activated each time you reconnect the device to StormRunner Functional. Huawei Huawei Ascend T1 Known limitation: The record and replay mechanisms are unable to identify certain objects in non-packaged apps. Huawei Huawei P10 Plus Known limitation: The record and replay mechanisms are unable to identify certain objects in non-packaged apps. Lenovo Lenovo Lenovo LG LG LG LG S90 S90-U Phab 2 Plus G3 16 GB D405h L90 G Flex2 G4 StormRunner Functional (Powered by Mobile Center 2.70) Page 12 of 88

13 View and manage devices Manufacturer LG LG LG LG Meizu* Meizu Model G5 G6 Nexus 5X LG V10, V20 Meizu MX4 Pro Meizu MX6 Meizu Meizu Pro 6 Meizu Motorola Motorola Motorola Motorola M3 Note Moto G (2nd Generation) Moto X Moto X (2nd Generation) Moto Z Motorola Nexus 6 Nubia Nubia Z9 mini OnePlus OnePlus One, OnePlus 2, OnePlus 3, OnePlus 5 OnePlus OnePlus Oppo Oppo OnePlus 3T, OnePlus 5T OnePlus X Oppo R7 Oppo R9sk Qiku Qiku 8681-A01 Samsung Galaxy Ace 3 Note: When connecting the device, the orientation should be set to portrait. Samsung Galaxy Note Samsung Galaxy Note 2, 3, 4, 5, 8, 10 Samsung Samsung Galaxy Note Edge N915F Galaxy S4, S5 StormRunner Functional (Powered by Mobile Center 2.70) Page 13 of 88

14 View and manage devices Manufacturer Samsung Model Galaxy S6, S6 Edge, S6 Edge Plus Samsung Galaxy A5, A5 (2017) Samsung Samsung Samsung Sony Sony Sony Galaxy A7, S7, S7 Edge Galaxy A8, A8 Plus, S8, S8 Plus Galaxy S9, S9 Plus Xperia Z Xperia Z3 Xperia Z5 Sony Xperia XZ F8331 * Sony Vivo Xperia XZs (G8232) Vivo X6S Xiaomi* Xiaomi Mi 3, 4, 5, 6 Xiaomi* Xiaomi* Xiaomi* Xiaomi Mi Max Xiaomi Mi Note Xiaomi Redmi Note Xiaomi* Xiaomi Redmi Note 3, 4 * See "Known Issues" on the next page. Tablets Manufacturer Model Google Nexus 7 Google Nexus 9 Google Nexus 10 HP HP Huawei HP Slate 7 extreme HP Slate S8-7600US 8-Inch Honor Tablet Huawei MediaPad T1 7.0 StormRunner Functional (Powered by Mobile Center 2.70) Page 14 of 88

15 View and manage devices Manufacturer Huawei Model MediaPad T Pro Lenovo Lenovo TAB 2 Samsung Galaxy Tab Samsung Galaxy Tab Samsung Galaxy Tab S2 9.7 Samsung Galaxy Tab 3 7" SM-T110 Samsung Galaxy Tab 3 Lite 7" Samsung Galaxy Tab Samsung Samsung Galaxy Tab S3 Galaxy Tab 4 8.0, T330 Samsung Galaxy Tab Samsung Galaxy Tab A 9.7 Samsung Soulycin Sony Teclast Xiaomi* Galaxy Note 10, Note Pro SM-P900 Soulycin T800 Xperia Z3 Teclast P98 Mi Pad Xiaomi* Mi Pad 2 * See the Known Issues section below. Known Issues On Xiaomi devices, you need to activate the Install app via USB in the Developer options settings. This requires you to have a registered Xiaomi account. On Xiaomi devices with the MIUI 8 operating system, you must manually enable USB Debugging under the Security settings to allow proper integration with StormRunner Functional. Due to a customized home screen package on devices such as the Sony Xperia F8331 or the HTC U Ultra, objects on the home page may not be recognized. Certain Meizu devices use a security option during installation, that prevents the packaging of apps. This security option also prevents the recording and replaying of packaged apps. Workaround: The security setting is per app. Disable the security option for the app that you are testing. StormRunner Functional (Powered by Mobile Center 2.70) Page 15 of 88

16 View and manage devices ios Note: Certain ios devices (iphone 4, ipad 2) are only supported for replay not record. When working with these devices, install apps manually before running them. For details, see "Repackage apps for specific ios devices" on page 69. When using native browsers and hybrid apps, the iphone 5 may be unstable. Integration with the AWS Device Farm is currently not supported for ios due to ADF ios connection restrictions. These devices have been tested and verified with StormRunner Functional: Smartphones Model iphone 5 iphone 5c iphone 5s iphone 5se iphone 6, 6 Plus iphone 6s, 6s Plus iphone 7, 7 Plus iphone 8, 8 Plus iphone X Tablets & ipods Model ipad Air ipad Air 2 ipad mini 2 Retina 16GB WiFi ipad mini 3 WiFi 16GB Gold ipad mini 4 WiFi 64GB StormRunner Functional (Powered by Mobile Center 2.70) Page 16 of 88

17 View and manage devices Tablets & ipods Model ipad 3 ipad 4 ipad (2017) ipod Touch (5th Gen) ipad Pro 9.7 inch ipad Pro 10.5 inch ipad Pro 12.9 inch Physical device connectivity Follow these guidelines when connecting your devices to a connector machine: USB cables Connect the devices through a genuine USB cable. A non-genuine cable may cause a failure in the connection. USB ports USB 2.0 ports are supported without limitations. USB 3.0 ports are supported with the following limitations: a. Both the USB port and USB hubs must be USB 3.0 compliant. b. Windows 7 does not have built-in USB 3.0 support. USB hubs USB hubs are supported for USB 2.0 and USB 3.0 with power adapters that comply with the Battery Charging (BC) 1.2 standard. The recommended models are: Small to medium deployments Large deployments The Plugable brand USB port hub with a 60 Watt power adapter. The Cambrionix brand, model PP15S USB hub. StormRunner Functional (Powered by Mobile Center 2.70) Page 17 of 88

18 View and manage devices Best practice guidelines for devices Place the devices in a cool space to prevent overheating. Reduce the screen brightness of devices to the minimum, to reduce power consumption and heat generation. Place the devices in a vertical position to facilitate a smooth change in orientation (portrait to landscape) in the remote device view. Disconnect the devices from their power source when not in use, to allow a full battery charge cycle. We recommend that you perform a full charge cycle on a weekly basis. Swollen Batteries Swollen batteries are a common problem with any device using lithium-ion batteries. It can affect mobile devices, laptops, smart watches, and even car batteries. The primary causes for swollen batteries in mobile devices are: Excessive heat: If the device is used extensively, it generates heat that may cause the battery to swell. Over-charging: Continuing to charge the device even after it is fully charged, can cause the battery to swell. Old age or a defective battery: A device that is 2-3 years old, may also show signs of a swollen battery. To avoid swollen batteries for devices under test, follow these guidelines: Reduce the device's screen brightness to minimum. Store the device in a cool, well-ventilated location. Use certified USB hubs that can provide adequate charging power. Perform manual battery charging cycles as part of the device maintenance, by disconnecting the device from Mobile Center and letting the battery drain completely. Make sure the battery is within a reasonable time of its recommended life, as specified by the manufacturer and covered by the warranty. Once a week, perform a visual inspection of the battery, and remove any devices with swollen batteries. See also: "Install the connector on a Windows machine" on page 21 "Install the connector on a Linux machine" on page 27 "Install the connector on a Mac machine" on page 32 Initial device setup This topic details the steps that you need to perform before you connect a device for the first time. StormRunner Functional (Powered by Mobile Center 2.70) Page 18 of 88

19 View and manage devices Android initial device configuration When connecting the device for the first time, there are a few steps that you need to perform on each device that you intend to connect to StormRunner Functional. After the initial connection has been set up, the device is "plug-and-play". 1. Check that your devices are supported by StormRunner Functional. For details, see supported devices. 2. Enable Developer options. In general, on most devices with Android 4.2 and higher, you can do this by navigating to Settings > About phone and tapping the Build number seven times. 3. Under Developer options, enable the following: Stay awake USB debugging Allow mock locations To enable GPS simulation when using Android 6.0 and higher, set the mock location app to MC Agent after connecting the device StormRunner Functional. (Settings > Developer options > Select mock location app). If you reinstall the Agent for any reason, you will need to repeat this step. 4. Under Developer options, disable Verify apps via USB (available in Android 4.20 and higher). StormRunner Functional (Powered by Mobile Center 2.70) Page 19 of 88

20 View and manage devices 5. Enable the following additional settings: In Settings > Display, select Auto rotate screen. If you simulate GPS events during your test, prevent collisions with your real location from WiFi/3G/LTE by enabling GPS only in Settings > Location > Mode. 6. If required by the apps being tested, make sure that there is an active Internet connection. ios initial device configuration Before you connect a device to StormRunner Functional, you need to re-sign the following apps: Agent Agent Launcher WebDriverAgent Runner-Runner WebDriverAgentRunner-Runner_xcode9 Re-sign them with a development certificate from an Apple Developer Account, and a development provisioning profile belonging to the same account. These provide the identity of the developer, and the list of devices on which distribution of the app is allowed. For details on how to re-sign these apps, see "Re-sign the Agent apps" on page 51. The first time that you connect a device, perform the following steps on each device you intend to connect to StormRunner Functional. These are one-time settings. After the initial connection has been set up, the device is "plug-and-play". 1. If the Auto-lock option is set to on, in Settings > General > Auto-lock set the maximum time for preventing auto-lock. 2. Set your preferences (such as icloud) to avoid unnecessary pop-ups. 3. If required by the apps that you are testing, make sure that there is an active Internet connection. 4. For ios 8 and higher, make sure UI Automation is enabled (Settings > Developer > UI Automation). If you perform this step after connecting the device, you will need to restart the device, or unplug it and plug it in again. 5. Turn off the passcode on the device. 6. For Safari browser support: Enable Javascript and Web Inspector in Settings > Safari > Advanced. 7. Make sure that the Display Zoom, under the Display and Brightness settings, is set to Standard, and not Zoomed. Before you start Connector requirements When installing the Device Connector, make sure that the connector machine meets the following requirements: StormRunner Functional (Powered by Mobile Center 2.70) Page 20 of 88

21 View and manage devices Linux Hardware: 2 GB RAM 2 GB disk space Operating System: Red Hat Enterprise Linux minimal x64 workstation installation of versions 6.5, 6.6, 6.7, 6.9, 7.0, 7.1, 7.2, or 7.4 CentOS minimal installation of versions 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, or 7.4 Windows Hardware: 2 GB RAM 2 GB disk space Operating System: Windows Server 2008 R2 SP1 64-bit Windows Server 2012 R2 Windows bit Windows 10 MacOS Hardware: 2 GB RAM 2 GB disk space Operating Systems: OS X and later Sierra , 10.12, , and Maximum number of connected devices per connector: 50 devices Install the connector on a Windows machine The Device Connector is a standalone component for connecting devices to your mobile lab. For details on how to see all of your connectors, see "View and manage connectors" on page 9 Install the connector To install the connector: 1. For information on the recommended system requirements, see connector requirements. 2. If your connector machine accesses the Internet though a proxy, make sure that the HTTP_PROXY and HTTPS_PROXY system environment variables are properly defined. StormRunner Functional (Powered by Mobile Center 2.70) Page 21 of 88

22 View and manage devices 3. Click MOBILE LAB > CONNECTORS and click. 4. In the Add Device Connector dialog box, select the Windows operating system and click Download. 5. Click Generate Credentials. Save these credentials for when you run the connector installation. 6. Extract the contents of the connector installation file to your computer. 7. Open the folder that you extracted above, and locate the.exe file. Double-click on the file to open the Installation wizard. Read the contents and click Next. 8. Fill in the information or answer the questions in each of the Installation wizard pages following these guidelines: Mobile lab Mobile lab specifications: Connect to Mobile Center. For connecting to the lab via an on-premises Mobile Center server, enter the IP address or the fully qualified domain name (FQDN) of the Mobile Center server machine. If the server was installed using an FQDN, use that same name here. If the server was configured to work without SSL, disable the Use SSL option and specify the non-secure port, 8080 by default. Connect to StormRunner Functional (SRF). To access the lab via SRF, paste your credentials in the Credentials to StormRunner Functional (SRF) field. To obtain cloud credentials, open StormRunner Functional. In the MOBILE LAB > CONNECTORS tab, click. In the Add Device Connector dialog box, click Generate Credentials. For details on how to change the configuration after the installation, see "Modify a connector" on page 25. If connecting over a proxy, select Enable in the proxy section, and specify the server, port, and credentials if required. Connector configuration Provide a meaningful name for the connector, as this will allow you to effectively filter devices based on connector names. Enter the Connector's IP address or FQDN. Indicate whether or not the connector should be private. A private connector only allows the current user and the administrator access to the connector's devices. Caution: To insure integrity and confidentiality of the information stored with StormRunner Functional, we strongly recommend that you incorporate filesystem monitoring on the installation and temporary folders. StormRunner Functional (Powered by Mobile Center 2.70) Page 22 of 88

23 View and manage devices Prepare devices Set up your Windows machine to detect the devices you want to connect to StormRunner Functional by performing the following steps: ios devices 1. Make sure you have itunes installed on your computer. For details, see 2. If you haven't already done so, follow the steps for setting up ios devices. Android devices 1. Download the USB driver for your devices. See for a list of links to Original Equipment Manufacturers (OEM) USB Drivers. Alternatively, search the Web for a USB driver for Windows, for your device. For Google Nexus devices, you must download the Google USB driver. 2. Extract the contents of the downloaded driver's archive file. 3. Connect the device(s) to your machine and install the driver per Windows version as described on the Install OEM USB Drivers page. Note: When you connect the device through a USB port, a security message may ask you to allow USB debugging or trust the connected computer. Accept the warning. 4. If you haven't already done so, follow the steps for the initial configuration of Android devices. Connect devices and verify the connection 1. Connect your devices to your computer via USB cable. Accept all notification, trust, or location pop-ups that may be displayed when you connect a device. 2. When the connector is running, the following items are automatically installed on the devices plugged into the connector machine: Remote viewer services The Agent application Wait until the Agent is running before interacting with the device. If the Agent crashes, try to unplug the device and then plug it in again. For additional troubleshooting information, see "Troubleshoot the Windows connector" on page 25. Tip: If you unplug a device, wait 5 seconds before reconnecting it to allow the system to stabilize. StormRunner Functional (Powered by Mobile Center 2.70) Page 23 of 88

24 View and manage devices 3. If the Agent app does not start up after you connect the devices, check if the devices are recognized: Verify Android devices Navigate to the <Windows Connector folder>\android-sdk-windows\platform-tools folder and run adb at a command prompt. adb devices All your connected devices should be listed. If your device is listed as unauthorized, check the device and accept any security pop-ups. If your device is not listed, or if there are no devices listed, check for the following: o o o A hardware problem. The USB port may not be working. Improper Installation of Windows driver. Select the driver inf file in the File Explorer and select Install from the right-click menu. Incorrect drivers for Android devices. Check the vendor website to see that you have the most recent version of the driver. Verify ios devices To verify ios devices: a. Open a command prompt window b. Navigate to the <Windows Connector folder>\libimobiledevice\windows-amd64 folder c. Run the idevice_id command: idevice_id l The result of this command should be a list of devices IDs (UDID). If there are no devices listed when a device is connected to the USB port, check for the following: A hardware problem. The USB port may not be working. Incorrect version of itunes. Check that you are using the most up-to-date version of itunes. UI Automation is not enabled. For ios 8.x and above with a Developer signed Agent app, enable UI Automation in Settings > Developer > Enable UI Automation. Disconnect the device, wait 5 seconds, and then reconnect it. Additional considerations for ios devices ios 8.x and above If you have not already done so, enable UI Automation on the device in Settings >Developer> Enable UI Automation. Disconnect the device, wait 5 seconds, and then reconnect it. StormRunner Functional (Powered by Mobile Center 2.70) Page 24 of 88

25 View and manage devices Important Note for ios and above: Users who install apps signed with an Enterprise certificate (that do not use a Mobile Device Management (MDM) solution) will be prompted to trust the Enterprise developer the first time the app is installed. To trust the profile, go to Settings > General > Device Management, select the Enterprise developer profile, and trust it. These actions can be performed remotely on the device. All users who install your enterprise-signed app for the first time will also need an internet connection. Once an Enterprise developer profile has been trusted on a device, additional apps with the same profile do not need to be trusted again, provided that the devices on which they are opened are connected to the internet. If the Enterprise developer profile of the application under test is not trusted, the Agent will not be able to open the app and will issue a 1009 Error: "Cannot communicate with AUT ". Start, stop, and restart the connector When the installation is complete, the setup program prompts you to start the connector service. If you chose not to start the connector service after installing it, you can perform a manual Start, Stop, and Restart from the Services console, or directly from the machine's Start menu: Start > Mobile Center Connector > Start service Start > Mobile Center Connector > Stop service Start > Mobile Center Connector > Restart service Modify a connector If you need to modify your connector details, for example to switch between an on-premises Mobile Center server or the StormRunner Functional mobile lab, or to change the connector port, you can modify them using the Modify configuration tool. To access the tool, select Start > Mobile Center Connector > Modify configuration. The configuration wizard opens. When running, the wizard stops the Connector service. The wizard's final page prompts you to start the service again. Enable localization To display system apps (apps that are used to run the device itself) in a supported language other than English, after installing the connector, navigate to <path to your Windows connector folder>\conf\connector.properties and uncomment the following line in the file: ENABLE_LOCALIZATION=true Troubleshoot the Windows connector This section provides some tips and guidelines for getting your connector to work. StormRunner Functional (Powered by Mobile Center 2.70) Page 25 of 88

26 View and manage devices Devices do not appear after starting the connector If the Windows connector started successfully, but you don't see devices in the StormRunner Functional lab: Verify that your machine can detect your device. Check the connector.log file located in <Windows connector folder>\connector\log folder and make sure that there are no "connection refused" messages or other errors. App features are blocked by a firewall If, during installation, Windows issues the warning Windows Firewall has blocked some features of this app, click Allow access or contact your system administrator. When this message is issued, the current Connector installation is aborted. Remote device view is blocked If you cannot view a remote device in StormRunner Functional, this may be a result of the antivirus software installed on the machine. For example, McAfee Host Intrusion Prevention blocks access. Workaround: Disable the antivirus while running the test. Remote access or recording fails The Windows connector started successfully and the device is displayed in the StormRunner Functional lab, but either remote access or recording are not working. In some cases, StormRunner Functional will issue a message with the problematic IP address and port. In other instances, you may receive a "connection refused" message, indicating an IP address problem: Check that the IP address (shown in the error message) that StormRunner Functional is trying to reach, is the correct one for your connector machine. To show the IP address of your machine, open a command line window and type ipconfig. If, for example, you were connected to a different network or IP when you installed the connector, you will need to run the Modify configuration utility under Start > Mobile Center Connector and enter the new IP of the connector machine. Check that the port shown in the error message, is open for incoming traffic on the connector machine. Proxy and SSL Proxy machines that require credentials are not supported. If you have a device connected when you install the connector using a proxy server, the devices will not appear in the Mobile Lab. Workaround: Connect the devices after you install the connector software. Connection refused or connection timed out message When trying to run the installation, if the setup program issues a "connection refused" or "connection timed out" warning: StormRunner Functional (Powered by Mobile Center 2.70) Page 26 of 88

27 View and manage devices Check that you are using the most up-to-date version of the connector, and that there are no notifications on the Device and Connector pages of the mobile lab, indicating that you should upgrade your connector. Port conflicts prevent the connector from starting If an existing service running on your machine is claiming the port on which the connector runs (Default: 8080), there will be a conflict, and the connector will not start up. To change the port, run the Modify configuration utility under the Start > Mobile Center Connector menu. Prior installations of Android SDK If you installed the Android SDK for a specific user (not the SYSTEM user), the Windows connector setup program may be unable to install the Agent, since the manually installed SDK is not accessible from the SYSTEM user. Workaround: Reinstall the Android SDK as a SYSTEM user, and delete the ANDROID_HOME environment variable. Uninstall a connector You can uninstall the connector via the Start menu or through the standard Windows Programs and Features > Uninstall or change a program interface. Install the connector on a Linux machine The Device Connector is a standalone component for connecting devices to StormRunner Functional. For details on how to see all of your connectors, see "View and manage connectors" on page 9 Install the connector To install the connector: 1. For information on the recommended system requirements, see connector requirements. 2. If your connector machine accesses the Internet though a proxy, make sure that the HTTP_PROXY and HTTPS_PROXY system environment variables are properly defined. 3. Click MOBILE LAB > CONNECTORS and click. 4. In the Add Device Connector dialog box, select the Linux operating system and click Download. 5. Click Generate Credentials. Save these credentials for when you run the connector installation. 1. On your Linux machine, log in as root or as a user in the Linux sudoers file. 2. Copy the connector installation file to your Linux machine and extract the contents: unzip <Name of connector installation file>.zip d <Target directory name> StormRunner Functional (Powered by Mobile Center 2.70) Page 27 of 88

28 View and manage devices 3. Change directory to the Target directory: cd <Target directory name> 4. Run the connector installer:./<install_connector-x64 file name>.bin 5. Read the License Agreement, and select Y to accept the terms and proceed with the installation. Fill in the information or answer the questions in each of the Installation sections following these guidelines: User configuration Enter y to use an existing Linux user, or enter n to use the default new user "hpmc". Enter the password for this user. Mobile Lab Mobile lab specifications: Connect to Mobile Center. For connecting to the lab via an on-premises Mobile Center server, enter the IP address or the fully qualified domain name (FQDN) of the Mobile Center server machine. If the server was installed using an FQDN, use that same name here. If the server that you are connecting to was configured to work without SSL, you need to also install the connector with a non-secure connection. For non-ssl, enter n to indicate that the selected port is not an SSL port. When prompted for a port, note that the default secure port using SSL is For a non-secure server, the default is port Connect to StormRunner Functional (SRF). To access the lab via SRF, paste your credentials when prompted. To obtain cloud credentials, open StormRunner Functional. In MOBILE LAB> CONNECTORS, click. In the Add Device Connector dialog box, click Generate Credentials. For details on how to change the configuration after the installation, see "Change the configuration of the connector" on page 31. If connecting over a proxy, enter y and specify the proxy details. Connector configuration Provide a meaningful name for the connector, as this will allow you to effectively filter devices based on connector names. Enter the Connector's IP address or FQDN. Specify the connector port or use the default (8080), and the port to be used internally (Default 8081). Indicate whether or not the connector should be private. A private connector only allows the current user and the administrator access to the connector's devices. Review the pre-installation summary and press Enter to continue with the installation of the connector. StormRunner Functional (Powered by Mobile Center 2.70) Page 28 of 88

29 View and manage devices Caution: To insure integrity and confidentiality of the information stored with StormRunner Functional, we strongly recommend that you incorporate filesystem monitoring on the installation and temporary folders. Connect and verify devices 1. If you have not already done so, make sure to follow the steps for initial device configuration when connecting Android and ios devices. 2. Connect the device to the connector machine using a USB cable. On some devices, when you connect the device, there may be notification, trust, or location pop-ups. Accept these pop-ups. 3. Wait until the Agent is running on the device. 4. If the Agent does not start up on the device, verify that the devices are recognized: Android devices Run the following command on the Linux connector machine (If you are a root user, change directory to /opt/mc/connector/android-sdk-linux/platform-tools): adb devices All your connected devices should be listed. The status of the device should be "device" and not any other state, for example "unauthorized". Tip: If you are connecting with a C-Type USB device, such as One Plus, Nexus 5, etc, the idvendor value may not have been recognized. Workaround: Run dmesg to obtain the idvendor value, beginning with 0x. Run sudo to switch to the hpmc user provided during installation. Run the ~/add_android_vendor.sh <idvendor> script. ios devices a. Navigate to: /opt/mc/connector/libimobiledevice/linux-amd64/ b. Run idevice_id l The result of this command should be a list of devices IDs (UDID). If the command returns an empty result or ERROR message, try the following: a. On the connector machine, log in as root or as a user on the Linux sudoers list. b. Locate the process ID of usbmuxd " ps aux grep '[u]sbmuxd' StormRunner Functional (Powered by Mobile Center 2.70) Page 29 of 88

30 View and manage devices c. Kill the process: kill 9 <processid> d. Start usbmuxd again: usbmuxd e. Run idevice_id l again to see if the device is recognized. If the devices are connected correctly, try to manually launch the MC Launcher app. If you see an Untrusted App Developer notification: Click Trust. Disconnect the device. Wait 5 seconds and then reconnect the device. Additional considerations for ios devices ios 8.x and higher If you have not already done so, enable UI Automation on the device in Settings >Developer> Enable UI Automation. Disconnect the device, wait 5 seconds, and then reconnect it. Important Note for ios and higher Users who install apps signed with an Enterprise certificate (that do not use a Mobile Device Management (MDM) solution) will be prompted to trust the Enterprise developer the first time the app is installed. To trust the profile, go to Settings > General > Device Management, select the Enterprise developer profile, and trust it. These actions can be performed remotely on the device. All users who install your enterprise-signed app for the first time will also need an internet connection. Once an Enterprise developer profile has been trusted on a device, additional apps with the same profile do not need to be trusted again, provided that the devices on which they are opened are connected to the internet. If the Enterprise developer profile of the application under test is not trusted, the Agent will not be able to open the app and a 1009 Error: "Cannot communicate with AUT " will result. Start and stop the connector You can stop and start the connector with the following commands: To start the connector: service hpmc start To stop the connector: service hpmc stop To restart the connector: service hpmc restart Enable localization To display system apps (apps that are used to run the device itself) in a supported language other than English, after installing the connector, navigate to /opt/mc/connector/conf/connector.properties and uncomment the following line in the file: ENABLE_LOCALIZATION=true StormRunner Functional (Powered by Mobile Center 2.70) Page 30 of 88

31 View and manage devices Uninstall the connector You can uninstall the connector for Linux as follows: 1. Log into the Linux connector machine as root user, or as a user in the Linux sudoers file. 2. Change directory to the connector installation directory: cd <path to installation folder> (Default /opt/mc/) 3. Run the uninstall script by entering the following command:./mc_uninstall 4. Press enter to proceed with uninstalling the StormRunner Functional connector. Change the configuration of the connector If you need to modify your connector details, for example to switch between an on-premises Mobile Center server or the StormRunner Functional mobile lab, of if you need to change the connector details, you can use the update tool. When you run the tool, you can update any of the following : On-premises Mobile Center server details: IP address or FQDN Port Secure or non secure connection (SSL) Proxy information StormRunner Functional Mobile Lab: Credentials Connector details: Credentials Connector name Connector IP address Connector port To change the configuration of the connector: 1. On the connector machine, log in as root or as a user in the Linux sudoers file. 2. Navigate to your connector installation directory. Default opt/mc/ 3. Run the following command:./mc_update 4. When prompted, specify the new details. 5. Restart the connector at the end of the process to allow the change to take effect. StormRunner Functional (Powered by Mobile Center 2.70) Page 31 of 88

32 View and manage devices Install the connector on a Mac machine The Device Connector is a standalone component for connecting devices to StormRunner Functional. This section describes how to install the connector on a Mac machine for testing ios or Android phones. For details on how to see all of your connectors, see "View and manage connectors" on page 9 For information on the recommended system requirements see connector requirements. Set up your Mac machine 1. Set up your Mac machine to detect the devices you want to connect to StormRunner Functional by performing the following steps: ios devices a. Check that you have an updated version of itunes on your Mac. b. If you haven't already done so, follow the steps for setting up ios devices. Android devices a. Install the USB drivers for your devices. Each device manufacturer has its own USB drivers for Mac. Follow the instructions from the device manufacturer. See for a list of links to Original Equipment Manufacturers (OEM) USB Drivers. b. If you haven't already done so, follow the steps for the initial configuration of Android devices. 2. Connect your devices to your machine via a USB port. For a new installation of Mac OS, make sure that you open itunes before plugging in a device. On some devices, when you connect the device via USB, the device issues a security alert. Accept the warning. Tip: Some phones have USB settings (Swipe left on the app list, tap Settings, and look for a USB option) that allow the data connection to be enabled separately from the charging connection. If your phone has this option, check the settings to ensure your USB data connection is enabled. 3. Download the Mac connector : a. Click MOBILE LAB > CONNECTORS and click. b. In the Add Device Connector dialog box, select the macos operating system and click Download. c. Click Generate Credentials. Download the credentials file for when you run the connector installation. StormRunner Functional (Powered by Mobile Center 2.70) Page 32 of 88

33 View and manage devices 4. If your connector machine accesses the Internet though a proxy, make sure that the HTTP_PROXY and HTTPS_PROXY system environment variables are properly defined. Install the connector with Terminal To install the connector: 1. Log in as root or admin user. If you are using macos Sierra, you must log in as root user, by running sudo -i in the Terminal window. 2. Extract the contents of <Name of macos connector installation file>.zip. 3. Run the following command to move the CONNECTOR folder to the Applications folder: cp r /desktop/connector/applications 4. Run the following command to get permissions to run the installation file: chmod -R 777 /Applications/CONNECTOR 5. Navigate to the folder: Aplications/CONNECTOR/install.app/Contents/MacOS 6. Run./install. The wizard is launched. Press Enter and Y/N when prompted to do so, for example to accept the license agreement. 7. Proceed through the wizard following these guidelines: Mobile lab Mobile lab specifications: Connect to Mobile Center. For connecting to the lab via an on-premises Mobile Center server, enter the IP address or the fully qualified domain name (FQDN) of the Mobile Center server machine. If the server was installed using an FQDN, use that same name here. If the server was configured to work without SSL, disable the Use SSL option and specify the non-secure port, 8080 by default. Connect to StormRunner Functional (SRF). To access the lab via SRF, upload the credentials file in the Credentials to StormRunner Functional (SRF). field. To obtain cloud credentials, open StormRunner Functional. In the MOBILE LAB tab, click. In the Add Device Connector dialog box, click Generate Credentials. For details on how to change the configuration after the installation, see "Reconfigure the Mac connector" on page 35. If connecting over a proxy, select Enable in the proxy section, and specify the server, port, and credentials. Connector configuration StormRunner Functional (Powered by Mobile Center 2.70) Page 33 of 88

34 View and manage devices Mobile lab Enter the Connector's IP address or FQDN. The FQDN must begin with an English alphabetical character. FQDNs beginning with numbers are not supported. Provide a meaningful name for the connector, as this will allow you to effectively filter devices based on connector names. In the Connector configuration screen, indicate whether or not the connector should be private. A private connector only allows the current user and the administrator access to the connector's devices. Verify device connection and connect devices After the installation, if you have Xcode installed, you can check whether the machine recognizes an ios device using the instruments command: instruments -s devices The result of this command should be a list of devices IDs (UDID). If your device is not listed when connected to the USB port, this may mean that: The USB port is not working (hardware problem). You are not using the most up-to-date version of itunes. You should upgrade your version of itunes To connect ios devices through a Mac connector to StormRunner Functional: 1. Codesign the Agent apps (HP4M-Agent.ipa, and HPMC-AgentLauncher.ipa WebDriverAgentRunner-Runner.ipa and WebDriverAgentRunner-Runner_xcode9.ipa) using MC Enabler. 2. Rename the files by removing -Codesigned from the file name. For example, the Agent file should be renamed from HP4M-Agent-Codesigned.ipa to HP4M-Agent.ipa 3. Copy the re-signed apps over to the Agent folder on the Mac connector machine. 4. Run the following commands in the Agent folder: sudo chown hpmc HP4M-Agent.ipa sudo chown hpmc HPMC-AgentLauncher.ipa sudo chown hpmc WebDriverAgentRunner-Runner.ipa sudo chown hpmc WebDriverAgentRunner-Runner_xcode9.ipa StormRunner Functional (Powered by Mobile Center 2.70) Page 34 of 88

35 View and manage devices sudo chmod 755* 5. If the Mac connector is running, restart it. Caution: To insure integrity and confidentiality of the information stored with StormRunner Functional, we strongly recommend that you incorporate filesystem monitoring on the installation and temporary folders. Start or stop the Mac connector When you run the installation, by default the Mac connector is installed as a Mac service. You are prompted to start this service at the end of the installation. To stop the service, perform an uninstall. If you chose not to start the service at the conclusion of the installation, you can stop and start the connector at a later time as follows: From the Terminal window, change directory to /opt/mc/scripts and run: To start the connector: sudo launchctl load /Library/LaunchDaemons/com.hpe.mobilecenter.plist To stop the connector: sudo launchctl unload /Library/LaunchDaemons/com.hpe.mobilecenter.plist Note: These commands require root access. Reconfigure the Mac connector If you need to modify your connector details, for example to switch between an on-premises Mobile Center server or the StormRunner Functional mobile lab, of if you need to change the connector details, you can reconfigure the connector s settings without having to reinstall it. To reconfigure from the Mac OS: Double-click MC_Update in the machine's Applications > Mobile Center Connector folder. To reconfigure from a terminal: 1. Change directory to the installation folder. cd /opt/mc/installation/ 2. Run the upgrade script:./mc_update.command StormRunner Functional (Powered by Mobile Center 2.70) Page 35 of 88

36 View and manage devices Uninstall the Mac connector You can remove the connector for Mac by running the uninstall program on the Mac OS machine, or via terminal. The uninstall requires root or admin permissions. Note: If you installed the connector via terminal (PuTTY), you can only uninstall it from a terminal. To uninstall from the Mac OS: Double-click MC_Uninstall in the machine's Applications > Mobile Center Connector folder. To uninstall from a terminal window: 1. Change directory to the installation folder. cd /opt/mc/installation/ 2. Run the uninstall script:./mc_uninstall.command Troubleshooting and tips Troubleshooting Android devices This section offers solutions for Android-specific issues. Samsung device disconnects after 24 hours Certain Samsung devices running Android 7.0, use a battery optimization tool that causes this issue. If you encounter disconnection issues, perform the following: 1. Open Settings > Apps. 2. Click the More button (three vertical dots) and select Special Access. 3. In the Special Access area, choose Optimize battery usage. 4. In the Optimize battery usage area, choose All apps. 5. Scroll to the MC Agent app and switch it to Off. Device disconnects on specific devices after several seconds Certain Android devices, primarily those manufactured by Chinese vendors, use a security tool that affects the memory and battery usage. If you encounter disconnection issues, perform the following: 1. Enable Autostart for the MC Agent: Open the device s Security app from the Home page, and click Permissions. Select Autostart, find the MC Agent app, and enable it. 2. Turn off the battery saver: Open the device s Security app from the Home page, and click Battery. Set Battery saver to Off. Alternatively, to work with the battery saver on, select App battery saver and find the MC Agent app. Select No Restrictions. StormRunner Functional (Powered by Mobile Center 2.70) Page 36 of 88

37 View and manage devices App crashes end recording sessions If an app crashes or is terminated forcefully during a recording session, your actions will no longer be recorded even if you restart the app. You must re-record your session from the beginning. Dexguard security You can work with Dexguard security by compiling your app in Dexguard. Follow these steps: 1. Upload your original, packaged or non-packaged app to StormRunner Functional. 2. Record a test on the original app. 3. Recompile the app in Dexguard with the following options: "-keepresourcexmlattributenames **/id -keepresources id/*" 4. Upload the Dexguard-wrapped version of the app to StormRunner Functional. 5. Replay the testing using the Dexguard-wrapped version of the app. iframe failures Cross-domain iframe calls are not supported. For example, if your test uses an iframe that points to a web page in another domain, it will fail. App installation failures due to insufficient storage An Android limitation may cause a device to issue the message INSTALL_FAILED_INSUFFICIENT_ STORAGE while installing certain apps. Workaround: Restart the device. Device hanging when in remote screen viewer If your device hangs when trying to open an app, it may be caused by the app's secure layout flag. Workaround: Manually remove the secure layout flag. If you are testing a packaged app, see "Package an Android app manually" on page 60 for more details. For non-packaged apps, see "Manually enable remote content debugging " on page 62. Replay issues with hybrid apps When working with hybrid non-packaged apps, make sure that remote content debugging is enabled. For details, see "Enable remote content debugging of Android apps" on page 62. Good Connect client issues In order to work in the remote view on a device with a Good Connect client, you must set the Prevent Android Screen Capture policy to Off. The release version of and above is required for the policy to take effect. For details, see the Blackberry Knowledge Base article. StormRunner Functional (Powered by Mobile Center 2.70) Page 37 of 88

38 View and manage devices Troubleshooting ios devices ios device best practices Are there version-specific guidelines for ios devices? For ios 7 devices, it is not recommended to manually delete the Agent and Agent Launcher apps. If you do so, when you reconnect the device, a black screen will be displayed and the device will not available to users. To resolve this, restart the device. For devices running ios < 11, record/replay is not supported for UIWebView in XC mode. For ios 8.x and above, with a Developer signed Agent app: On the device, enable UI Automation in Settings > Developer > Enable UI Automation. Disconnect the device, wait 5 seconds, and then reconnect it. How do I automatically dismiss alerts? If your record or replay session is interrupted due to alert pop-ups that need to be dismissed, set the automatic alert dismiss option in the following way: 1. On the ios Agent, tap seven times on the Micro Focus icon. 2. Navigate to the VNC tab. 3. Switch on Automatic Alert Dismiss. This dismisses a single active pop-up dialog before the recording, replay, or launching of your app. StormRunner Functional (Powered by Mobile Center 2.70) Page 38 of 88

39 View and manage devices What should I know about app certificates? When installing an app that is already installed on the device, be sure to use the same developer certificate as the installed app. If the certificates do not match, the installation will fail. For example, if the app on the device is signed with Certificate A you cannot install the same app signed with Certificate B. The same applies if an app on the device is signed with an Enterprise certificate and you want to install the same app signed with a Developer certificate. Workaround: If the certificates do not match, first remove the app that is already installed on the device, and then reinstall the app with the other certificate onto your device. Note: Non-packaged hybrid apps signed with an Enterprise certificate are not supported. How do I resolve the "Certificate was signed by an unknown authority" issue when trying to code sign an app? When code-signing an app on a Macintosh, an Apple trusted authority certificate must be installed so that Apple can be recognized as a trusted authority by the Keychain Access app. If an Apple trusted authority certificate is not installed, any certificate issued by Apple will be shown as invalid. For more details, see the Apple Developer documentation. If a certificate is shown as invalid (red) in the Keychain Access app, followed by an error This certificate was signed by an unknown authority, you need to download and install a new certificate from the Apple Worldwide Developer Relations Certificate Authority. Install the certificate as follows: 1. Download the certificate from the Apple Developer support site. 2. Double-click the certificate. 3. Verify that it is valid (green) and does not display the following error: This certificate was signed by an unknown authority. How can I prevent my ios device from locking itself during replay? If the device was set up to lock its screen, or sleep, after a certain interval, this can affect your replay. To prevent the screen from locking up, make sure that your Display Settings for Sleep are set to "Never". StormRunner Functional (Powered by Mobile Center 2.70) Page 39 of 88

40 View and manage devices If your device continues to sleep and lock its screen, you can apply a workaround to send a pseudoaction to the device to prevent it from sleeping, and to keep the device unlocked. The pseudo-action used by this workaround, is the Volume up and Volume down controls. It will not affect the steps in your test, but you will see the control briefly at certain intervals, on the device screen. To set up this action: 1. On your device, open the Agent application. 2. On the agent logo, tap the screen seven times. The advanced developer bar becomes visible at the bottom of the screen. 3. Click the bottom right button, VNC, to display the VNC server details settings. 4. Click in the right value column for the Avoid Device Lock feature. 5. Select an interval in which to send the pseudo-action to the device, from 1 to 5 minutes. Where do I find the log files for my ios devices? You can get crash logs for a device in a number of ways: Method Locate file on Linux connector machine File Location 1. Change directory to the linux-amd64 directory: cd /opt/mc/libimobiledevice/linux-amd64 2. Run the following command:./idevicesyslog u <UDID> StormRunner Functional (Powered by Mobile Center 2.70) Page 40 of 88

41 View and manage devices Locate file on Windows connector machine 1. Open a command prompt window and navigate to the following folder: <Path to your Windows Connector folder>\libimobiledevice\windows-amd64 2. Run the following command: idevicesyslog u <UDID> Locate file on Mac connector machine Sync with itunes 1. Change directory to the linux-amd64 directory: cd /opt/mc/libimobiledevice/linux-amd64 2. Run the following command:./idevicesyslog u <UDID> Perform a sync with itunes to copy the files to your machine. The files will be copied to: Windows: C:\Users\<USERNAME>\AppData\Roaming\Apple Computer\Logs\CrashReporter\MobileDevice\<DEVICE_ NAME> Mac: ~/Library/Logs/CrashReporter/MobileDevice/<DEVIC E_NAME> Share from your device Locate the crash information in the following locations on your device: ios 7.x: Settings > General > About >Diagnostics & Usage > Diagnostic & Usage Data ios 8.x/ ios 9.x/ ios 10.2: Settings > Privacy > Diagnostic & Usage > Diagnostic & Usage Data ios 10.3 or later: Settings > Privacy. Scroll down and tap Analytics. Open the Xcode Organizer (requires macos and Xcode) 1. Launch Xcode on your desktop machine. 2. Open the Xcode Organizer window. (Window menu > Organizer, or Cmd-Shift-2.) 3. Find your device in the left sidebar, and then select device logs. Orientation steps When you record the packaged version of an app on ios, the recorder generates two orientation steps after the Home navigation step. StormRunner Functional (Powered by Mobile Center 2.70) Page 41 of 88

42 View and manage devices Known issues and problem solving ios app crashes If an app consistently crashes after a launch or Start Record, or if you cannot launch it when the Install application option (the actual option name may differ depending on the tool you are using) is selected, perform one of the following : 1. Run the tests with the uninstall or delete option. Tool UFT Option name Uninstall application after recording or running > Always in the Record and Run Settings dialog box, in the Mobile tab. 2. Install the repackaged AUT on the device, and only use the Restart option. Tool UFT Option name Restart application before recording or running in the Record and Run Settings dialog box, in the Mobile tab. The Agent doesn't start up on the device If the Agent does not start up on the device, verify that the devices are recognized by the connector machines: Linux 1. Navigate to: /<path to connector installation folder>/libimobiledevice/linux-amd64/ 2. Run idevice_id l The result of this command should be a list of devices IDs (UDID). If the command returns an empty result or ERROR message, try the following: 1. Log in as root on the connector machine. 2. Locate the process ID of usbmuxd " ps aux grep '[u]sbmuxd' 3. Kill the process: kill 9 <processid> 4. Start usbmuxd again: usbmuxd 5. Run idevice_id l again to see if the device is recognized. StormRunner Functional (Powered by Mobile Center 2.70) Page 42 of 88

43 View and manage devices Windows 1. Open a command prompt window and navigate to the following folder: <Path to your Windows Connector folder>\libimobiledevice\windows-amd64 2. Run the following command: idevice_id l The result of this command should be a list of devices IDs (UDID). If there are no devices listed when a device is connected to USB port, this may mean that: The USB port is not working (hardware problem) itunes is not installed, or you are not using the most up-to-date version of itunes on the Connector computer. In this case, you should download the latest version of itunes. If the devices are connected correctly, try to manually launch the MC Launcher app. If you see an Untrusted App Developer notification: 1. Click Trust. 2. Disconnect the device. 3. Wait 5 seconds and then reconnect the device. Enterprise certified apps do not launch When trying to launch an enterprise certified app through your test (for example UFT), the launching may fail the first time you start the app, since Apple requires the user to manually approve the app on the device. The error message asking for approval will not be visible in the testing tool's interface (e.g. UFT). However, if you launch the app manually, it will be visible. Solution: Manually launch the app and approve its certificate. Then, launch it through your test. Calls during replay When a phone call starts on an ios device, the background apps are suspended, including the Agent app. The Agent app will therefore be unable to communicate, execute code, or run scripts. As a workaround, make the call to a wrong number (e.g. "12345"), wait for the operator to report that it is a wrong number, and wait for the call to end. The script will continue to replay once the call has ended. Failed date picker actions When using the date picker to select a date, make sure that you make your selection within 30 seconds. If the duration of the time selection exceeds 30 seconds, the agent will time out. This issue only applies to non-packaged apps on ios devices. Unresponsive device If a device doesn't work as expected, try to reset all settings. For example, if remote access doesn't work, taps don t respond, apps don t install, and so forth, revert to the original default settings: Select General > Reset > Reset All Settings. Follow the steps described in "ios initial device configuration" on page 20. StormRunner Functional (Powered by Mobile Center 2.70) Page 43 of 88

44 View and manage devices Error in connecting during replay For Mac Connectors connecting to ios 11.1 devices: If your device cannot connect to the Mobile Lab, check the Connector log for an error when executing./ideviceadddocument. This indicates a trust issue. Reconnect the device, open ITunes and press Trust on the device. Stopped Agent If the Agent stops working on the device, do the following: Disconnect the device by unplugging the USB cable. Wait 5 seconds, and reconnect the device by USB cable. If you're still having problems: Remove the Agent app, the launcher app, and all applications under test (AUTs) from the device. Close all open apps on the device. Wait 5 seconds and reconnect the device to the USB port. As a last resort: Restart the device. The Agent is reinstalled. Accept any system pop-ups on the device. Unplug the device by disconnecting the USB cable. Wait 5 seconds and reconnect the device. StormRunner Functional (Powered by Mobile Center 2.70) Page 44 of 88

45 View, upload, and manage apps View, upload, and manage apps On the MOBILE LAB tab, click APPS to view and manage the applications in your lab. You can upload a new app, see information about apps that have already been uploaded, and delete apps. View app details Tip: Use the filter panel to limit what items are displayed, so that you can focus on the information that is important to you. You can filter by OS, or use the Search in the right pane to specify an app name or app package ID. Only matching items are displayed. Apps are displayed with the following summary details: Name of the app The app name may contain I18N characters. Operating system Android or ios. Note that Windows phone is not supported in StormRunner Functional. When the app requires a minimum OS version, this is indicated next to the OS icon. Upload number, version and build number The upload number is the specific upload of the app selected for testing. You may have several uploads of an app that you want to test. For example, if you introduce changes to your app, you may want to test the differences between the various uploads of the application. You can choose to use the latest upload, or a specific upload of an app. Compatible device types Indicates what type of devices are compatible with the app - Phone, Tablet, or both. System apps Several built-in apps are provided with your installation: StormRunner Functional (Powered by Mobile Center 2.70) Page 45 of 88

46 View, upload, and manage apps MC Browser The MC Browser apps for ios and Android can be used to test mobile web applications. (Following the end of Microsoft's mainstream support for Windows Phone, the MC Browser app is no longer supported for Windows Phone.) The MC Browser apps can't be deleted or updated. For more details, see "MC Browser Apps" on page 70. Advantage Shopping The Advantage Shopping app is available for devices with ios 8.2 and higher and Android devices versions 4.4 and higher. This app is a sample online store for home electronics. It has a standard online shop interface, with common features such as search and a shopping cart. Options toolbar Hover on a specific app, and a floating toolbar is displayed with the following options: Delete. Delete all uploads of the app. More information. Click More information to display the full details of the app as shown below: StormRunner Functional (Powered by Mobile Center 2.70) Page 46 of 88

47 View, upload, and manage apps This is the specific upload of the app selected for testing. If you introduce changes to your app between uploads, you may want to test the differences between the various uploads of the application. By default, the latest upload is always selected for testing. This is the version & build number of the app. StormRunner Functional takes this from the manifest file of the app. This is the unique identifier for the app. This information is taken directly from the manifest file of the app. You can also filter by this name. Android apps only: The name of the Android activity to run when the app is launched. Displays all the app uploads, and which upload the tester has selected for testing. To delete a specific upload, select the Delete button in its row. To always use the latest one, select Latest upload. The information icon displays whether the packaged or non-packaged version of the app is available. For more details, see "When to use a packaged app" on page 49. Note: For ios apps, there will also be information about the devices on which the app can be installed. For details, see Device provisioning information below. StormRunner Functional (Powered by Mobile Center 2.70) Page 47 of 88

48 View, upload, and manage apps Device provisioning information (ios only) Provisioning is the process of preparing an app to launch on devices. As part of this process, a match is required between the provisioning profile embedded in the app and the one installed on the device. If you have an Enterprise certificate, all devices are included. If, however, you have a development certificate, you must make sure that the UDID of your device is listed in the provisioning profile. To check whether or not your upload can be installed: 1. In the App view, click on the More information icon in the app whose upload you want to test. 2. Select the upload you want to test, and hover on the icon in the App Details screen. The tooltip shows the status of the selected upload: Signed with an enterprise certificate and can be installed on all devices Signed with a development certificate. Click on the icon for the list of devices included in the provisioning profile. If the provisioning profile of an ios app that you select to install on a specific device does not include that device, a warning icon will be displayed, and you will not be able to proceed with your selection. Note that this only applies when selecting a specific device, and not if you select a device by capabilities. Upload an app To upload an app, drag and drop the file into the APPLICATIONS pane, or click Note that: The maximum file size that you can upload is 200 MB.. Select the app. For devices running an Android version prior to 5.00, apps with multiple dex files are not supported (for packaged apps). StormRunner Functional (Powered by Mobile Center 2.70) Page 48 of 88

49 View, upload, and manage apps Troubleshooting Why can't I see all my apps? Check the filter panel to see what options are selected. StormRunner Functional displays only the items that fit the filter conditions. To display all items, select all the filter options and clear the search field of any text that you have entered. Blue text in the filter pane indicates an active filter. App packaging and signing StormRunner Functional supports testing both packaged and non-packaged native and hybrid apps. When to use a packaged app What is a packaged app? A packaged app is an app that StormRunner Functional has repackaged with record and replay libraries. Although both packaged and non-package apps are supported by StormRunner Functional, packaging is still required for simulations. Additional considerations There are also some differences between packaged and non-packaged apps in the following areas: Full Device Automation functionality such as cross-app recording and recording of system apps, is not supported in packaged apps. Support for touch gestures. Object recognition. For UFT, see the Object Method Reference for UFT. Considerations when using non-packaged hybrid apps When using non-packaged hybrid apps, note the following: For Android apps, remote content debugging must be enabled. For details, see "Enable remote content debugging of Android apps" on page 62. StormRunner Functional (Powered by Mobile Center 2.70) Page 49 of 88

50 View, upload, and manage apps ios hybrid apps must be signed with a development certificate of either an Apple Developer or Enterprise Account. StormRunner Functional packaging and signing tools StormRunner Functional supports testing both packaged and non-packaged native and hybrid apps. This gives you the option of selecting either a packaged app or the original version when running a test. By default, Android apps uploaded to the Mobile Lab are automatically packaged with record and replay libraries and signed with a debug certificate. There is no need to manually package these apps before uploading them. However, if you want to use the packaged version of an Android app that uses services requiring a private key, such as Google Maps or the Authentication service, the app must be repackaged manually with your own certificate before uploading it to the Mobile Lab. To use the packaged version of an ios app for testing, you must package the app manually before uploading it to the Mobile Lab. For details see, "Package an Android app manually" on page 60 or "Package an ios app manually on a Mac machine" on page 64. Certificates required when signing ios apps To test an ios app with StormRunner Functional, you may need to re-sign your app. This section explains when you need to re-sign your app, and what certificate to use. Agent, Agent Launcher, and WebDriverAgent-Runner apps The Agent, Agent Launcher and WebDriverAgent-Runner apps must be re-signed with a development certificate of an Apple Developer Account, and a development provisioning profile belonging to the same account. Other ios apps Application under Test Mode Re-sign required? Required certificate ios native app Packaged app Yes. This is part of the packaging process. Any type of certificate of either an Apple Developer or Enterprise account ios native app Nonpackaged app No, unless your organization needs to re-sign the app for some specific reason. Any type of certificate of either an Apple Developer or Enterprise account StormRunner Functional (Powered by Mobile Center 2.70) Page 50 of 88

51 View, upload, and manage apps Application under Test Mode Re-sign required? Required certificate ios hybrid app Packaged app Yes For ios versions and higher: Development certificate of an Apple Developer account For versions lower than ios 8.4.1: Development certificate of either an Apple Developer or Enterprise account ios hybrid app Nonpacked app Yes To identify WebView, development certificate of an Apple Developer account See also: "Package an ios app manually on a Mac machine" on page 64 "Package an Android app manually" on page 60 Re-sign the Agent apps The Agent apps are standard ios applications that need to be installed on each device that you want to use with StormRunner Functional. More about the Agent apps The Agent apps provide a communication channel between the device and Mobile Center. The following apps must be re-signed with a development certificate of an Apple Developer account, and a development provisioning profile belonging to the same account: Agent Agent Launcher WebDriverAgent Runner-Runner WebDriverAgentRunner-Runner_xcode9 The certificate and provisioning profile provide the identity of the developer, and the list of devices on which distribution of the app is allowed. Obtain a development certificate of an Apple Developer account The Agent apps (Agent, Launcher, WebDriverAgentRunner-Runner and WebDriverAgentRunner- Runner_xcode9) must be re-signed with a development certificate of an Apple Developer account. StormRunner Functional (Powered by Mobile Center 2.70) Page 51 of 88

52 View, upload, and manage apps Create a development certificate on a Mac If you already have a Developer certificate, you can skip this section. 1. Open the Keychain Access app. 2. Select Certificate Assistant > Request a Certificate From a Certificate Authority. 3. Enter your address (twice), name, and select Save to disk. Click Continue. This creates a *.csr file. 4. Open a browser and log in to the Apple Member Center. 5. Select Certificates, Identifiers & Profiles. 6. In the Certificate section, select All. 7. Click the + (Add) button. 8. When you are prompted to indicate the type of certificate, select ios App Development and click Continue. Click Continue again in the next screen. 9. Click Choose File and locate the *.csr file created above. Click Generate. 10. Click Download to save the certificate to your machine. 11. Double click on the downloaded certificate to install it to the Keychain Access. For step-by-step instructions on how to generate a development certificate using a Mac, see "Generate a development certificate using a Mac" on page 76 Export a development certificate from a Mac for use on a Linux machine If you already have a development certificate installed on your Mac machine, and you want to use it for MC Enabler on Linux, follow these steps to export it: 1. Open the Keychain Access app. 2. In the Category pane, select Certificates to show the installed certificates. 3. In the main pane, select your certificate, and select Export "<Certificate name>" from the right-click menu. 4. When prompted to enter a password, leave the fields empty, and click OK. You can use the generated *.p12 file to re-sign the Agent and Agent Launcher on a Linux machine. Create a development certificate in Linux or Windows 1. Generate a *.csr (Certificate Signing Request) file with following set of commands, replacing with your own address, and providing a meaningful NAME. (The sample code below shows Linux format. For Windows, navigate to the OpenSSL installation and switch the direction of the slash.) cd /etc/openssl/certs/ openssl genrsa -out ios-dev.key 2048 StormRunner Functional (Powered by Mobile Center 2.70) Page 52 of 88

53 View, upload, and manage apps openssl req -new -key ios-dev.key -out ios-dev.csr -subj "/ address=< >, CN=<NAME>, C=US" 2. Open a browser and log in to the Apple Member Center. 3. Click Certificates, Identifiers & Profiles. 4. In the Certificate node, select All. 5. Click on the Add button. 6. Select ios App Development and click Continue. Click Continue again in the next screen. 7. Browse to the ios-dev.csr file created above and upload it. Click Generate. 8. Click Download to get the generated certificate *.cer file. 9. Convert the *.cer file to a *.p12 file using the following set of commands. (If you used a name other than ios-dev.cer, modify the command's arguments.) openssl x509 -in ios-dev.cer -inform DER -out ios-dev.pem -outform PEM openssl pkcs12 -export -inkey ios-dev.key -in ios-dev.pem -out iosdev.p12 Obtain a development provisioning profile To install an ios app on a device, the app must be provisioned to launch on the device. Note: Each device under test must be included in the provision profile (UDID must be included in list of devices.) To obtain a provisioning profile: 1. Open a browser and log in to the Apple Member Center. 2. Select Certificates > Identifiers & Profiles. 3. Click All under the Provision Profiles node and select your provision profile, belonging to the same Apple Developer account used to generate the development certificate above. Click Download. For step-by-step instructions, see "Obtain a development provisioning profile" on page 80 Re-sign and deploy the Agent apps To simplify and the re-signing process, the MC Enabler utility is provided for both Mac and Linux: StormRunner Functional (Powered by Mobile Center 2.70) Page 53 of 88

54 View, upload, and manage apps The MC Enabler for Mac enables you to re-sign and package (instrument) apps. The MC Enabler for Linux only lets you re-sign apps, not package them. For example, you can use it to re-sign the Agent and Launcher apps. A system running with macos is not required. Note: The MC Enabler for Linux is no longer supported. Re-sign apps on a Mac The following procedure describes how to run the MC Enabler utility to re-sign apps on a Mac. Prerequisites A Mac machine with OS X 10.8 or 10.9 or macos Sierra , 10.12, , , and Xcode version 6 and above installed To check that Xcode is installed: In the Terminal window, type codesign. The usage of codesign should be displayed. If the codesign command is missing, Xcode is not properly installed, and you should reinstall it. To re-sign the Agent apps: 1. Download the MC Enabler package for MacOS onto your Mac. We recommend using the GUI version of the app. For details on using the command line version, see " MC Enabler on Mac - command line version" on page Locate the Agent files in the Agent folder of the Device Connector installation files. : HP4M-Agent.ipa HPMC-AgentLauncher.ipa WebDriverAgentRunner-Runner.ipa WebDriverAgentRunner-Runner_xcode9 3. Copy the files to your Mac machine. 4. Copy the provision profile that you created to your Mac machine. For details, see "Obtain a development provisioning profile" on the previous page. 5. Select the Agent/L mode in the MC Enabler window to show the relevant fields. StormRunner Functional (Powered by Mobile Center 2.70) Page 54 of 88

55 View, upload, and manage apps UI Element Agent/L - Original IPA Destination Provision Profile Certificate Name Description The Enabler mode for code signing the Agent ipa files. The full path to the original ipa file. For example /<full_path>/hp4m-agent.ipa A destination for the generated files on your Mac machine. The path to the provisioning profile file on your Mac machine. A drop-down list of the installed certificates from the Keychain. Select the required certificate from the list. If the certificate is not listed, it is not properly installed on this Mac machine. Note: The MC Enabler does not check the validity of the certificate, so you must ensure that it is valid. StormRunner Functional (Powered by Mobile Center 2.70) Page 55 of 88

56 View, upload, and manage apps UI Element Verbose Description Displays warning and error messages in the text area, if the Agent is not enabled properly. 6. Fill in all of the fields and click Run. This generates an additional HP4M-Agent enabled ipa file, customized with your code signing certificate and provisioning profile. Re-sign apps on Linux Note: The MC Enabler for Linux is no longer supported. To re-sign the Agent apps on a Linux or Window machine, you need a p12 certificate file and a provisioning profile. For details, see "Create a development certificate in Linux or Windows" on page 52. You can create these files on either a Linux or Windows machine, but you can only run the MC Enabler on a Linux machine not a Windows machine. Prerequisites Before you can run the MC Enabler on a Linux machine, follow the instructions below to install Python, even if you already have a Python installation on your machine. 1. Install gcc Check that you have the gcc package installed on your system. If you do not have it, run the following command: yum install gcc 2. Install openssl If you have the connector installed on the machine, you can skip this step. Otherwise, run the following commands: yum install openssl yum install openssl-devel 3. Download Python using following commands from the official Python site. cd /usr/src wget 4. Extract the contents of the Python archive file and install it on your machine. StormRunner Functional (Powered by Mobile Center 2.70) Page 56 of 88

57 View, upload, and manage apps tar xzf Python tgz cd Python /configure make altinstall To re-sign the Agent apps 1. Download the MCEnabler for Linux and copy the file to your Linux machine. 2. On you Linux machine, extract the files: unzip MCEnablerLinux.zip d <target directory> 3. Copy the p12 file and provisioning profile you generated earlier, to the MCEnabler directory. Include only the appropriate Linux distribution, redhat or centos. cp <p12_file_path> <path to target directory>/mcenabler/redhat centos/ cp <provision_profile_file_path> <path to target directory>/mcenabler/redhat centos/ 4. Navigate to the target directory (root folder of MCEnabler) and run the following command: chmod -R +x.* 5. Navigate to the MCEnabler folder on your Linux machine using the appropriate Linux distribution, redhat or centos. cd <path to target directory>/mcenabler/redhat centos/ 6. Run HPMCEnabler in verbose mode to generate debug logs../hpmcenabler <path to connector installation folder>/connector/agent/hp4m-agent.ipa --p12-file./<your_p12_ filename>.p12 -p./<your_provision_profile>.mobileprovision -v./hpmcenabler <path to connector installation folder>/connector/agent/hpmc-agentlauncher.ipa --p12-file./<your_p12_ StormRunner Functional (Powered by Mobile Center 2.70) Page 57 of 88

58 View, upload, and manage apps filename>.p12 -p./<your_provision_profile>.mobileprovision -v./hpmcenabler <path to connector installation folder>/connector/agent/webdriveragentrunner-runner.ipa --p12-file./<your_p12_filename>.p12 -p./<your_provision_profile>.mobileprovision -v./hpmcenabler <path to connector installation folder>/connector/agent/webdriveragentrunner-runner_xcode9.ipa --p12- file./<your_p12_filename>.p12 -p./<your_provision_ profile>.mobileprovision -v The re-signed files are copied to the Agent folder. Distribute the re-signed apps Once you re-sign the Agent apps, deploy them in the following way: 1. Rename the files by removing -Codesigned from the file name. For example, the Agent file should be renamed from HP4M-Agent-Codesigned.ipa to HP4M-Agent.ipa 2. Copy the re-signed apps over to the Agent folder on connector machines: Windows Connector: <Path to Windows Connector folder>\agent (Default: C:\Program Files\Mobile Center Connector\Agent) Linux Connector: <path to connector installation folder>/connector/agent Default: /opt/mc/connector/agent StormRunner Functional (Powered by Mobile Center 2.70) Page 58 of 88

59 View, upload, and manage apps Mac Connector: <path to connector installation folder>/connector/agent Default: /opt/mc/connector/agent Run the following commands in the Agent folder: sudo chown hpmc HP4M-Agent.ipa sudo chown hpmc HPMC-AgentLauncher.ipa sudo chown hpmc WebDriverAgentRunner-Runner.ipa sudo chown hpmc WebDriverAgentRunner-Runner_xcode9.ipa sudo chmod 755* 3. Restart the connector service. Windows On the connector machine: Open the Windows Services Window (Control Panel > System and Security > Administrative Tools and double-click Services). Select the Mobile Center Connector service and choose Restart from the right-click menu. Linux Use the following command: service hpmc restart Mac From the Terminal window, change directory to /opt/mc/scripts and run: sudo launchctl load /Library/LaunchDaemons/com.hpe.mobilecenter.plist Note: These commands require root access. See also: "Troubleshooting ios devices" on page 38 StormRunner Functional (Powered by Mobile Center 2.70) Page 59 of 88

60 View, upload, and manage apps Package an Android app manually You can package your app from the command line using the Android Enabler tool. Prerequisites 1. The packaging process should be run on a machine that meets the following requirements: The Java Runtime Environment (v7.x or higher) is installed. The JRE_HOME environment variable is defined. 1.5 GB free RAM (Recommended) 2. Copy the following to the testing tool machine: AndroidTools folder. Your app (.apk file) Only when testing Hybrid apps with UFT: Copy the uft.mobilecenter.agent.<version>.min.js file for your version of UFT. Run the enabler on your app Run the Android Enabler on your app by running the following from the command line: To sign the app with your own Android certificate Windows <Path to AndroidTools folder>\mcandroidenabler.bat keystore <Android key store path> alias <Android alias name> storepass <Android store password> -keypass <Android key password> hybrid native -jsdir <path to the JavaScript file> <path to your application> Linux <Path to AndroidTools folder>/mcandroidenabler.sh keystore <Android key store path> alias <Android alias name> storepass <Android store password> -keypass <Android key password> hybrid native -jsdir <path to the JavaScript file> <path to your application> keystore alias -storepass The path to keystore file containing your set of private keys. The name used to identify the private key entry in the key store. The password for the key store. StormRunner Functional (Powered by Mobile Center 2.70) Page 60 of 88

61 View, upload, and manage apps -keypass -hybrid -native -removesecuredlayout -jsdir The password for the private key used to sign your apps. Enable packaging of hybrid app. Enable packaging of native app. Remove the LayoutParams.FLAG_SECURE flag, when set, from any detected Window.setFlag() invocations. Use this only when testing hybrid apps with UFT. Package the app with the required JavaScript file/s from the given location on the testing machine. The packaging process consists of a number of steps. Wait for the steps to be completed successfully. The result is an APK file signed with your android certificate. For example, running the above command on my-android-app.apk generates the file: my-android-app.apk.signed.apk in the same folder as the original APK file. Upload the generated *.signed.apk file to StormRunner Functional. To sign the app with a debug Android certificate Windows <Path to AndroidTools folder>\mcandroidenabler.bat native hybrid signdebug -jsdir <path to the JavaScript file> <path to your application> Linux <Path to AndroidTools folder>/mcandroidenabler.sh native hybrid signdebug -jsdir <path to the JavaScript file> <path to your application> signdebug -hybrid -native -removesecuredlayout -jsdir Sign the app with the debug certificate. Enable packaging of hybrid app. Enable packaging of native app. Remove the LayoutParams.FLAG_SECURE flag, when set, from any detected Window.setFlag() invocations. Use this only when testing hybrid apps with UFT. Packages the app with the required JavaScript file/s from the given location on the testing machine. The packaging process consists of a number of steps. Wait for the steps to be completed successfully. The result is an APK file signed with the default debug certificate. For example, running the above command on my-android-app.apk generates the file my-android-app.apk.signed.debug.apk in the same folder as the original APK file. StormRunner Functional (Powered by Mobile Center 2.70) Page 61 of 88

62 View, upload, and manage apps Upload the generated *.signed.debug.apk file to StormRunner Functional. See also: "App packaging and signing " on page 49 "Package an ios app manually on a Mac machine" on page 64 Enable remote content debugging of Android apps StormRunner Functional supports testing non-packaged hybrid Android apps, provided that remote content debugging has been enabled in the app. Before testing a non-packaged hybrid Android app, inspect your app to see if remote content debugging is enabled. For details on remote debugging and how to see check if this enabled in your app, see Google Developer. If remote content debugging is not already enabled, you can use the Android Enabler tool to manually enable remote content debugging. Manually enable remote content debugging You can manually enable remote content debugging in your app from the command line using the Android Enabler tool. Prerequisites: The packaging process should be run on a machine that meets the following requirements: The Java Runtime Environment (v7.x or higher) is installed The JRE_HOME environment variable is defined 1.5 GB free RAM (Recommended) To enable remote content debugging: 1. Copy the following to the testing tool machine: AndroidTools folder. Your app (.apk file) 2. Run the enabler on your app. To sign the app with your own Android certificate Run the following from the command line: Windows StormRunner Functional (Powered by Mobile Center 2.70) Page 62 of 88

63 View, upload, and manage apps <Path to AndroidTools folder>\mcandroidenabler.bat keystore <Android key store path> alias <Android alias name> storepass <Android store password> -keypass <Android key password> webdriver <path to your application> Linux <Path to AndroidTools folder>/mcandroidenabler.sh keystore <Android key store path> alias <Android alias name> storepass <Android store password> -keypass <Android key password> webdriver <path to your application> keystore alias -storepass -keypass -webdriver -removesecuredlayout The path to keystore file containing your set of private keys. The name used to identify the private key entry in the key store. The password for the key store. The password for the private key used to sign your apps. Enable remote content debugging. Removes the LayoutParams.FLAG_SECURE flag, when set, from any detected Window.setFlag() invocations. The process consists of a number of steps. Wait for the steps to be completed successfully. The result is an APK file signed with your android certificate. For example, running the above command on my-android-app.apk generates the file: my-android-app.apk.signed.apk in the same folder as the original APK file. Upload the generated *.signed.apk file to the StormRunner Functional lab. To sign the app with the default debug certificate: Run the following from the command line: Windows <Path to AndroidTools folder>\mcandroidenabler.bat webdriver signdebug <path to your application> Linux <Path to AndroidTools folder>/mcandroidenabler.sh webdriver signdebug <path to your application> webdriver Enable remote content debugging. StormRunner Functional (Powered by Mobile Center 2.70) Page 63 of 88

64 View, upload, and manage apps -signdebug -removesecuredlayout Sign the app with the debug certificate. Removes the LayoutParams.FLAG_SECURE flag, when set, from any detected Window.setFlag() invocations. The process consists of a number of steps. Wait for the steps to be completed successfully. The result is an APK file signed with the default debug certificate. For example, running the above command on my-android-app.apk generates the file my-android-app.apk.signed.debug.apk in the same folder as the original APK file. Upload the generated *.signed.debug.apk file to the StormRunner Functional lab. Troubleshooting There may be times when enabling remote debugging does not succeed. This can happen when: You tried to upload an app that StormRunner Functional doesn't support The maximum file size that you can upload is 200MB. Package an ios app manually on a Mac machine The MC Enabler utility is provided to simplify and support the re-signing and repackaging of apps. Prerequisites The following must be installed on the Mac machine that you use for packaging an ios app: OS X 10.8 or 10.9 or macos Sierra , 10.12, , and Xcode 6 or higher How can I check that Xcode is installed? 1. In the Terminal window, type codesign The usage of codesign should be displayed. 2. If the codesign command is missing, Xcode is not properly installed, and you should reinstall it. Additional required resources Copy the following resources to your Mac machine: MC Enabler Download the MC Enabler package for MacOS onto your Mac.. The MC Enabler tool is available in both GUI and command line versions. HPMobileCenter.dylib This library enables your apps to work with StormRunner Functional. The library is included in the MC Enabler package. StormRunner Functional (Powered by Mobile Center 2.70) Page 64 of 88

65 View, upload, and manage apps Code signing certificate Code signing provisioning profile This is the certificate your organization uses to code sign apps. The certificate must be installed on the Mac machine that you are using, and can be seen in the Keychain Access program. For more details on the certificates needed, see "Certificates required when signing ios apps" on page 50. This is the mobile provisioning profile that your organization uses to code-sign apps. This is originally a file downloaded from the Apple Developer Member Website and installed on your Mac. For details on how to generate a provisioning profile, see "Apple Development Certificates and Provisioning Profiles" on page 76. For hybrid apps only When using UFT: Copy the uft.mobilecenter.agent.<version>.min.js file for your version of UFT. You can find the file in the HybridJS folder in the MC Enabler package. MC Enabler on Mac The MC Enabler tool is available in both GUI and command line versions. The GUI version allows you to enter the required values in an accurate and simple manner, using a graphical interface. MC Enabler on Mac - GUI version The MC Enabler GUI enables you to re-sign and repackage your apps for the testing of ios devices. 1. Extract the files onto your Mac machine from the downloaded HPMCEnabler.zip package. 2. Open HPMCEnabler-GUI.app: Ctrl+click or right-click on the app and select Open from the context menu. Note: Since the GUI version of HPMCEnabler is not distributed via the Mac App Store, if you try to install it through the App Store, it will issue a security warning indicating that the application cannot be opened since it is from an unidentified developer. Instead, use the method described above. 3. Fill in all of the fields in the HPMC Enabler. StormRunner Functional (Powered by Mobile Center 2.70) Page 65 of 88

66 View, upload, and manage apps User interface elements are described below: UI Element Agent/L - AUT Original IPA HPMC Dylib JS Folder Description The Enabler mode: Agent/L mode. For code signing the Agent apps, as described in "Re-sign the Agent apps" on page 51. AUT mode. For packaging apps, as described in "Package an ios app manually on a Mac machine" on page 64. The full path to the original ipa file that you want to re-sign. For example, if you are re-signing the Agent app, enter /<full_path>/hp4m-agent.ipa In AUT mode only. A library to inject that enables your apps to work with StormRunner Functional. The library is included in the MC Enabler.zip file. In AUT mode only. The full path to the js folder with the js file to inject. Note: Use this only when testing hybrid apps with UFT. Packages the app with the required JavaScript file/s from the given location on the testing machine. Destination Provision Profile Certificate Name A destination for the generated files on your Mac machine. The path to the provisioning profile file on your Mac machine. A drop-down list of the installed certificates from the Keychain. Select a certificate from the list or click Suggest to get the recommended one. If the certificate is not listed, it is not properly installed on this Mac machine. Note: The MC Enabler does not check the validity of the certificate, so you must ensure that it is valid. StormRunner Functional (Powered by Mobile Center 2.70) Page 66 of 88

67 View, upload, and manage apps UI Element Verbose Description Displays warning and error messages in the text area, if the Agent is not enabled properly. 4. Click Run. This generates an additional ipa file, customized with your code signing certificate and a provisioning profile. 5. Upload the new ipa to the mobile lab. Note: Whenever you upload a new or modified ipa file, as a result of adding or changing an ios device, make sure to unplug the device and plug it in again. MC Enabler on Mac - command line version Use the following syntax when running the Enabler from the terminal command line. $ <path>/hpmcenabler <path>/<original_ipa>.ipa [<options>] Command line options: -inject -codesign Inject the dylib into the app. Provide the full path to the HPMobileCenter.dylib. Codesign the app with a certificate. This is the certificate your organization uses to code sign apps. The certificate must be installed on the Mac machine that you are using, and can be seen in the OSX Keychain Access program. Use the full name of the certificate as shown in the Keychain. For more details on the certificates needed, see "Certificates required when signing ios apps" on page 50. -p Attach a mobile provisioning profile to the App. Provide the path to the provisioning profile on your Mac machine. -e Entitlements file. -r Resources rules list. Your custom resource rules file. --originalres-rules --genericres-rules --forceres-rules --no-urlscheme Use the Resources rules file from the original IPA, ResourceRules.plist. Apply a generic Resources rules definition. If the codesign fails due to problems with the resources, try this option. A generic template will be used. Runs the enabler as if the --original-res-rules option was set. If no original rules were found, it runs the enabler as if the --generic-res-rules option was used. Do not add a unique URL scheme in Info.plist. By default, it is added. The format of scheme is hpmc- (a 32 char uid) StormRunner Functional (Powered by Mobile Center 2.70) Page 67 of 88

68 View, upload, and manage apps --verifyagent -d destination folder -n new file name Issue a warning if the Agent is not enabled properly. An optional path to the folder in which to place the new.ipa file. The folder must exist. An optional name for the new.ipa file. -v verbose -V print version -h print usage -j path to.js file folder The full path to the js folder with the js file to inject. Note: Use this only when testing hybrid apps with UFT. Packages the app with the required JavaScript file/s from the given location on the testing machine. A new ipa file is created. Upload the new ipa to your Mobile Lab. Note: Whenever you upload a new or modified ipa file, as a result of adding or changing an ios device, make sure to unplug the device and plug it in again. HPMC Enabler - command line examples The following examples show some common uses of the Enabler command line tool. Re-signing of the HPMC-Agent app <path to HPMCEnabler> <path>/hp4m-agent.ipa codesign <certificate_name> -p <path to mobile.provision> --verify-agent Re-signing of the HPMC-AgentLauncher app $ <path to HPMCEnabler> <path>/hpmc-agentlauncher.ipa codesign <certificate_name> -p <path to mobile.provision> Re-signing of the WebDriverAgentRunner-Runner app $ <path to HPMCEnabler> <path>/webdriveragentrunner-runner.ipa codesign <certificate_name> -p <path to mobile.provision> Re-signing of the WebDriverAgentRunner_Runner_xcode9 app StormRunner Functional (Powered by Mobile Center 2.70) Page 68 of 88

69 View, upload, and manage apps $ <path to HPMCEnabler> <path>/webdriveragentrunner-runner_xcode9.ipa codesign <certificate_name> -p <path to mobile.provision> Repackaging an app $ <path to HPMCEnabler> <path to your_app.ipa> -inject <path to HPMobileCenter.dylib> codesign <certificate name> -p <path to mobile.provision> d <destination_folder> -j <path to js folder> Test generated files After re-signing an agent, we recommend testing the newly-generated ipa before connecting your devices, to check that the agent has been properly enabled for your devices. 1. Locate a device whose UDID is on the provisioning profile list. 2. Install the HP4M-Agent.ipa on the device using your application of choice - iexplore, ifunbox, itunes. 3. Launch the HP4M-Agent app. If the Agent doesn't install or run, there is most likely a problem with your code-signing certificate or provisioning profile. Make sure that: The get-task-allow entitlement is set to true. All the UDIDs of your devices are included in the list. Repackage apps for specific ios devices When working with an iphone 4 and ipad 2, we recommend that you install the app before running it, as described below: Create and install the repackaged app: 1. Repackage the.ipa file on a Mac machine using the MC Enabler. For details, see "Package an ios app manually on a Mac machine" on page Copy the repackaged.ipa file to the connector machine. 3. Connect the ios device to the connector machine. 4. Verify that the ios device is detected. For Linux: cd <path to your connector installation folder>/connector/libimobiledevice/linux-amd64/ StormRunner Functional (Powered by Mobile Center 2.70) Page 69 of 88

70 View, upload, and manage apps idevice_id l For Windows (from a command line, with default installation): cd <path to your connector installation folder>\connector\libimobiledevice\windows-amd64\./idevice_id.exe l 5. Install the.ipa file on the ios device: For Linux:./ideviceinstaller -I <ipalocation> <ipaname> -u <device UDID> For Windows (from a command line): ideviceinstaller.exe -I <ipalocation> <ipaname> -u <device UDID> 6. On the device, check that the app is installed and that it can be launched. 7. On the MOBILE TAB select Applications and click Upload App. Upload the repackaged app. 8. Select the ios device: iphone 4, iphone 4s, ipad 2, or ipad mini In your testing tool, select the Restart app option. Make sure to disable the Install app option, so that you do not overwrite the repackaged app. MC Browser Apps The MC Browser apps provide the ability to record and replay websites and web apps designed for mobile devices. This is achieved by using an instrumented hybrid browser app, for either Android or ios. Note that Windows Phone is not supported in StormRunner Functional. The apps come preloaded and cannot be removed or updated. The MC Browser apps use the platform s WebView component to load the website or web app. The WebView component comes with the platform SDK, and uses a browser engine that comes bundled with the platform to render web pages inside an app, regardless of the browsers currently installed on the device. In most cases this engine cannot be updated without also upgrading the operating system. WebView in Android In Android versions lower than 4.4 (KitKat), WebView uses the WebKit rendering engine to display web pages, and includes methods to navigate forward and backward through a user s history, to zoom in and out, to perform text searches, and more. For details, see Android 4.4 OS and higher use a WebView component based on the Chromium open source project. StormRunner Functional (Powered by Mobile Center 2.70) Page 70 of 88

71 View, upload, and manage apps For details, see As it shares the same rendering engine as Chrome for Android, rendering should be more consistent between the Android WebView and Chrome. Devices with an operating system equal to or lower than 5.x, the embedded WebView may use a different Chrome core than the device's Chrome browser. WebView in ios In ios, the UIWebView uses a WebKit based browser engine based on the ios version. Users can expect performance improvements and bug fixes in the UIWebView in newer ios versions. For details, see Class Tips for using MC Browser apps Record and replay (R&R) on the website is performed in a similar way to using a packaged hybrid app, and uses the same JavaScript library. Limitations to R&R for packaged hybrid apps are also relevant here. The MC Browser apps have basic browser functionality, including navigation to a URL, Back, Forward, Refresh, and Stop. To apply a certificate to the client: a. Create a new folder, iosclientcert. b. Copy all client-side certificates into the new folder. When you install an MC Browser app, the connector will push all certificate files to the device. c. To remove a client-certificate from your device, manually uninstall the MC Browser app and reinstall it through StormRunner Functional. StormRunner Functional (Powered by Mobile Center 2.70) Page 71 of 88

72 Gestures Gestures This topic summarizes StormRunner Functional support for recording touch gestures on native, mobile web, and hybrid apps. What are native, mobile web, and hybrid apps? Native apps are written in the specific language of the mobile operating system. They are downloaded on the device, run on the device's internal software and hardware, and can take full advantage of the device features. Mobile web apps are written in common web languages, such as HTML5 or Java and are crossplatform Internet-enabled apps accessible via the device s web browser. Native features of the device are not accessible in mobile web apps. Hybrid apps are a mixture of the two. Hybrid apps are written in a combination of languages and leverage a software shell that allows users to tap into the native capabilities of the device, such as the camera or GPS, which pure web apps cannot do. Gestures below that are not supported for recording can be manually added to the script, and are supported on replay. However, you cannot record gestures on a packaged app, and then replay the script on a non-packaged app. Gestures on the physical device are not recorded for non-packaged apps. Android native apps Gesture Packaged app Non-packaged app Scroll Records as swipe. Pan (Drag and Drop) Swipe Long press Does not record duration. Does not record duration. Tap/Click Pinch Add the step to the script. StormRunner Functional (Powered by Mobile Center 2.70) Page 72 of 88

73 Gestures Android hybrid apps Gesture Packaged app Non-packaged app Scroll Records as swipe. Pan (Drag and Drop) Add the step to the script. Add the step to the Swipe script. Long press Does not record duration. Does not record duration. Tap/Click Pinch Add the step to the script. Android mobile web apps Gesture MC Browser Chrome Scroll Records as a swipe. Records as a swipe. Pan (Drag and Drop) Add the step to the script. Add the step to the script. Swipe Long press Does not record duration. Does not record duration. Tap/Click Pinch Records with a delay. Waits until the step following the pinch, and then records both. StormRunner Functional (Powered by Mobile Center 2.70) Page 73 of 88

74 Gestures ios native apps Gesture Packaged app Non-packaged app Scroll Pan (Drag and Drop) Swipe Long press Tap/Click Pinch ios hybrid apps Add the step to the script. The Agent apps must be signed with a development certificate of an Apple Developer Account, and a development provisioning profile belonging to the same account. Note: Both packaged and non-packaged hybrid apps must be signed with a development certificate. For more details, see "Certificates required when signing ios apps" on page 50. Gesture Packaged app Non-packaged app Scroll Records as swipe. Records as swipe. Pan (Drag and Drop) Add the step to the script. Add the step to the script. Swipe Long press Records with a delay. Waits until the step following the press, and then records both, but does not record duration. Records with a delay. Waits until the step following the press, and then records both, but does not record duration. Tap/Click StormRunner Functional (Powered by Mobile Center 2.70) Page 74 of 88

75 Gestures Gesture Packaged app Non-packaged app Pinch Add the step to the script. ios mobile web apps The Agent apps must be signed with a development certificate of an Apple Developer Account. Gesture MC Browser Safari Scroll Pan (Drag and Drop) Swipe Records as swipe. Add the step to the script Add the step to the script. Add the step to the script. Long press Tap/Click Does not record duration. Does not record duration. Pinch Add the step to the script. StormRunner Functional (Powered by Mobile Center 2.70) Page 75 of 88

76 Apple Development Certificates and Provisioning Profiles Apple Development Certificates and Provisioning Profiles Generate a development certificate using a Mac StormRunner Functional (Powered by Mobile Center 2.70) Page 76 of 88

77 Apple Development Certificates and Provisioning Profiles StormRunner Functional (Powered by Mobile Center 2.70) Page 77 of 88

78 Apple Development Certificates and Provisioning Profiles StormRunner Functional (Powered by Mobile Center 2.70) Page 78 of 88

79 Apple Development Certificates and Provisioning Profiles StormRunner Functional (Powered by Mobile Center 2.70) Page 79 of 88

80 Apple Development Certificates and Provisioning Profiles Obtain a development provisioning profile StormRunner Functional (Powered by Mobile Center 2.70) Page 80 of 88

81 Apple Development Certificates and Provisioning Profiles StormRunner Functional (Powered by Mobile Center 2.70) Page 81 of 88

82 Apple Development Certificates and Provisioning Profiles StormRunner Functional (Powered by Mobile Center 2.70) Page 82 of 88

83 Apple Development Certificates and Provisioning Profiles StormRunner Functional (Powered by Mobile Center 2.70) Page 83 of 88

84 Apple Development Certificates and Provisioning Profiles StormRunner Functional (Powered by Mobile Center 2.70) Page 84 of 88

85 Apple Development Certificates and Provisioning Profiles StormRunner Functional (Powered by Mobile Center 2.70) Page 85 of 88

86 Apple Development Certificates and Provisioning Profiles StormRunner Functional (Powered by Mobile Center 2.70) Page 86 of 88

87 Send Us Feedback Let us know how we can improve your experience with the Mobile Lab User Guide. Send your to: StormRunner Functional (Powered by Mobile Center 2.70) Page 87 of 88

88