Settings LoggingSettings: Unterschied zwischen den Versionen
Zur Navigation springen
Zur Suche springen
Cg (Diskussion | Beiträge) (Die Seite wurde neu angelegt: „== Logging Settings == === Overview === Activity log entries remember the result of a step's execution. They usually include information about the input pin v…“) |
Cg (Diskussion | Beiträge) (Weiterleitung nach SETTINGS LOGGINGSettings/en erstellt) |
||
| Zeile 1: | Zeile 1: | ||
#redirect [[ 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 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). |
|||
=== Max. Number of kept Subactivities per Activiy === |
|||
Maximum number of subactivities per activity stored in the activity log. |
|||
This setting is used to limit the amount of logdata during execution. |
|||
If nothing is specified, all subactivities are stored; |
|||
otherwise, only the last N log entries are kept. |
|||
The default value is stored in the testsuite, not in the user's private settings file. |
|||
=== Trace Stdout & Stderr of Shell/Batch Actions on Transcript === |
|||
If checked, the stdout and stderr of shell- (unix) and batch- (msdos) actions are traced on the |
|||
Transcript window (if it has been opened). Stdout lines are prefixed by "1:", Stderr lines by "2:". |
|||
This is useful while debugging the test, |
|||
to copy and paste the concatenated output from multiple commands, without having |
|||
to scan the log or to add extra output collection blocks. |
|||
Version vom 29. März 2018, 15:28 Uhr
Weiterleitung nach:
