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 Rational® Test Workbench 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.