Setting TrueLog Options

Use the TrueLog options to enable TrueLog and to customize the test result information that the TrueLog collects.

Logging bitmaps and controls in a TrueLog may adversely affect performance. Because capturing bitmaps and logging information can result in large TrueLog files, you may want to log test cases with errors only and then adjust the TrueLog options for test cases where more information is needed.

Note: To reduce the size of TrueLog files with Silk Test 17.5 or later, the file format for TrueLog files with the Open Agent has changed from .xlg to the compressed .tlz file format. Files with a .xlg suffix are automatically appended with a .tlz suffix. To parse result data from a .tlz file, you can unzip the .tlz file and parse the data from the included .xlg file. For the Classic Agent, the .xlg file format is used.
  1. Click Options > TrueLog to open the TrueLog Options dialog box.
  2. To capture TrueLog data and activate logging settings, check the Enable TrueLog check box and then choose to capture data for:
    All testcases
    Logs activity for all test cases, both successful and failed. This setting may result in large TrueLog files.
    Testcases with errors
    Logs activity only for test cases with errors. This is the default setting.
  3. In the TrueLog location field, type the name of and optionally the path to the TrueLog file, or click Browse and select the file. The path is relative to the machine on which the agent is running. The default path is the path of the Silk Test Classic project folder, and the default name is the name of the suite class, with a .tlz suffix. To ensure that TrueLog files are not overwritten, for example when you perform parallel testing, you can add placeholders to the TrueLog file name. These placeholders are replaced with the appropriate data at execution time.
    Note: The path is validated at execution time. Tests that are executed by Silk Central set this value to the Silk Central results directory to enable the screenshots to be shown in the result view.
  4. Only when you are using the Classic Agent, choose one of the following to set pre-determined logging levels in the TrueLog Presets section:
    Minimal
    Enables bitmap capture of desktop on error; does not log any actions.
    Default
    Enables bitmap capture of window on error; logs data for Select and SetText actions; enables bitmap capture for Select and SetText actions.
    Full
    Logs all control information; logs all events for browsers except for MouseMove events; enables bitmap capture of the window on error; captures bitmaps for all actions.

    If you enable Full logs and encounter a Window Not Found error, you may need to manually edit your script.

  5. Only when you are using the Classic Agent, in the Log the following for controls section, specify the types of information about the controls on the active window or page to log.
  6. Only when you are using the Classic Agent, in the Log the following for browsers section, specify the browser events that you want to capture.
  7. Specify the amount of time you want to allow Windows to draw the application window before a bitmap is taken.
    • When you are using the Classic Agent, specify the delay in the TrueLog Delay field.
    • When you are using the Open Agent, specify the delay in the Delay field in the Screenshot mode section.
    The delay can be used for browser testing. You can insert a Browser.WaitForReady call in your script to ensure that the DocumentComplete events are seen and processed. If WindowActive nodes are missing from the TrueLog, you need to add a Browser.WaitForReady call. You can also use the delay to optimize script performance. Set the delay as small as possible to get the correct behavior and have the smallest impact on script execution time. The default setting is 0.
  8. To capture screenshots of the application under test:
    • When you are using the Classic Agent, check the Enable Bitmap Capture check box and then choose to capture bitmaps.
    • When you are using the Open Agent, determine how Silk Test Classic captures screenshots in the Screenshot mode section.
  9. Only when you are using the Classic Agent, click the Action Settings tab to select the scripted actions you want to include in the TrueLog. When enabled, these actions appear as nodes in the Tree List view of the TrueLog.
  10. Only when you are using the Classic Agent, in the Select Actions to Log section, check the Enable check box to include the corresponding 4Test action in the log. Each action corresponds to a 4Test method, except for Click and Select.
  11. Only when you are using the Classic Agent, in the Select Actions to Log section, from the Bitmap list box, select the point in time that you want bitmaps to be captured.
  12. Click OK.