Testsuite Editor-Metadata Editor/en - Versionsgeschichte

Cg: /* Include Imported Menus */

2025-02-14T11:08:22Z

Include Imported Menus

← Nächstältere Version		Version vom 14. Februar 2025, 11:08 Uhr
Zeile 51:		Zeile 51:
	==== Include Imported Menus ====		==== Include Imported Menus ====
	If this flag is checked, operation menu entries from imported libraries are also included.		If this flag is checked, operation menu entries from imported libraries are also included.

			==== Include Flat ====
			Controls if included imported menus are shown on the same level as any menu action defined here, or else to be presented as a submenu (one level down).

	==== Background Menu Actions ====		==== Background Menu Actions ====

Cg: /* Testplan Execution */

2025-02-14T11:05:54Z

Testplan Execution

← Nächstältere Version		Version vom 14. Februar 2025, 11:05 Uhr
Zeile 65:		Zeile 65:

	Also notice: errors in these actions may open a debugger, ignoring your "''Open Debugger on Error''" settings.		Also notice: errors in these actions may open a debugger, ignoring your "''Open Debugger on Error''" settings.

			=== Compatibility ===

			* No text expansion of freeze values (pre 19.2 compatibility)
			: Prior to vsn19.2, $(...) variables were not expanded in freeze values.
			: If your suite was created before, and contains such suchstrings, you should set this flag. Notice that this release is now more than 5 years old, and it is unlikely that you are affected by this.
			* 2.7.5 Compatibility
			: This enforces compatibility with an even older release. This flag will vanish in the near future.
			* Must be same version in all imports
			: If this flag is set, this library may never be imported in multiple different versions, to ensure that any change is consistently present in all imports. This affects libraries which are imported on different levels (i.e. an imported library which also imports this library). This is especially useful if the library contains type definitions which are to be the same in all situations.

	[[Category: Editors]]		[[Category: Editors]]

Cg: /* GUI Extensions */

2020-02-18T16:47:20Z

GUI Extensions

← Nächstältere Version		Version vom 18. Februar 2020, 16:47 Uhr
Zeile 40:		Zeile 40:

	=== GUI Extensions ===		=== GUI Extensions ===
			==== Operation Menu ====
	Allows for a folder full of actions to be attached to expecco's main-menu. If a folder is dropped into that field, all of that folder's actions are presented as menu items in the [[ExtrasMenu \| "''Extras''" menu]] (or optionally in the main menu).		Allows for a folder full of actions to be attached to expecco's main-menu. If a folder is dropped into that field, all of that folder's actions are presented as menu items in the [[ExtrasMenu \| "''Extras''" menu]] (or optionally in the main menu).
	This is very useful to make common functions (calibration, test-setup, tear-down etc.) easily accessible to the test-operator.		This is very useful to make common functions (calibration, test-setup, tear-down etc.) easily accessible to the test-operator.

Cg: /* GUI Extensions */

2020-02-18T16:35:46Z

GUI Extensions

← Nächstältere Version		Version vom 18. Februar 2020, 16:35 Uhr
Zeile 46:		Zeile 46:

	==== In Main Menu ====		==== In Main Menu ====
	If this flag is checked, the operations menu is shown as a separate entry in the main menu. Otherwise the items are sliced into the "''Extras''" menu.		If this flag is checked, the operations menu is shown as a separate entry in the main menu. Otherwise the items are sliced into the [[ExtrasMenu \| "''Extras''" menu]].

	==== Include Imported Menus ====		==== Include Imported Menus ====

Cg: /* GUI Extensions */

2020-02-18T16:32:46Z

GUI Extensions

← Nächstältere Version		Version vom 18. Februar 2020, 16:32 Uhr
Zeile 40:		Zeile 40:

	=== GUI Extensions ===		=== GUI Extensions ===
	Allows for a folder full of actions to be attached to expecco's main-menu. If a folder is dropped into that field, all of that folder's actions are presented as menu items in the "''Extras''" menu (or optionally in the main menu).		Allows for a folder full of actions to be attached to expecco's main-menu. If a folder is dropped into that field, all of that folder's actions are presented as menu items in the [[ExtrasMenu \| "''Extras''" menu]] (or optionally in the main menu).
	This is very useful to make common functions (calibration, test-setup, tear-down etc.) easily accessible to the test-operator.		This is very useful to make common functions (calibration, test-setup, tear-down etc.) easily accessible to the test-operator.

Cg: /* GUI Extensions */

2020-02-18T16:21:17Z

GUI Extensions

← Nächstältere Version		Version vom 18. Februar 2020, 16:21 Uhr
Zeile 40:		Zeile 40:

	=== GUI Extensions ===		=== GUI Extensions ===
	Allows for a folder full of actions to be attached to expecco's main-menu. If a folder is dropped into that field, all of that folder's actions are presented as menu items in the "''~~Extra~~''" menu (or optionally in the main menu).		Allows for a folder full of actions to be attached to expecco's main-menu. If a folder is dropped into that field, all of that folder's actions are presented as menu items in the "''Extras''" menu (or optionally in the main menu).
	This is very useful to make common functions (calibration, test-setup, tear-down etc.) easily accessible to the test-operator.		This is very useful to make common functions (calibration, test-setup, tear-down etc.) easily accessible to the test-operator.

