TrueLog Options - Classic Agent Dialog Box

Use the TrueLog Options - Classic Agent dialog box to enable TrueLog for the Classic Agent and to customize the information that the TrueLog collects for Silk Test Classic.

Click Options > TrueLog.

Logging bitmaps and controls in TrueLog may adversely affect the performance of Silk Test Classic. 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: By default, TrueLog Explorer is enabled when you are using the Open Agent, and disabled when you are using the Classic Agent. When TrueLog Explorer is enabled, the default setting is that screenshots are only created when an error occurs in the script and only test cases with errors are logged.

For additional information about TrueLog Explorer, refer to the Silk TrueLog Explorer Help for Silk Test.

Logging Settings tab

Enables the TrueLog capture and configures the TrueLog.

Enable TrueLog

Captures TrueLog data and activates logging settings. You can also enable or disable TrueLog each time you run a test case by checking this check box in the Run Testcase dialog box. When you enable or disable TrueLog in the Run Testcase dialog box, Silk Test Classic makes the same change in the TrueLog Options dialog box. Likewise, when you enable or disable TrueLog in the TrueLog Options dialog box, Silk Test Classic makes the same change in the Run Testcase dialog box.

All testcases: Logs activity for all test cases, both successful and failed.
Testcases with errors: Logs activity for only those test cases with errors.

TrueLog file

Designates the location and name of the TrueLog file. This path is relative to the machine on which the agent is running. The name defaults to the name used for the results file, with an .xlg extension. The location defaults to the same folder as the test case .res file.

Note: If you provide a local or remote path in this field, the path cannot be validated until script execution time.

Log the following for controls

Logs certain types of information about the controls on the active window or page.

Control information

Logs the GUI control’s hierarchy, name, type, and other attributes for the active window or page. This information appears on the Controls tab of the Information window in TrueLog Explorer. This is selected by default when you enable TrueLog. If you choose to log control information, you may optionally decide to log:

Control creation/deletion: Tracks the creation and/or deletion of controls on the active window or page. TrueLog updates the control hierarchy after each action. Choosing this option may adversely affect performance.
Include static text controls: Includes the static text controls in the logged hierarchy. To keep TrueLogs small, leave this option turned off for browser testing.
Track low level events: Logs keyboard and mouse events. For each mouse click and key press a new Action node is created on the Tree List in the TrueLog. Use caution when selecting this option for browser applications, as you can significantly impact performance.

Log the following for browsers

Identifies the browser events you want to capture.

Download events: Captures all events that trigger page downloads. Selected by default.
Navigate events: Captures all events that cause new pages to appear. Selected by default.
Terminate events: Captures all events that cause a browser to close. Selected by default.
New window events: Captures all events that cause a new browser window to appear. Selected by default.
MouseMove calls: Logs all scripted MouseMove calls. This is useful for tracking JavaScript MouseOver events. By including this information in TrueLogs, you may significantly affect performance. This information appears as an Action node in the Tree List.

TrueLog delay

Allows Windows time to draw the application window before a bitmap is taken. 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 TrueLog 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.

Enable bitmap capture

Controls when TrueLog captures screenshots of the application under test. Bitmap files are included in TrueLog (.xlg) files. Selected by default.

As specified on action settings tab: Enables the capture of bitmaps for each action type you select on the Action Settings tab. This setting also causes a bitmap capture each time a window becomes active in your application.
On error: Captures a bitmap when an error occurs in your test case.
Window only: Saves the bitmaps for the active window.
Desktop: Saves a bitmap of the entire desktop.
Before error bitmap: Captures the bitmap before the error occurred.

TrueLog Presets

Sets pre-determined logging levels.

Minimal

Logs test cases with errors; enables bitmap capture of desktop on error; does not log any actions.

Default

Logs test cases with errors; 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 test cases; 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.

Action Settings tab

The Action Settings tab on the TrueLog Options - Classic Agent dialog box selects 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.

Select actions to log

Enable

Selects the action to log. Each action corresponds to a 4Test method, except for Click and Select.

Click

Records mouse clicks on many controls, such as PushButton, ScrollBar, TextField, and HtmlLink. To record Click methods on a CheckBox, choose Select, not Click.

Select

Records actions on multiple methods of multiple types of controls, including ListBox, TreeView, ComboBox, RadioButton, and CheckBox. Here is a partial list of what Select records:

Select (ListBox, TreeView, ComboBox, RadioButton)
DoubleSelect, SelectList, SelectRange (ListBox, TreeView)
Click (ListBox, TreeView, ComboBox, RadioButton, CheckBox)
Check, Uncheck, Toggle, SetState (CheckBox)

Bitmap

Selects the point in time you want bitmaps to be captured:

None: Never captures bitmaps.
Before: Captures bitmaps before errors occur.
After: Captures bitmaps after errors occur.
Both: Capture bitmaps both before and after errors occur.