Cross-platform testing

UFT One tests can use the same scripts to test multiple applications, on multiple devices and platforms.

In this topic:

Test multiple devices

Use the Record and Run settings, object properties, and descriptive programming to record and run on multiple applications and devices.

For example, the following script shows a single test.

This test uses Web methods as well as Mobile methods to perform steps on a mobile device, and then moves on to select list items on a second mobile device.

Browser("Google ").Page("Google").WebEdit("Search").Set "string"
Browser("Google ").Page("Google").Link("Python Strings").Click
Device("Device").App("Mobile Browser").MobileEdit("url").SetFocus
Device("Device").App("Mobile Browser").MobileEdit("url").Set "http://www.bing.com"
Device("Device_2").App("UICatalog").MobileList("list").Select 5
Device("Device_2").App("UICatalog").MobileList("listview_1").Select 0

For more details, see:

• Define Mobile Record and Run Settings
• Maintain test objects in an object repository
• Programming Tests

Back to top

Test multiple platforms

Record a test using one mobile operating system, and then run the test on another.

Adjust the App test object properties when switching back and forth between Android and iOS.

"name:=HPE Mobile Web"

"name:=HPE Mobile Web"

Adjust these properties by:

• Manually changing the values in the object repository

• Parameterizing the properties in the object repository

• Using the App.SetTOProperty method

For more details, see the App test object in the UFT One Object Model Reference.

Back to top

Test Web on mobile

Record your Web tests on a desktop browser, and then run them on a mobile browser using the Mobile Web app.

To do this, you must have both the Mobile and Web Add-ins loaded.

Alternatively, consider using the Chrome emulator to record and run tests on Web apps. The Chrome emulator enables you to run the same test on both desktop and mobile browsers, as well as test devices not yet supported by UFT One.

For more details, see Define settings to test Web apps using the Chrome emulator.

Back to top

Prepare for BPT testing on multiple devices

Application area settings are limited to a single device and application.

To test multiple devices or applications simultaneously:

1. Create an object repository parameter for the Device and/or the App test object's id or identifier description property.

   For details, see:

   • Use a description property to identify your device
   • Use a description property to identify your application

2. Associate the parameter with your component, business process test, or flow test parameter.

3. Change the value of that parameter to represent a different device or app ID for each test iteration, as needed.

Back to top

Use a description property to identify your device

Create a device id property that is used in the server's script or settings to identify the correct device to open.

1. Open your test in UFT One.

2. Add the id description property to the Device test object.

3. Add a device_id test input parameter.

   For more details, see Use action and test parameters.

4. Add a device_id action input parameter:

   1. In the Solution Explorer, select the relevant action node.
   2. In the Properties pane, click the Parameters tab .
   3. Click the Add down arrow, and select Add Input Parameter.

   4. In the Add Input Parameter dialog box, name the parameter as device_id or similar.

      The parameter is added at the action level.

5. Create a link between the test and action input parameters:

   1. In the canvas, right-click the action containing the action input parameter and select Action Call Properties to open the Action Call Properties dialog box.
   2. On the Parameter Values tab, click the Default Value cell for the device_id parameter, and then click the Configuration button.

   3. In the Value Configuration Options dialog box, select Parameter.

      Under the Parameter option, verify that Test/action parameter and device_id are selected.

      The default value for device_id is set in the Action Call Properties dialog box.

      

   4. Click OK and return to the canvas, where a link is added between the test and action input parameters.

      

6. Configure the Device test object's id description property to use the device_id parameter:

   1. In the test's object repository tree, select the Device test object.
   2. In the Test object details area, click the Configuration button for the id description property.

   3. In the Value Configuration Options dialog box, select Parameter > Test/action parameter.

      In the Parameter box, select device_id.

      In the object repository, the value for the id description property is set to device_id.

      

Use a description property to identify your application

Create an application identification property that is used in the server's script or settings to identify the correct application to open when the test is run.

1. Open your test in UFT One.
2. Add an app_name test input parameter:

   1. In the Solution Explorer, select the test node.
   2. In the Properties pane, click the Parameters tab .
   3. Click the Add down arrow, and select Add Input Parameter.

   4. In the Add Input Parameter dialog box, name the parameter as app_name or similar.

      The parameter is added at the test level.

3. Add an app_name action input parameter:

   1. In the Solution Explorer, select the relevant action node.
   2. In the Properties pane, click the Parameters tab .
   3. Click the Add down arrow, and select Add Input Parameter.

   4. In the Add Input Parameter dialog box, name the parameter as app_name or similar.

      The parameter is added at the action level.

4. Create a link between the test and action input parameters:

   1. In the canvas, right-click the action containing the action input parameter and select Action Call Properties to open the Action Call Properties dialog box.
   2. On the Parameter Values tab, click the Default Value cell for the app_name parameter, and then click the Configuration button.

   3. In the Value Configuration Options dialog box, select Parameter.

      Under the Parameter option, verify that Test/action parameter and app_name are selected.

      The default value for app_name is set in the Action Call Properties dialog box.

      

   4. Click OK and return to the canvas, where a link is added between the test and action input parameters.

      

5. Configure the App test object's identifier description property to use the app_name parameter:

   1. In the test's object repository tree, select the App test object.
   2. In the Test object details area, click the Configuration button for the name description property.

   3. In the Value Configuration Options dialog box, select Parameter > Test/action parameter.

      In the Parameter box, select app_name.

      In the object repository, the value for the name description property is set to app_name.

      

See also:

• How to perform Cross Browser Testing with Mobile browsers in UFT
• One Script to Rule them all – Testing Android and iOS Hybrid Apps with Micro Focus UFT
• Run a single test across multiple operating systems
• Test Web apps on multiple browsers
• Define Mobile Record and Run Settings
• Use descriptive programming for multiple browser testing - Use-case scenario