Cg: /* In Main Menu */

2020-02-18T16:21:04Z

In Main Menu

← Nächstältere Version		Version vom 18. Februar 2020, 16:21 Uhr
Zeile 46:		Zeile 46:

	==== In Main Menu ====		==== In Main Menu ====
	If this flag is checked, the operations menu is shown as a separate entry in the main menu. Otherwise the items are sliced into the "''~~Extra~~''" menu.		If this flag is checked, the operations menu is shown as a separate entry in the main menu. Otherwise the items are sliced into the "''Extras''" menu.

	==== Include Imported Menus ====		==== Include Imported Menus ====

Cg: /* GUI Extensions */

2020-02-18T16:20:52Z

GUI Extensions

← Nächstältere Version		Version vom 18. Februar 2020, 16:20 Uhr
Zeile 40:		Zeile 40:

	=== GUI Extensions ===		=== GUI Extensions ===
	Allows for a folder full of actions to be attached to expecco's main-menu. If a folder is dropped into that field, all of that folder's actions are presented as menu items in the "Extra" menu (or optionally in the main menu).		Allows for a folder full of actions to be attached to expecco's main-menu. If a folder is dropped into that field, all of that folder's actions are presented as menu items in the "''Extra''" menu (or optionally in the main menu).
	This is very useful to make common functions (calibration, test-setup, tear-down etc.) easily accessible to the test-operator.		This is very useful to make common functions (calibration, test-setup, tear-down etc.) easily accessible to the test-operator.

Zeile 46:		Zeile 46:

	==== In Main Menu ====		==== In Main Menu ====
	If this flag is checked, the operations menu is shown as a separate entry in the main menu. Otherwise the items are sliced into the "Extra" menu.		If this flag is checked, the operations menu is shown as a separate entry in the main menu. Otherwise the items are sliced into the "''Extra''" menu.

	==== Include Imported Menus ====		==== Include Imported Menus ====

Cg: /* Testplan Execution */

2020-02-18T16:20:08Z

Testplan Execution

← Nächstältere Version		Version vom 18. Februar 2020, 16:20 Uhr
Zeile 56:		Zeile 56:

	=== Testplan Execution ===		=== Testplan Execution ===
	Allows for additional pre- and post-execution actions to be automatically executed with any test plan execution. Different actions can be specified depending on the test plan's outcome, for example to trigger further reporting or alarm processing. It may also be used to add actions which send email notifications or which contact a QM-system for automatic issue generation (e.g. into Bugzilla, ~~jira~~ or other bug tracking systems).		Allows for additional pre- and post-execution actions to be automatically executed with any test plan execution. Different actions can be specified depending on the test plan's outcome, for example to trigger further reporting or alarm processing. They may also be used to add actions which send email notifications or which contact a QM-system for automatic issue generation (e.g. into Bugzilla, Jira or other bug tracking systems).

	[[Datei:point_right.png\|20px]] Notice: These actions are not logged in the activity-log. Because they are not logged, they should not have any influence on the actual test execution. Especially, they should not be used to setup equipment, protocols etc.		[[Datei:point_right.png\|20px]] Notice: These actions are not logged in the activity-log. Because they are not logged, they should not have any influence on the actual test execution. Especially, they should not be used to setup equipment, protocols etc.

Cg: /* Background Menu Actions */

2020-01-24T00:07:33Z

Background Menu Actions

← Nächstältere Version		Version vom 24. Januar 2020, 00:07 Uhr
Zeile 53:		Zeile 53:
	==== Background Menu Actions ====		==== Background Menu Actions ====
	By default, the menu operations are synchronous, which means that expecco waits for the action to finish. While executing, the expecco UI is blocked. If that is not desired, or if an action needs to remain active during the whole test execution (for example, if a shell script is to be executed in parallel), append an ampersand character ("&") to the action's name. In that case, the menu item will execute the block in a separate thread in the background. This is especially useful to start external programs, Java bridges or the System Under Test itself.		By default, the menu operations are synchronous, which means that expecco waits for the action to finish. While executing, the expecco UI is blocked. If that is not desired, or if an action needs to remain active during the whole test execution (for example, if a shell script is to be executed in parallel), append an ampersand character ("&") to the action's name. In that case, the menu item will execute the block in a separate thread in the background. This is especially useful to start external programs, Java bridges or the System Under Test itself.
		⚫	<br>See more in [[User_Defined_Menu_Items \| User Defined Menu Items]]

⚫	See more [[User_Defined_Menu_Items \| ~~here~~]]

	=== Testplan Execution ===		=== Testplan Execution ===