User Defined Menu Items - Versionsgeschichte

Cg: /* Errors in a Background Action */

2023-07-14T08:48:27Z

Errors in a Background Action

← Nächstältere Version		Version vom 14. Juli 2023, 08:48 Uhr
Zeile 122:		Zeile 122:
	Either kill all Background actions via the "''Extras''" → "''Debugging''" → "''Stop all Executions''" menu item, or open a process monitor ("''Extras''" → "''Debugging''" → "''Process Monitor''"), find an individual background action's process in the list and terminate it there.		Either kill all Background actions via the "''Extras''" → "''Debugging''" → "''Stop all Executions''" menu item, or open a process monitor ("''Extras''" → "''Debugging''" → "''Process Monitor''"), find an individual background action's process in the list and terminate it there.

	=== Errors in a ~~Background~~ Action ===		=== Errors in a Menu Action ===
	It is best to try any ~~background~~ action first by executing it as usual, with all its debug- and logging features available.		It is best to try any menu action first by executing it as usual, with all its debug- and logging features available.
	To ~~make~~ ~~sure,~~ ~~that your~~ background action does not interfere with your test's interactions (e.g. by popping up a dialog at unexpected times, or by entering an endless loop).		If it is a background menu action, make sure that it does not interfere with your test's interactions (e.g. by popping up a dialog at unexpected times, or by entering an endless loop).

	Make sure that exceptions are handled gracefully, so that the ~~background~~ action finishes with success.		Make sure that exceptions are handled gracefully, so that the action finishes with success.

	If any unhandled exception happens (or it finishes with fail, error or inconclusive), a popup confirmation dialog is shown, offering a chance to see the activity log which lead to that situation. Of course, ~~that~~ ~~information~~ is under the ~~same~~ control of any "''skip in log''" flags set in steps or actions. And also under control of the global "''ignore skip in log settings''" flag, which is found in the user's settings ("''Extras''" - "''Settings''" - "''Execution''" - "''Activity Log''" - "''Ignore Any Skip in Log''").		If any unhandled exception happens (or it finishes with fail, error or inconclusive), a popup confirmation dialog is shown, offering a chance to see the activity log which lead to that situation. Of course, the amount of detail is under the control of any "''skip in log''" flags as set in steps and actions. And also under control of the global "''ignore skip in log settings''" flag, which is found in the user's settings ("''Extras''" - "''Settings''" - "''Execution''" - "''Activity Log''" - "''Ignore Any Skip in Log''").

Cg: /* Debugging Custom Menu Operations */

2023-07-14T08:04:05Z

Debugging Custom Menu Operations

← Nächstältere Version		Version vom 14. Juli 2023, 08:04 Uhr
Zeile 45:		Zeile 45:

	Custom menu functions are harder to debug than regular action blocks, because when executed, there is no test/demo page, in which an activity-log is shown.		Custom menu functions are harder to debug than regular action blocks, because when executed, there is no test/demo page, in which an activity-log is shown.
	By default, if any error occurs inside the menu operation, it is simply cancelled. A short error message is shown in the lower information area, ~~though~~.		By default, if any error occurs inside the menu operation, it is simply cancelled and a short error message is shown in the lower information area. With release 23.1, this was changed to show a warn dialog, and an option to show the activity log (see below).

	You can place a breakpoint in an elementary block and enable the "''Debug all Exceptions''" flag in the "''Execution Settings''".		You can place a breakpoint in an elementary block and enable the "''Debug all Exceptions''" flag in the "''Execution Settings''".

	You can also send trace messages to the Transcript or Stdout.		You can also send trace messages to the Transcript or Stdout.
	Sorry, but breakpoints on an activity step or single stepping are currently not ~~possible~~ ~~for~~ an ~~action started via the menu~~.		Sorry, but breakpoints on an activity step or single stepping are currently not allowed in menu actions.
	<br>We recommend to first test the action in a regular "Test/Demo" page.		<br>We recommend to first test the action in a regular "''Test/Demo''" page.

	=== Useful Building Blocks for Custom Menu Operations ===		=== Useful Building Blocks for Custom Menu Operations ===

Cg: /* Defining a Custom Menu Operation */

2023-07-14T07:59:17Z

Defining a Custom Menu Operation

