Generic Test Log

Applies to TestComplete 15.0, last modified on October 14, 2021

About Panels

Each test type in TestComplete produces a specific log. The Generic Test Log is common for several test types: keyword tests, script routines, unit tests, BDD tests and some others. A generic test log includes the following:

  • Test Log
  • Picture
  • Details
  • Call Stack
  • Performance Counters
The Generic Test Log

Click the image to enlarge it.

Panel Description

Test Log

Contains messages posted to the log by the test engine and by test operations (for example, operations that simulate user actions, log operations, statement operations, and so on).

Picture

Displays an image or images associated with the message which is selected in the Test Log panel.

Details

Contains additional information for the message.

Call Stack

Displays the execution sequence of tests that led to the execution of the test in which the message was posted (by default, available only for error messages).

Performance Counters

Displays the evolution of performance counters monitored during the test run (available only if performance counters are added to the project).

Common Tasks

Below is a description of some operations that are performed most frequently on the generic test log.

To view extended information or images associated with a message
  1. Select the desired message in the Test Log panel. TestComplete will update other log panels with the information relevant for the selected messages.

  2. Switch to the Details or Picture panel to view the extended information or image.

To jump to the keyword test operation or script code that posted a message

To view a keyword test operation or script code that posted a message to the log, simply double-click the desired message in the Test Log panel. TestComplete will open the test or script unit for editing and highlight the operation or line in it.

Note: You cannot jump to the script code, if the computer where the test was run does not have the script debugger installed (see Debugging Tests - Overview).
To view a call stack for a message

Typically, tests may call each other. For example, a keyword test may call a script routine and vice versa. The execution sequence may be even more complex and include several levels. Knowing this sequence may help you better understand what happened in your project during the run and find the cause of the problem.

Note: By default, the call stack information is available only for error messages, and only error messages will have the Call Stack panel. For messages of other types, the Call Stack panel will be hidden. To learn how to enable tracing the call stack for messages of other types, see Collecting Call Stack Information for Log Messages.

To view the run sequence of tests that led to posting a message to the log:

  1. Select the desired message in the Test Log panel.

  2. Switch to the Call Stack panel. This panel lists the execution sequence of tests that led to posting the selected message to the log.

You can then open the tests for editing by double-clicking the desired test in the Call Stack panel.

To filter messages by their type

To view or hide error, warning, informative and other messages in the test log, simply select or clear the check boxes at the top of the Test Log panel. This will filter the log contents so that the panel displays messages of the selected type. For instance, by selecting the Error check box and clearing other check boxes, you can command the panel to only display the error messages:

Error messages in the test log
To filter messages by their contents

To view the messages that contain specific words or phrase, type the desired words into the Quick Search edit box (it is shown at the top-right corner of the panel):

Quick Search Box

The panel will display only those rows that contain all typed words.

Notes:

  • The search is case-insensitive.
  • The search is performed in all visible columns.
  • The search is only performed in the rows that are visible in the panel. For instance, if the Event messages are filtered out and hidden because the Event check box is clear (see above), the search will not be performed in them.

To remove the filter, erase the text you have typed, or just click the button (it appears if the Quick Search box has text).

To update a Visualizer frame from the test log

You can update a Visualizer frame directly from the test log. To do this, follow the steps below:

  1. Select the desired log item in the Test Log panel.
  2. Select the line that contains the image to be updated (when you select lines in the test log, Visualizer images that correspond to these lines are shown in the Picture panel)
  3. Switch to the Picture panel.
    As you can see, the Picture panel contains two images: the expected and actual ones.
    Note: A Visualizer frame can be updated with the actual image only.
  4. Right-click the image shown in the Actual Image section and select Update Visualizer Data from the ensuing context menu.
If you use this item to update the Visualizer frame that contains test object info, all the information about the controls that are shown on the image will be lost.
To update a checkpoint from the test log
  1. Select the message informing about the checkpoint failure in the test log.

  2. Switch to the Details panel.

  3. Click the Update the <Checkpoint_name> checkpoint link at the bottom of the panel.

  4. TestComplete will display a message asking you want to update the checkpoint. Click Yes in this message to close it and to update the baseline data used for the failed checkpoint. After that, TestComplete will replace the stored item with the actual data. If you click No, TestComplete will close the message without updating the checkpoint.

For more information on updating checkpoints, see the description of the desired checkpoint type.

See Also

Test Results
Posting Messages to the Log
Posting Messages, Images and Files to the Log

Highlight search results