Setting synchronization policy with the test results

Response time is calculated automatically for Web applications and hybrid applications. But for native applications, response time is based on synchronization policies. When you record a test, the synchronization policies are automatically computed and set in the test steps. Response times are reported for actions that have been played back successfully and only if the synchronization policy has been set to allow response time calculation.

Before you begin

Record a test on a mobile device. Run the test from the test workbench if you want a statistical report to be generated. Don't forget to choose Enter the passive mode to give control to the test workbench.

About this task

Restriction: Applicable to Android only.
After the test is generated, you can see the synchronization policies of the actions that were recorded on the device (Start, press back) and the UI actions (click button) from the launch node or from a step selected in the test script in the test editor. Synchronization policies are available for native steps only, it is not applicable to web UI steps. For web UI steps, a hidden default synchronization policy, which cannot be edited, is used to measure the response time for successful steps. Response time results are displayed in a web report. A statistical report is generated only if you run a test from the test workbench. Response time is measured only when a step is successful and if its synchronization policy is set to Wait for idle (default) or Wait not busy. You must choose the policy that is the most appropriate so that response time is calculated and reported.
Note: If your test was generated with HCL OneTest Studio Mobile Client 8.5.1 and edited in a version 8.6, you must first set the mobile synchronization policy to the default state as described in step 1, and run the test to have response time reported.

Procedure

  1. Optional (only for tests generated with HCL OneTest Studio Mobile Client older than 8.6 version) : Select the root node of the test script, right-click and select Set default mobile synchronization policies. In the wizard that opens check the changes to be performed and click Finish. Then, run the test.
  2. Open the report. You can see information on the measured response time for each successful step of the test and the maximum measured response time. Response time is expressed in minutes. Warnings indicate the steps where the synchronization policy should be changed. The response times are measured only if the synchronization policy succeeds and if the policy is set to compute an accurate value. Example of such policies are those that are set to Wait for idle or Wait not busy. If the report contains a message that the synchronization policy does not allow to compute the response time, it usually indicates that the application is running a background task and failed to display a progress monitor to the end-user. Details on how to view mobile reports can be found in Viewing mobile reports.
  3. Edit the test script, select the step, and in Sync policy, select one of the following policies: Wait for idle or Wait not busy. For details, see Time measurement actions in mobile tests.
  4. When the policy is selected, save the test. Replay the test to verify that it is still successful, that response time is calculated now, and that the report shows no other warnings.
  5. You can modify the time out and think time that contribute the time calculation in the test too. For details on time calculation, see Time measurement actions in mobile tests.
Feedback