Run Mobile tests

This topic describes details about running Mobile tests in OpenText Functional Testing.

In this topic:

Overview

Before running a Mobile test, you must perform a number of tasks.

Back to top

Mobile test run flow

In OpenText Functional Testing, ensure that you are connected to Digital Lab or to a local device, and click Run.

OpenText Functional Testing connects to the device and the remote access window opens, enabling you to view the application's behavior as OpenText Functional Testing runs the test steps.

During a Mobile run session

When the run reaches a step on a mobile test object, OpenText Functional Testing determines the device and application as follows:

Does the Device test object contain an ID description property?

Yes	OpenText Functional Testing uses the identified device. To use programmatic descriptions with the Device test object, manually add "micclass:=Device" to the step. For example: Device("micclass:=Device").App(...
No	OpenText Functional Testing uses the device defined in OpenText Functional Testing's Record & Run Settings.

Does the step contain an App test object?

Yes	OpenText Functional Testing uses the identifier and version properties to locate the application.
No	OpenText Functional Testing uses the application defined in OpenText Functional Testing's Record & Run Settings.

After OpenText Functional Testing determines the device and application, the device is locked, so that only OpenText Functional Testing can perform actions on it. The steps run as configured.

During a run session, view the data by expanding the Metrics pane on the right side of the remote access window.

The end of a Mobile run session

When a run session ends, if Uninstall is selected in the record and run settings, Digital Lab uninstalls the application from the device.

The device is released, making it available for other Digital Lab users.

The run results are then displayed, including a general run summary, details and statuses for each step, and the following:

Back to top

Run tests with Insight

Tests containing Insight test objects run like any other OpenText Functional Testing test.

However, if the remote access window fails to completely load the user interface, Insight steps may be skipped if those test objects are displayed.

In such cases, modify the image in the object repository to adjust the image borders or the location to click.

For more details, see:

• Record Insight steps for web apps on your mobile device
• Work with Insight or Text test objects

Back to top

Run tests on multiple apps

If a test is designed to run on multiple apps during a single run session, make sure that the test is configured to open the each application separately before running the test.

Then, in the test run, add an App.Launch method before the steps were performed on each application. This enables OpenText Functional Testing to ensure that the application is open before trying to perform the necessary steps.

For details, see:

• Record Insight steps for web apps on your mobile device
• Add steps to open additional apps

Back to top

Run tests on multiple devices

When running a test that contains steps on multiple devices, all remote access windows open layered in the same location, overlapping each other.

The windows remain in a stationary position for the duration of the run session. Running a step on a "hidden" remote access window does not move the window to the foreground. This can prevent steps, including Insight steps, from running correctly.

To solve this, add the following code to the test (or a function library):

'@Description Activate the remote access window for the device
Public Function Device_ActivateRemoteWindow(ByRef device)

       raWindowHwnd = device.GetROProperty("hwnd")
       Window("is child window:=False", "hwnd:=" & raWindowHwnd).Activate       

End Function
RegisterUserFunc "Device", "ActivateRemoteWindow", "Device_ActivateRemoteWindow"

For more details, see Cross-platform testing.

Back to top

Run a single test across multiple operating systems

Create a test for a website or web app on one mobile operating system (for example, Android), and then run that same test on another mobile operating system (for example, iOS).

1. Record your test using a supported native browser, or the Digital Lab Browser app.

   Note: The Digital Lab Browser app is a built-in, packaged and ready-to-use Digital Lab app. For more details, see the Digital Lab Help.

2. In your test, create the following input action parameters:

   device_id	The device's UUID. This is displayed as the device ID in the Mobile Device Selection dialog box, under the device image.
   identifier	The unique identifier for the app (bundle identifier / app ID). For example, to use the Digital Lab Browser app: iOS: com.hp.HPMobileWebBrowserINJ Android: com.hp.mobileweb For more details, see the Digital Lab Help.

   For more details, see Use action and test parameters.

3. Add steps to the beginning of your test to define the device and app IDs.

   For example:

   Device("Device").SetTOProperty "id", Parameter("deviceId")
   Device("Device").App("Mobile Browser").SetTOProperty "identifier", Parameter("identifier")
   

4. In the object repository, edit the Device test object to add the description property id.

   Then, modify the device and app IDs to set their properties using any of the following methods:

   Use the SetTOProperty method for your device or app.

   The SetTOProperty method changes the property values used to identify an object during the test run.

   For details, see the Mobile section of the OpenText Functional Testing Object Model Reference.

   Add a hard-coded description property

   The following example shows how to add the id description property to the Device test object in the object repository. This process is similar for adding any description property.

   1. In the test's object repository, in the Test Objects tree, select Device.

      

   2. On the right, click the Add description properties button.

   3. In the Add Properties dialog box, select id. The id property is added to the list of Description properties.

      

   Convert the value of the id property to a data table parameter:

   1. In the Test object details area, click in the Value cell for the id property.
   2. Click the parameterization icon to the right of the value.
   3. In the Value Configuration Options dialog box, select Parameter, and then select DataTable from the list.
   4. Select to store the data table content in the global sheet, or in the current action sheet.

   The id parameter is added to the Data pane.

For more details, see Cross-platform testing.

Back to top

Run multiple tests in parallel

Use the ParallelRunner CLI tool to run multiple OpenText Functional Testing tests in parallel on mobile devices.

For details, see Run tests in parallel using a command line.

Back to top

Use virtualized networks for OpenText Functional Testing Mobile tests

During your test runs, use virtualized networks for your mobile devices to test the mobile device's performance in a variety of different scenarios, with differing network performance.

1. In Network Virtualization, create different profiles to simulate varying network conditions. For details, see the Network Virtualization Help Center.

2. Configure your NV integration with Digital Lab. For details, see the Network Virtualization Help Center.

3. In your OpenText Functional Testing test or component, insert a Device.StartNV <profile name> statement to apply the network conditions defined in the network virtualization profile.

4. At the end of the test, or earlier if relevant, insert a Device.StopNV statement to stop running the virtualized network.

For details about devices and methods supported by OpenText Functional Testing, see the Mobile section of the OpenText Functional Testing Object Model Reference.

Back to top

See also:

• Run mobile tests from ALM
• Integrate with Digital Lab and Jenkins
• Integrate mobile tests and Bamboo
• Run tests in parallel using a command line
• Real device monitoring
• Define Mobile Record and Run Settings
• Open the remote access window