Accessing logs to help troubleshoot iOS testing and instrumentation issues

This topic describes how to access information that can help you troubleshoot issues found while testing iOS applications. You can use the different log files that are generated when you record or play back an application on an iOS mobile test client. In the case of instrumentation issues, you can retrieve a .zip file that contains all of the data needed to investigate and troubleshoot the issue.

Procedure

  1. When recording and playing back tests of native iOS applications, all steps are logged in the console. Any crash information will go to the relevant device log. Make sure that the application is properly instrumented. Then, connect the device through a USB cable to a Macintosh computer. After the connection is established, open Xcode and access the device log as follows:
    1. If you use Xcode version 6.0 and later, click Window > Devices and click View Devices Logs.

      Access to devices logs for Xcode version 6.0 and later

    2. If you use Xcode version 5.0 and older, click Xcode > Window > Organizer to see the device logs.

      Access to devices logs for Xcode version up to 5.0

  2. When you test through an iOS simulator and need to debug any recording or playback issue, you can access the iOS simulator system log through iOS Simulator > Debug > Open System Log.
    Access to the system log file
  3. If you have any issues when instrumenting the AUT, you can retrieve the RTWinvestigate.zip that is generated during the instrumentation process. This file is available only if you instrument the AUT by running the rtwBuildXcode script with the RTWinvestigate option. The script collects all of the information that would be needed to troubleshoot instrumentation issues. For details about the script, see Instrumenting iOS applications and rtwBuildXcode.sh script.
    All collected data is gathered into an RTWinvestigate.zip file. The file is located in the folder from where you ran the command.

Feedback