← Nächstältere Version		Version vom 14. Juli 2023, 07:59 Uhr
Zeile 27:		Zeile 27:
	* give the block a useful name - the name of the block will later be shown as the label of the menu item.		* give the block a useful name - the name of the block will later be shown as the label of the menu item.
	[[Datei:CreateCustomMenu2.png]]		[[Datei:CreateCustomMenu2.png]]
	* navigate to the testsuite's "Misc" page		* navigate to the testsuite's "''Misc''" page
	[[Datei:CreateCustomMenu3.png]]		[[Datei:CreateCustomMenu3.png]]
	* drag the folder (Custom Menu Operations) into the "GUI-Extensions"-"Operation Menu" field.		* drag the folder ("Custom Menu Operations") into the "''GUI-Extensions''" - "''Operation Menu''" field.
	And "''Accept''" the change (click on "Accept").		And "''Accept''" the change (click on "Accept").

	[[Datei:CreateCustomMenu4.png]]		[[Datei:CreateCustomMenu4.png]]

	You are now ready to use the new operation; you will find a new menu item named "Hello" in the "~~Extra~~" menu:		You are now ready to use the new operation; you will find a new menu item named "''Hello''" in the "''Extras''" menu:

	[[Datei:CreateCustomMenu5.png]]		[[Datei:CreateCustomMenu5.png]]

Cg: /* Useful Operations of a Custom Menu */

2023-07-14T07:57:15Z

Useful Operations of a Custom Menu

← Nächstältere Version		Version vom 14. Juli 2023, 07:57 Uhr
Zeile 7:		Zeile 7:
	The following is a partial list of what can and has been done with this feature in the past (by customers):		The following is a partial list of what can and has been done with this feature in the past (by customers):

	* Startup / Shutdown of the System Under Test (usually ~~blocks~~ which ~~execute~~ shell scripts)		* Startup / Shutdown of the System Under Test (usually actions which run shell scripts)
	* Startup / Shutdown of Java Bridge connections		* Startup / Shutdown of Java Bridge connections
	* Creation of test data files		* Creation of test data files
Zeile 14:		Zeile 14:
	* Opening a Java GUI on an attachment's contents via the Java Bridge		* Opening a Java GUI on an attachment's contents via the Java Bridge
	* Bulk generation of empty TestCase templates from an imported CSV file		* Bulk generation of empty TestCase templates from an imported CSV file
			* Starting mock/simulated services
			* Load test specifications from a custom data base
			* Upload results to a custom data base

	=== Defining a Custom Menu Operation ===		=== Defining a Custom Menu Operation ===

Cg: /* Killing (Background) Actions */

2023-07-14T07:55:03Z

Killing (Background) Actions

← Nächstältere Version		Version vom 14. Juli 2023, 07:55 Uhr
Zeile 117:		Zeile 117:
	=== Killing (Background) Actions ===		=== Killing (Background) Actions ===
	Either kill all Background actions via the "''Extras''" → "''Debugging''" → "''Stop all Executions''" menu item, or open a process monitor ("''Extras''" → "''Debugging''" → "''Process Monitor''"), find an individual background action's process in the list and terminate it there.		Either kill all Background actions via the "''Extras''" → "''Debugging''" → "''Stop all Executions''" menu item, or open a process monitor ("''Extras''" → "''Debugging''" → "''Process Monitor''"), find an individual background action's process in the list and terminate it there.

			=== Errors in a Background Action ===
			It is best to try any background action first by executing it as usual, with all its debug- and logging features available.
			To make sure, that your background action does not interfere with your test's interactions (e.g. by popping up a dialog at unexpected times, or by entering an endless loop).

			Make sure that exceptions are handled gracefully, so that the background action finishes with success.

			If any unhandled exception happens (or it finishes with fail, error or inconclusive), a popup confirmation dialog is shown, offering a chance to see the activity log which lead to that situation. Of course, that information is under the same control of any "''skip in log''" flags set in steps or actions. And also under control of the global "''ignore skip in log settings''" flag, which is found in the user's settings ("''Extras''" - "''Settings''" - "''Execution''" - "''Activity Log''" - "''Ignore Any Skip in Log''").

Cg: /* Asynchronous (Background) Actions */

2023-07-14T07:38:42Z

Asynchronous (Background) Actions

