Testsuite Editor-ExecutionSettings Editor/en - Versionsgeschichte

Alkurz: /* Logging */

2024-05-15T09:42:30Z

Logging

← Nächstältere Version		Version vom 15. Mai 2024, 09:42 Uhr
Zeile 45:		Zeile 45:

	== Logging ==		== Logging ==
	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.		These settings specify, how log entries should be stored in the activity log as shown in the [[Testplan_Editor/en\|testplan editor]]. 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.		Older versions of expecco included also Report Parameter settings here. These are now kept as [[ReportTemplate_Element/en\|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.

	;Use Values of the User Activity-Log Settings		;Use Values of the User Activity-Log Settings

Alkurz: /* Logging */

2024-05-15T09:40:50Z

Logging

← Nächstältere Version		Version vom 15. Mai 2024, 09:40 Uhr
Zeile 68:		Zeile 68:
	----		----

	;Trace [[Glossary/en#Stdout \| Stdout]] and [[Glossary/en#Stderr \| Stderr]] on [[Transcript]]		;Trace [[Glossary/en#Stdout \| Stdout]] and [[Glossary/en#Stderr \| Stderr]] on [[Tools_Transcript/en\|Transcript]]
	:If enabled, the Stdout and Stderr are shown on the transcript.		:If enabled, the Stdout and Stderr are shown on the transcript.

Alkurz: /* Execution Settings */

2024-05-15T09:36:38Z

Execution Settings

← Nächstältere Version		Version vom 15. Mai 2024, 09:36 Uhr
Zeile 2:		Zeile 2:
	The execution editor is used to modify the execution settings of a [[TestSuite Element\|test suite]]. It is located under the "''Execution''" tab when the test suite element (the top element) is selected in the navigation tree.		The execution editor is used to modify the execution settings of a [[TestSuite Element\|test suite]]. It is located under the "''Execution''" tab when the test suite element (the top element) is selected in the navigation tree.

	== Execution ~~Settings~~ ==		== Execution ==
	;Use Values of the User Execution Settings		;Use Values of the User Execution Settings
	:The following settings are also defined in the user execution settings. If this option is activated, the values from the user execution settings are used, otherwise the values defined here in the test suite are used		:The following settings are also defined in the user execution settings. If this option is activated, the values from the user execution settings are used, otherwise the values defined here in the test suite are used
Zeile 26:		Zeile 26:
	:This parameter limits the max. execution time of cleanup actions. This allows for cleanup actions which try to communicate with dead connections to be terminated and thus avoids blocking. If a cleanup action executes longer, a dialog is shown, asking if a hard termination (i.e. termination without cleanup) or a wait for the action is desired by the user. If expecco is executed in non-interactive mode (slave-mode or executed via command line), the dialog is not shown. Instead, the cleanup action is hard terminated automatically after the max. cleanup time.		:This parameter limits the max. execution time of cleanup actions. This allows for cleanup actions which try to communicate with dead connections to be terminated and thus avoids blocking. If a cleanup action executes longer, a dialog is shown, asking if a hard termination (i.e. termination without cleanup) or a wait for the action is desired by the user. If expecco is executed in non-interactive mode (slave-mode or executed via command line), the dialog is not shown. Instead, the cleanup action is hard terminated automatically after the max. cleanup time.

			== Probes ==
	----

	;Set probe mode to checking		;Set probe mode to checking

Alkurz: /* Logging Settings */

2024-05-15T09:36:00Z

Logging Settings

← Nächstältere Version		Version vom 15. Mai 2024, 09:36 Uhr
Zeile 44:		Zeile 44:
	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".		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~~ ==		== Logging ==
	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.		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.

Alkurz: /* Inventory */

2024-05-15T09:35:31Z

Inventory

← Nächstältere Version		Version vom 15. Mai 2024, 09:35 Uhr
Zeile 31:		Zeile 31:
	:If there are [[Probe\|Probes]] in your test suite, set them to checking mode.		:If there are [[Probe\|Probes]] in your test suite, set them to checking mode.

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

	;Default Inventory		;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.		:Specifies the set of resources which are available during developing and tests of the testsuite. This resource template might differ to the ALM Template.

	;~~ExpeccoNET~~ Template		;ALM Template
	:Optional Resources used by expeccoNET. If unspecified, the default inventory will be used.		:Optional Resources used by ALM/expeccoNET. If unspecified, the default inventory will be used.

	== User Interface ==		== User Interface ==

Alkurz am 15. Mai 2024 um 09:33 Uhr

2024-05-15T09:33:14Z

← Nächstältere Version		Version vom 15. Mai 2024, 09:33 Uhr
Zeile 1:		Zeile 1:
	[[Bild:Execution ~~Editor~~.png\|thumb\|300px\|Execution Editor]]		[[Bild:Execution Editor_en.png\|thumb\|300px\|Execution Editor]]
	The execution editor is used to modify the execution settings of a [[TestSuite Element\|test suite]]. It is located under the "''Execution''" tab when the test suite element (the top element) is selected in the navigation tree.		The execution editor is used to modify the execution settings of a [[TestSuite Element\|test suite]]. It is located under the "''Execution''" tab when the test suite element (the top element) is selected in the navigation tree.

	== Execution Settings ==		== Execution Settings ==
			;Use Values of the User Execution Settings
			:The following settings are also defined in the user execution settings. If this option is activated, the values from the user execution settings are used, otherwise the values defined here in the test suite are used

	;Separate Processes for Long-Running Activities		;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.)		: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.)
Zeile 9:		Zeile 12:
	: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.		: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		;Max. Number of Activity 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.		: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.

			;Separate Processes for Suspended Activities
			:Due to the fact that starting up new processes (execution threads) is a relatively 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 creating 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. Recursion Level
			:This parameter limits the nesting of activities during execution (i.e. the nesting of compound activities which invokes another compound activity). If this limit is reached, an error is raised, which leads to the current test case to be reported as erroneous.

			:Effectively, expecco will keep a pool of worker threads for execution, which process pending activities. The max. number of worker threads is set by this parameter.

			;Max. Cleanup Time
			:This parameter limits the max. execution time of cleanup actions. This allows for cleanup actions which try to communicate with dead connections to be terminated and thus avoids blocking. If a cleanup action executes longer, a dialog is shown, asking if a hard termination (i.e. termination without cleanup) or a wait for the action is desired by the user. If expecco is executed in non-interactive mode (slave-mode or executed via command line), the dialog is not shown. Instead, the cleanup action is hard terminated automatically after the max. cleanup time.

			----

	;Set probe mode to checking		;Set probe mode to checking
	:If there are [[Probe\|Probes]] in your test suite, set them to checking mode.		:If there are [[Probe\|Probes]] in your test suite, set them to checking mode.

	These defaults can also be changed in the more convenient [[Settings#Execution Settings\|settings dialog]].

	== Inventory ==		== Inventory ==
Zeile 34:		Zeile 48:

	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.		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.

			;Use Values of the User Activity-Log Settings
			:The following settings are also defined in the user activity-log settings. If this option is activated, the values from the user activity-log settings are used, otherwise the values defined here in the test suite are used

	;Log Activities		;Log Activities
Zeile 39:		Zeile 56:
	:If disabled, only failed activities are stored.		:If disabled, only failed activities are stored.
	:At least there is one activity log, which keeps the whole information about the execution.		:At least there is one activity log, which keeps the whole information about the execution.

		⚫	;Max. Number of kept Subactivities per [[Executor#Activity\|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.<br>The default setting is specified in the testsuite.

	;Log Pin Data		;Log Pin Data
	:If enabled, all input and output pin values are stored in the activity log. Otherwise all values are discarded.		: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		;Log Info
	:If enabled, all information messages are stored in the activity log. Otherwise all information messages are discarded.		: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 [[Glossary/en#Stdout \| Stdout]] and [[Glossary/en#Stderr \| Stderr]] on [[Transcript]]		;Trace [[Glossary/en#Stdout \| Stdout]] and [[Glossary/en#Stderr \| Stderr]] on [[Transcript]]
	:If enabled, the Stdout and Stderr are shown on the transcript.		:If enabled, the Stdout and Stderr are shown on the transcript.

⚫	;Max. Number of kept Subactivities per [[Executor#Activity\|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.<br>The default setting is specified in the testsuite.

	The default values can also be changed in the more convenient [[Settings#Logging Settings\|settings dialog]].		The default values can also be changed in the more convenient [[Settings#Logging Settings\|settings dialog]].

Cg am 26. August 2019 um 13:50 Uhr

2019-08-26T13:50:17Z

← Nächstältere Version		Version vom 26. August 2019, 13:50 Uhr
Zeile 1:		Zeile 1:
	[[Bild:Execution Editor.png\|thumb\|300px\|Execution Editor]]		[[Bild:Execution Editor.png\|thumb\|300px\|Execution Editor]]
	The execution editor is used to modify the execution settings of a [[TestSuite Element\|test suite]]. It ~~can~~ be ~~found on~~ the "Execution" tab ~~after~~ ~~selecting~~ the ~~testsuite~~ in the navigation tree.		The execution editor is used to modify the execution settings of a [[TestSuite Element\|test suite]]. It is located under the "''Execution''" tab when the test suite element (the top element) is selected in the navigation tree.

	== Execution Settings ==		== Execution Settings ==

Cg: /* Logging Settings */

2019-02-26T16:14:29Z

Logging Settings

← Nächstältere Version		Version vom 26. Februar 2019, 16:14 Uhr
Zeile 48:		Zeile 48:
	:The default setting is specified in the testsuite.		:The default setting is specified in the testsuite.

	;Trace [[Stdout]] and [[Stderr]] on [[Transcript]]		;Trace [[Glossary/en#Stdout \| Stdout]] and [[Glossary/en#Stderr \| Stderr]] on [[Transcript]]
	:If enabled, the Stdout and Stderr are shown on the transcript.		:If enabled, the Stdout and Stderr are shown on the transcript.

Mawalch am 11. Februar 2018 um 20:21 Uhr

2018-02-11T20:21:43Z

← Nächstältere Version		Version vom 11. Februar 2018, 20:21 Uhr
Zeile 4:		Zeile 4:
	== Execution Settings ==		== Execution Settings ==
	;Separate Processes for Long-Running Activities		;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.)		: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		;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.		: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		;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.		: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		;Set probe mode to checking
Zeile 33:		Zeile 33:
	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.		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.		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		;Log Activities
Zeile 51:		Zeile 51:
	:If enabled, the Stdout and Stderr are shown on the transcript.		:If enabled, the Stdout and Stderr are shown on the transcript.

	;Max. Number of kept Subactivities per [[Executor#~~Activiy¦~~Activity]]		;Max. Number of kept Subactivities per [[Executor#Activity\|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.<br>The default setting is specified in the testsuite.		: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.<br>The default setting is specified in the testsuite.


	The default values can also be changed in the more convenient [[Settings#Logging Settings\|settings dialog]].		The default values can also be changed in the more convenient [[Settings#Logging Settings\|settings dialog]].

Sv am 14. April 2014 um 10:15 Uhr

2014-04-14T10:15:56Z

← Nächstältere Version		Version vom 14. April 2014, 10:15 Uhr
Zeile 1:		Zeile 1:
	[[Bild:Execution Editor.png\|thumb\|300px\|Execution Editor]]		[[Bild:Execution Editor.png\|thumb\|300px\|Execution Editor]]
	The execution editor is used to modify the execution settings of a [[TestSuite Element]]. It can be found on the "Execution" tab after selecting the testsuite in the navigation tree.		The execution editor is used to modify the execution settings of a [[TestSuite Element\|test suite]]. It can be found on the "Execution" tab after selecting the testsuite in the navigation tree.

	== Execution Settings ==		== Execution Settings ==
Zeile 51:		Zeile 51:
	:If enabled, the Stdout and Stderr are shown on the transcript.		:If enabled, the Stdout and Stderr are shown on the transcript.

	;Max. Number of kept Subactivities per [[Executor#Activiy]]		;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.<br>The default setting is specified in the testsuite.		: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.<br>The default setting is specified in the testsuite.