Settings LoggingSettings/en: Unterschied zwischen den Versionen
Cg (Diskussion | Beiträge) |
Cg (Diskussion | Beiträge) |
||
| Zeile 1: | Zeile 1: | ||
| ⚫ | |||
=== Overview === |
=== Overview === |
||
Activity log entries remember the result of a step's execution. They usually include information |
Activity log entries remember the result of a step's execution. They usually include information |
||
| Zeile 9: | Zeile 7: | ||
lots of memory - sometimes more than can be kept and prunning (cutting off parts of the trace) is |
lots of memory - sometimes more than can be kept and prunning (cutting off parts of the trace) is |
||
required. For such tests, it might be useful to disable the logging of certain actions and/or steps and/or pins. This can be controlled via popup menus of steps and pins in the diagram editor. |
required. For such tests, it might be useful to disable the logging of certain actions and/or steps and/or pins. This can be controlled via popup menus of steps and pins in the diagram editor. |
||
In contrast to activity logs, traces as sent to the Transcript (Console) are not persistent and will be lost when the Transcript window is closed (unless the contents is captured and saved explicitly, via one of the Transcript action blocks) |
|||
| ⚫ | |||
=== Log Activities === |
=== Log Activities === |
||
Version vom 28. Mai 2018, 15:07 Uhr
Inhaltsverzeichnis
Overview[Bearbeiten]
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. For such tests, it might be useful to disable the logging of certain actions and/or steps and/or pins. This can be controlled via popup menus of steps and pins in the diagram editor.
In contrast to activity logs, traces as sent to the Transcript (Console) are not persistent and will be lost when the Transcript window is closed (unless the contents is captured and saved explicitly, via one of the Transcript action blocks)
Logging Settings[Bearbeiten]
Log Activities[Bearbeiten]
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[Bearbeiten]
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[Bearbeiten]
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[Bearbeiten]
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[Bearbeiten]
If enabled, all executed OS commands (shell/script interpreter calls, etc.) will be logged in the activity log.
Log System Activity Notifications[Bearbeiten]
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).
Timestamps have Microsecond Resolution[Bearbeiten]
If enabled, timestamps are kept with microsecond resolution (if the underlying operating system supports them); otherwise, they are generated with millisecond resolution.
The default is false for backward compatibility with older expecco versions.
Ignore any "Skip in Trace" Attribute[Bearbeiten]
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.
Tracing Settings[Bearbeiten]
Show Internal Warning and Info Messages[Bearbeiten]
Probably only useful for diagnostics of expecco itself
Show External Commands on Transcript[Bearbeiten]
If on, executed shell, batch, script and other OS commands will be traced on the Transcript.
Show Stdout and Stderr on Transcript[Bearbeiten]
If on, the stdout/stderr of executed external programs is traced on the Transcript (stderr in red)
Show Outgoing HTTP Requests on Transcript[Bearbeiten]
Outgoing HTTP requests (from the HTTP-get/put actions) will be traced on the Transcript.
Show Outgoing SOAP Requests on Transcript[Bearbeiten]
Outgoing SOAP requests will be traced on the Transcript.
MessageTally on Execution[Bearbeiten]
If checked, execution times of elementary activities are measured and an execution profile is generated after the execution (on the Transcript window). This is useful to find out where time is spent for performance optimizations.
