Settings LoggingSettings/en
Logging Settings
Overview
Activity log entries remember the result of a step's execution. They usually include information about the input pin values, the execution time, the outcome (verdict) and the generated output value(s). The activity log is (currently) stored in memory, to avoid excessive slow-down of the tests execution.
The activity log as generated by long running extensive tests may become very large and consume lots of memory - sometimes more than can be kept and prunning (cutting off parts of the trace) is required.
Log Activities
If enabled, every activity is stored in the activity log. If disabled, only failed activities are stored. There will be always one master (top-level) entry stored, which keeps the overall outcome of an execution, even for passed runs with disabled logging.
This setting value is stored in and loaded from the project, not the user's private settings file.
Log Pin Data
If enabled, all input and output pin values are stored in the activity log. Otherwise all values are discarded and pin values cannot be inspected after the test run.
The default value is stored in the testsuite, not in the user's private settings file.
Log Info
If enabled, all information messages (i.e. messages as generated by explicit logInfo calls and logInfo blocks) are stored in the activity log. Otherwise information messages are discarded.
The default setting is stored in the testsuite, not in the user's private settings file.
Log GUI Screenshots Automatically on Error
If enabled, GUI action blocks which encounter an error (typically: element/xpath not found) will automatically generate a screenshot and add this to the activity log. Be aware that this may generate a huge number of images and lead to excessive memory use and even a failure when running out of memory (especially on 32bit machines). SO this feature should only be used during development.
Log External OS Commands
If enabled, all executed OS commands (shell/script interpreter calls, etc.) will be logged in the activity log.
Log System Activity Notifications
If enabled, activity information notifications (i.e. implicit notifications of the underlying language framework) are stored in the activity log as info log entries. Otherwise information messages are discarded.
The default is false (used to be true in pre 2.1 releases).
Show Internal Warning and Info Messages
Probably only useful for diagnostics of expecco itself
Ignore any "Skip in Trace" Attribute
Enforces an activity log/trace to be generated for all steps/pin values, even if individual steps/pins have the "Skip in Trace" attribute set.
Suppress DialogBoxes for Warnings from alert() and warn:
If checked, no such dialog boxes are opened Such code is often left in elementary code, during debugging of the test suite or while debveloping. For a test run you may temporarily disable them, in case your boss wants to see a quick demo run.
Show External Commands on Transcript
If on, executed shell, batch, script and other OS commands will be traced on the Transcript.
Trace Stdout and Stderr on Transcript
If on, the stdout/stderr of executed external programs is traced on the Transcript (stderr in red)