Execution Editor
Aus ExpeccoWiki
The execution editor is used to mody the execution settings of a testsuite. It can be found on the "Execution" tab after selecting the testsuite in the navigation tree.
To the right, you see an example for an opened execution editor.
Execution Settings
- Separate Processes for Long-Running Activities
This check toggle controls if multiple activities are allowed to execute in parallel (are executed by separate threads). By default, this is enabled, but for some programs, it makes sense to disable this feature. (Usually badly formulated activities, which do not care for synchronized access to shared data.) - When execution longer than
Due to the fact that starting up new processes is a slow operation and takes up some processing power, the expecco system delays the creation of new processes for some time, in order to allow for short activities to finish without the need for an expensive creation of a new process. If an activity is finished within that time duration, no new process is created. Effectively, short-term activities are sequentially executed, as long as their processing takes less than this time duration. - Max. Number of Processes
This limits the number of parallel executing separate processes. Because a process is a somewhat expensive resource in a computer (memory, disk space etc.), allowing for an arbitrary number of separate processes might lead to a slowdown or even blocking of the computers operation.
The default settings can be made in the settings.
Logging Settings
- Log Activities
If enabled, each activity is stored in an activity log.
If disabled, only failed activities are stored.
At least there is one activity log, which keeps the whole information about the execution. - Log Pin Data
If enabled, all input and output pin values are stored in the activity log. Otherwise all values are discarded.
The default setting is specified in the testsuite. - Log Info
If enabled, all information messages are stored in the activity log. Otherwise all information messages are discarded.
The default setting is specified in the testsuite. - Trace Stdout and Stderr on Transcript
If enabled, the Stdout and Stderr are shown on the transcript. - 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 log data during execution. If nothing is specified, all sub activities are stored.
The default setting is specified in the testsuite.
The default settings can be made in the settings.
Back to the Project Editor
For other editors see: Editors
The full online documentation can be found under: Online Documentation
