Native application script playback results

When you play back a mobile native application script, carefully review the results to make sure it can play back successfully at a later time.

If the script fails, you can view the failed script step to determine the cause.

Some mobile application scripts may appear to run successfully, but when you review the results, you may find that the login failed, or there was another problem. Not all native applications are developed to send back error codes for login or other failures, so, to the Recorder, the script played back successfully, but it requires some work before it can be uploaded and run on the mobile nodes. This is especially true if the mobile native application is implemented with security. In some cases, you may be able to record the script successfully, but during recording, your credentials were not stored in a manner in which the script can use them again.

During recording, other background processes and applications, such as email or GPS applications, are still running, so their actions are also recorded, but are not necessary to repeat during playback. You can delete steps or actions in a step if those actions do not apply to the mobile application.

Reviewing the results

After the playback is complete, in the SCRIPT PLAYBACK RESULTS section, a message indicates that either the script ran successfully or the script failed.

Script playback results

Even if the script ran successfully, review the results to ensure that the login was complete and that no other problems occurred during playback.

Expand the Script by clicking Expand button next to Script. The Expand button button changes to a Expand button button.

Expand the Step where the login occurred by clicking Expand button.

If you notice actions that relate to other background processes or applications that occurred on the mobile device, you can delete them.

Review the actions to determine if the login was successful.

If you entered login credentials such as a username and password, they appear in a POST action. The response typically appears in a GET action following the POST. Because each mobile application is developed differently, there are many ways for an application to indicate if a login was successful or not. Review the Reply Content of the GET responses carefully.

No screen shots are captured during native application script playback.

You can further modify the script to ensure it plays back successfully on the mobile agent. For more information, see Using JSON for dynamic session token handling and Creating parameters for the username and password.

When playback is complete, you can:

  • Click the right-pointing arrow Expand button to the left of the script name to view the script settings you can modify. See Mobile web scripts.

  • View the details of the URLs in the script.
    This section displays the return code, method, URL, size, and time for each item in a step in the script. You can hold the mouse pointer over the URL to see the full URL. You can also select the URL to view additional information shown in one of the tabs described below.

Summary

View a summary of the play back results by clicking the Summary tab. If the script completed successfully, this tab lists summary information depending on whether you select the script, a step, or an object in the tree view:

  • Object URL – Object.

  • Total response time – Script, step, or object.

  • Number of hosts used – Script or step.

  • Number of connections used – Script or step.

  • Number of objects transferred – Script or step.

  • Return code – Object.

  • Total number of bytes downloaded – Script, step, or object.

Summary tab example

The collected information is also broken out into Host Details and Step Details:

  • Host Details – Shows information about the objects served by each host. The list on this tab shows the name and IP address for each host.
    Click a row to drill down for more information. Click the row again to collapse this information. For each connection to the host, the following details are listed:

    • Port
    • Connect time (in milliseconds)
    • Response time (in milliseconds)
    • Number of objects loaded over the connection
    • Number of errors on the connection
    • Total bytes downloaded
  • Step Details – Shows information about the objects loaded at each step of the script, states whether the step completed successfully, and lists the summary information (as described above). Select a step to drill down for more information. Select the step again to collapse this information. For each object that was transferred in this step, the following details are listed:

    • Status code
    • URL of the object
    • Response time (in milliseconds)

Screen shot tab

No screen shots are captured during native application script play back.

Debug alerts

If you inserted debug statements to troubleshoot the script, the output of the inserted debug statements appears on this tab.

Debug statements can be added to help you troubleshoot an issue. In any action that accepts JavaScript, you can add a JavaScript alert in the location of the script to troubleshoot.

After inserting the debug statement, run the script and view the Debug Alert tab.

Headers

After expanding a step, select an action in the list then select the Headers tab to view the request and response headers.

Headers tab example

POST content

After expanding a step, select an action in the list then select the POST Content tab to view content sent to the server.

POST content tab example

Reply content

After expanding a step, select an action in the list then select the Reply Content tab to view content received from the server.

Reply content tab example