Use the Log action to write a specified Output Message to the console and to an optional logging file.

The file can be stored locally or stored remotely by using a UNC path. The use of tags is supported.

In the Log action editor you can designate a Role for the log message:
  • Info
  • Warning
  • Error

You can set the location of the logging output file by typing the full path name to the file (which can include tags), clicking Browse to locate and select the file, or by selecting one of the most recently used files.

Logging an Error message gives the overall test a fail status, but subsequent test steps are executed as the logic of the test requires. The number of Information, Warning, and Error messages generated by the log action are totalled in a "Logging summary" message at the end of the test.

Note: If you want the output from each test session to appear on its own line, include a carriage return at the end of the output message.

If an output file is designated, the Append and Flush options can be used.

  • If Append is enabled, the test action adds new logging to the existing file contents. Otherwise, the existing contents are overwritten.
  • If Flush is enabled, the test action writes the message to the file immediately. Otherwise, messages are buffered and written in batches (which can improve performance).
    Note: The Log action can be used as a file-writer process.
Note: If you do not want to fail a test when a Log action fails, add a Failure Path to the Log action node and then another Log action to the new Failure Path to write to the console and an optional logging file.