Testsuite Editor-ExecutionSettings Editor/en

Aus expecco Wiki (Version 2.x)
Wechseln zu: Navigation, Suche
Execution Editor

The execution editor is used to modify the execution settings of a test suite. It can be found on the "Execution" tab after selecting the testsuite in the navigation tree.

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.
Set probe mode to checking
If there are Probes in your test suite, set them to checking mode.

These defaults can also be changed in the more convenient settings dialog.


Specifies the set of resources (devices, operators etc.) which are available for resource allocation.

Default Inventory
Specifies the set of resources which are available during developing and tests of the testsuite. This resource template might differ to the expeccoNET Template.
ExpeccoNET Template
Optional Resources used by expeccoNET. If unspecified, the default inventory will be used.

User Interface

Specifies if and how the optional user interface of actions with GUI is to be shown. This affects only actions which have a GUI attached. In version 2.x, this is a non-supported feature which is not yet released for public use, so we recommend to not use GUI actions and to leave the setting here as defaulted "none".

Logging Settings

These settings specify, how log entries should be stored in the activity log as shown in the TestplanEditor. The activity log is also the base of test reports, so limiting the log entries in the activity log also limits, what can be shown in a test report.

Older versions of expecco included also Report Parameter settings here. These are now kept as Report Template Element in the project tree. Multiple of them can be stored and maintained within a single test suite, to provide specifications for multiple reports with different detail for different target audiences.

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 Executor#Activiy¦Activity
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 values can also be changed in the more convenient settings dialog.

Copyright © 2014-2016 eXept Software AG