← Nächstältere Version		Version vom 14. Juli 2023, 07:38 Uhr
Zeile 93:		Zeile 93:
	By default, custom menu actions are blocking. This means that the expecco UI is not responding while the menu operation is being executed. This is OK for typical operations as listed above, but is inconvenient if the menu operation is itself a long time running operation.		By default, custom menu actions are blocking. This means that the expecco UI is not responding while the menu operation is being executed. This is OK for typical operations as listed above, but is inconvenient if the menu operation is itself a long time running operation.

	It is especially inconvenient if the operation consists of a daemon process, for example to simulate a communication partner, a web service, a monitor or other task, which has to run in parallel with the test execution.		It is especially inconvenient if the operation consists of a daemon process, for example to simulate a communication partner, a web service, a monitor or other task, which has to run in parallel with the test execution. For example, you may want to have a menu item to start a mockup service (e.g. HTTP or SOAP) for development of the test, but not when the suite runs in the production cycle.

	Of course, it is always possibly to open another expecco window, and execute such an action in the second window, but this will lead to a number of blocked expecco windows being present.		Of course, it is always possibly to open another expecco window, and execute such an action in the second window, but this will lead to a number of blocked expecco windows being present (although it might be useful to see the activities execute there).

	To make a custom operation execute in the background (i.e. in parallel) without a need for a second window, place an ampersand character ("&") behind the action's name (e.g. rename the action to something like "Start Foo&".		To make a custom operation execute in the background (i.e. in parallel) without a need for a second window, place an '''ampersand character''' ("&") behind the action's name (e.g. rename the action to something like "''Start Foo &''".
	Then, when selected via the menu, the action will be started as a background task, and expecco will immediately return from the menu action.		Then, when selected via the menu, the action will be started as a background task, and expecco will immediately return from the menu action.

Zeile 109:		Zeile 110:
	* if no other window is open on the same suite, you will be asked if the background actions are to be terminated.		* if no other window is open on the same suite, you will be asked if the background actions are to be terminated.

	The process monitor will always show all background actions in the system - regardless from which window they were started.		The process monitor ("''Extras''" - "''Debugging''" - "''Process Monitor''") will always show all background actions in the system - regardless from which window they were started.
	Therefore, in any case, these can always be terminated at any time via this tool.		Therefore, in any case, these can always be terminated at any time via this tool.

Cg: /* Killing (Background) Actions */

2020-02-13T13:24:31Z

Killing (Background) Actions

← Nächstältere Version		Version vom 13. Februar 2020, 13:24 Uhr
Zeile 115:		Zeile 115:

	=== Killing (Background) Actions ===		=== Killing (Background) Actions ===
	Either kill all Background actions via the "''Extras''" → "''Debugging''" → "''Stop all Executions''" menu item, or open a process monitor ("''Extras''" → "''Debugging''" → "''Process Monitor''", find an individual background action's process in the list and terminate it there.		Either kill all Background actions via the "''Extras''" → "''Debugging''" → "''Stop all Executions''" menu item, or open a process monitor ("''Extras''" → "''Debugging''" → "''Process Monitor''"), find an individual background action's process in the list and terminate it there.

Cg: /* Killing (Background) Actions */

2020-02-13T13:24:19Z

Killing (Background) Actions

← Nächstältere Version		Version vom 13. Februar 2020, 13:24 Uhr
Zeile 115:		Zeile 115:

	=== Killing (Background) Actions ===		=== Killing (Background) Actions ===
	Either kill all Background actions via the "''Extras''" → "''Debugging''" → "''Stop all Executions''" menu item, or open a process monitor ("''Extras''" → "''Debugging''" → "''Process Monitor''", find ~~the~~ ~~Background~~ action's process in the list and terminate it there.		Either kill all Background actions via the "''Extras''" → "''Debugging''" → "''Stop all Executions''" menu item, or open a process monitor ("''Extras''" → "''Debugging''" → "''Process Monitor''", find an individual background action's process in the list and terminate it there.

Cg: /* Asynchronous (Background) Actions */

2020-02-13T13:23:57Z

Asynchronous (Background) Actions

← Nächstältere Version		Version vom 13. Februar 2020, 13:23 Uhr
Zeile 113:		Zeile 113:

	Background actions are always terminated, when the last expecco window is closed (they are lightweight threads, and will not stay alive after the expecco session).		Background actions are always terminated, when the last expecco window is closed (they are lightweight threads, and will not stay alive after the expecco session).

			=== Killing (Background) Actions ===
			Either kill all Background actions via the "''Extras''" → "''Debugging''" → "''Stop all Executions''" menu item, or open a process monitor ("''Extras''" → "''Debugging''" → "''Process Monitor''", find the Background action's process in the list and terminate it there.

Cg: /* Asynchronous (Background) Actions */

2020-02-13T13:21:13Z

Asynchronous (Background) Actions

← Nächstältere Version		Version vom 13. Februar 2020, 13:21 Uhr
Zeile 91:		Zeile 91:
	=== Asynchronous (Background) Actions ===		=== Asynchronous (Background) Actions ===

	By default, custom menu actions are blocking. This means that the UI is not responding while the menu operation is being executed. This is OK for typical operations as listed above, but is inconvenient if the menu operation is itself a long time running operation.		By default, custom menu actions are blocking. This means that the expecco UI is not responding while the menu operation is being executed. This is OK for typical operations as listed above, but is inconvenient if the menu operation is itself a long time running operation.

	It is especially inconvenient if the operation consists of a daemon process, for example to simulate a communication partner, a web service, a monitor or other task, which has to run in parallel with the test execution.		It is especially inconvenient if the operation consists of a daemon process, for example to simulate a communication partner, a web service, a monitor or other task, which has to run in parallel with the test execution.