Running tests from HCL OneTest UI

After generating a test from a recording, you can edit the test according to your requirements and initiate a test run from HCL OneTest™ UI. The test actually runs on the mobile test client (mobile device or emulator/simulator). This means that the playback is controlled from HCL OneTest UI. The test results can be viewed from both HCL OneTest UI and the mobile test client.

Before you begin

You must have recorded and generated a test on a mobile device, emulator or simulator. You can find information on the procedure in Recording tests from HCL OneTest UI, in Recording tests from the Android mobile test client, or Recording tests from the iOS mobile test client.
Ensure that you give control to HCL OneTest UI to run tests by tapping Enter passive mode. After you tap it, on the mobile client, a message tells you to press Back to end this mode or wait until a playback scenario starts. On iPads, you must select any other page on the left to end the passive mode.
To prevent your iOS device from disconnecting during playback, go to Settings > General on your iOS device and turn Auto-Lock to Never.

Note: If your test contains datasets, it will be controlled by HCL OneTest UI.

About this task

Resource monitoring starts immediately after the test run is initiated. Resource data is collected at the frequency specified in the polling interval. At every interval the collected data is averaged for resources and sent back to workbench to be plotted in the report. Resource monitoring is terminated when the test run finishes.

Note: To capture Response Time and Resource Monitoring data about mobile application and device's resources, you must have Android 2.2 or newer.

Procedure

From HCL OneTest UI, you can start a mobile test run by using any of the following steps in the Web UI Test perspective:
- In the Test Navigator view, right-click a test and click Run As > Test.
- From the Test Navigator view, open the test and, in the test editor, click the Run Test button.
- Add the mobile test to the Compound Test editor.
A wizard displays the list of available devices. Select the device on which the test will be run. You can run the test on multiple devices. For more details, see Running tests on multiple devices in parallel. Click Next.
Optional: Select the options in the Performance Measurement window:
1. To measure the usage of resources such as processor, physical memory, network traffic in and out, and battery of the mobile device and the application under test, select the Resource Monitoring check box. Use the Polling Interval field to specify the periodic intervals in which the resources should be monitored during a run. For example, if you specify 5000 milliseconds, the resource monitoring process starts when the test is executed and collects data every 5000 milliseconds of the test run. The process stops when the test run is completed.
  Note: To view known limitations for resource monitoring, see release notes.
2. To collect response time data within the application and outside the application (in the network and server), select the Collect Response Time Contribution Data check box. This data is displayed in the Mobile and Web UI Statistical report as On App and Off App bar graphs. This will help to identify the contribution of the application against the contribution of the network and server to an unexpected response time or breakdown for a test step. For more details, see Evaluating response time results.
The first time you run a test, you will be prompted to run the test from the Test Execution perspective. Select the Remember my decision check box to avoid receiving the message again and click Yes.

Results

The test is played back on the mobile device. Do not interact with the mobile device until the test is complete. If you need to stop the test run, click the Stop test button in the HCL OneTest UI toolbar. For details on the Stop Test Run wizard, see Interrupting a run .

After the run, both Statistical (Performance) and Mobile (Live) reports are displayed.

What to do next

You can now evaluate the test results. See Evaluate results.

Feedback