DiagramElements-Step/en - Versionsgeschichte

Cg: /* See also */

2021-12-06T09:45:36Z

Cg am 6. Dezember 2021 um 09:43 Uhr

2021-12-06T09:43:53Z

← Nächstältere Version		Version vom 6. Dezember 2021, 09:43 Uhr
Zeile 134:		Zeile 134:
	For this, add a timeout (say 5 seconds), and set one of the "''Ignore Exceptions''" or the "''Timeout is OK''" flags of the step. Of course, you should then decide if the timeout should be interpreted as confirmation or as rejection, by continuing execution along either the "''Trigger-out''" or the "''Exception-out''" pin.		For this, add a timeout (say 5 seconds), and set one of the "''Ignore Exceptions''" or the "''Timeout is OK''" flags of the step. Of course, you should then decide if the timeout should be interpreted as confirmation or as rejection, by continuing execution along either the "''Trigger-out''" or the "''Exception-out''" pin.

			==See also==
	~~See also:~~ [[Block Element]], [[Executor#Activity\|Activity]], [[DiagramElements-Pin\|Pin]], [[DiagramElements-Connection\|Connection]]		[[Block Element]], [[Executor#Activity\|Activity]], [[DiagramElements-Pin\|Pin]], [[DiagramElements-Connection\|Connection]]

Cg: /* Auto-Closing of Interactive Dialog Actions */

2021-12-06T07:44:30Z

Auto-Closing of Interactive Dialog Actions

← Nächstältere Version		Version vom 6. Dezember 2021, 07:44 Uhr
Zeile 134:		Zeile 134:
	For this, add a timeout (say 5 seconds), and set one of the "''Ignore Exceptions''" or the "''Timeout is OK''" flags of the step. Of course, you should then decide if the timeout should be interpreted as confirmation or as rejection, by continuing execution along either the "''Trigger-out''" or the "''Exception-out''" pin.		For this, add a timeout (say 5 seconds), and set one of the "''Ignore Exceptions''" or the "''Timeout is OK''" flags of the step. Of course, you should then decide if the timeout should be interpreted as confirmation or as rejection, by continuing execution along either the "''Trigger-out''" or the "''Exception-out''" pin.

	See also: [[Block Element]], [[Executor#Activity\|Activity]], [[DiagramElements-Pin]], [[DiagramElements-Connection]]		See also: [[Block Element]], [[Executor#Activity\|Activity]], [[DiagramElements-Pin\|Pin]], [[DiagramElements-Connection\|Connection]]

Cg: /* Augmenting the Step's Name in the Log */

2021-12-06T07:43:06Z

Augmenting the Step's Name in the Log

← Nächstältere Version		Version vom 6. Dezember 2021, 07:43 Uhr
Zeile 125:		Zeile 125:
	* %(END) - expands to the step's execution end timestamp		* %(END) - expands to the step's execution end timestamp
	* %(STATE) - expands to the step's outcome (fail, error, passed, inconclusive)		* %(STATE) - expands to the step's outcome (fail, error, passed, inconclusive)

			This has no effect on the step's operation; it only affects the generated activity log/test report.

	== Auto-Closing of Interactive Dialog Actions ==		== Auto-Closing of Interactive Dialog Actions ==

Cg: /* Augmenting the Step's Name in the Log */

2021-12-06T07:41:30Z

Augmenting the Step's Name in the Log

← Nächstältere Version		Version vom 6. Dezember 2021, 07:41 Uhr
Zeile 117:		Zeile 117:
	== Augmenting the Step's Name in the Log ==		== Augmenting the Step's Name in the Log ==

	If a ~~steps~~ name contains the substring %i, where i is a number from 1 to the number of input pins,		If a step's name contains the substring "%i", where i is a number from 1 to the number of input pins,
	the ~~step's~~ name is expanded by including the input pin's value string in the activity log.		the name is expanded by including the corresponding input pin's value-string in the activity log.
	I.e. if the input pin received a value of (say) 1234, then the step name "My Step (test data is %1)" will be shown as "My Step (test data is 123)".		I.e. if the input pin received a value of (say) 1234, then the step name "My Step (test data is %1)" will be shown as "My Step (test data is 123)".

Cg: /* Special Attributes of a Step */

2021-12-06T07:39:37Z

Special Attributes of a Step

Cg: /* Triggering a Step */

2021-12-06T07:33:51Z

Triggering a Step

← Nächstältere Version		Version vom 6. Dezember 2021, 07:33 Uhr
Zeile 77:		Zeile 77:
	A step in an activity diagram gets triggered when its required input values are available at its input pins. The details for triggering are described in [[DiagramElements-Pin#Input_Pins\|the pin documentation]], and are controlled by the number and type of input pins. However, the vast majority of actions are declared with a simple and intuitive "''All connected pins must have a value''" as triggering condition (the so called [[DiagramElements-Pin#Triggering_Behavior_when_Multiple_Inputs_are_Present\|"''And-Connected Trigger Condition''"]]).		A step in an activity diagram gets triggered when its required input values are available at its input pins. The details for triggering are described in [[DiagramElements-Pin#Input_Pins\|the pin documentation]], and are controlled by the number and type of input pins. However, the vast majority of actions are declared with a simple and intuitive "''All connected pins must have a value''" as triggering condition (the so called [[DiagramElements-Pin#Triggering_Behavior_when_Multiple_Inputs_are_Present\|"''And-Connected Trigger Condition''"]]).

	Actions with no input pins or where all input pins have constant "''freeze values''" usually have the "''Autostart''" attribute, which is described below.		Actions with no input pins or where all input pins have constant "''freeze values''" usually have either the "''Autostart''" attribute, or are triggered via a special "''Trigger Input''" pin, which are both described below.

	== Special Attributes of a Step ==		== Special Attributes of a Step ==

Cg: /* Introduction */

2021-12-06T07:31:11Z

Introduction

← Nächstältere Version		Version vom 6. Dezember 2021, 07:31 Uhr
Zeile 15:		Zeile 15:

	[[Datei:ActionInsideAnotherCompound.png\|mini\|Placed as a Step in another Compound Action]]		[[Datei:ActionInsideAnotherCompound.png\|mini\|Placed as a Step in another Compound Action]]

			[[Datei:AttachmentInDiagram.png\|mini\|Attachment Step in a Compound Action]]

	== Types of Steps ==		== Types of Steps ==

Cg: /* Introduction */

2021-12-06T07:19:34Z

Introduction

← Nächstältere Version		Version vom 6. Dezember 2021, 07:19 Uhr
Zeile 13:		Zeile 13:

	[[Datei:ActionInsideCompoundView.png\|mini\|Schema: Inside View of a Compound Action]]		[[Datei:ActionInsideCompoundView.png\|mini\|Schema: Inside View of a Compound Action]]

			[[Datei:ActionInsideAnotherCompound.png\|mini\|Placed as a Step in another Compound Action]]

	== Types of Steps ==		== Types of Steps ==

Cg: /* Introduction */

2021-12-06T07:18:19Z

Introduction

← Nächstältere Version		Version vom 6. Dezember 2021, 07:18 Uhr
Zeile 7:		Zeile 7:

	In workflow literature, the terms ''Activity'' and ''Action'' are used in the same tenor. However, in UML literature the terms "''Action''", "''Activity''" and "''Step''" are unfortunately used inconsistently. The expecco documentation strictly separates between "Action block" (= action definition), "Step" (= placed block) and "Activity" (= executed step). Please note that an action block can be placed (instantiated) several times as a step and multiple activities could be actively executing the same step's action.		In workflow literature, the terms ''Activity'' and ''Action'' are used in the same tenor. However, in UML literature the terms "''Action''", "''Activity''" and "''Step''" are unfortunately used inconsistently. The expecco documentation strictly separates between "Action block" (= action definition), "Step" (= placed block) and "Activity" (= executed step). Please note that an action block can be placed (instantiated) several times as a step and multiple activities could be actively executing the same step's action.

			[[Datei:ActionOutsideView.png\|mini\|Schema: Outside View of an Action]]

			[[Datei:ActionInsideElementaryView.png\|mini\|Schema: Inside View of an Elementary Action]]

			[[Datei:ActionInsideCompoundView.png\|mini\|Schema: Inside View of a Compound Action]]

	== Types of Steps ==		== Types of Steps ==

← Nächstältere Version		Version vom 6. Dezember 2021, 09:45 Uhr
Zeile 134:		Zeile 134:
	For this, add a timeout (say 5 seconds), and set one of the "''Ignore Exceptions''" or the "''Timeout is OK''" flags of the step. Of course, you should then decide if the timeout should be interpreted as confirmation or as rejection, by continuing execution along either the "''Trigger-out''" or the "''Exception-out''" pin.		For this, add a timeout (say 5 seconds), and set one of the "''Ignore Exceptions''" or the "''Timeout is OK''" flags of the step. Of course, you should then decide if the timeout should be interpreted as confirmation or as rejection, by continuing execution along either the "''Trigger-out''" or the "''Exception-out''" pin.

	==See ~~also~~==		==See Also==
	[[Block Element]], [[Executor#Activity\|Activity]], [[DiagramElements-Pin\|Pin]], [[DiagramElements-Connection\|Connection]]		[[Block Element]], [[Executor#Activity\|Activity]], [[DiagramElements-Pin\|Pin]], [[DiagramElements-Connection\|Connection]]

← Nächstältere Version		Version vom 6. Dezember 2021, 07:39 Uhr
Zeile 82:		Zeile 82:

	=== Autostart ===		=== Autostart ===
	This attribute is used for steps which have no input pin, for triggering, and for which no other external trigger input is available.		This attribute is used for steps which have no input pin for triggering, and for which no other external trigger input is available.

	In traditional activity diagrams, this would be called the "''Start''" step, although in expecco, any step can be made a start step, and multiple such "autostarted" steps may be present within a single activity diagram. This simplifies the diagram, as no extra start step (which would provide no other semantic operation) is needed. However, for those who prefer the traditional picture, a dummy "Start" action is provided in the standard library~~, which can be used as start step~~.		In traditional activity diagrams, this would be called the "''Start''" step, although in expecco, any step can be made a start step, and multiple such "autostarted" steps may be present within a single activity diagram. This simplifies the diagram, as no extra start step (which would provide no other semantic operation) is needed.<br>However, for those who prefer the traditional picture, a dummy "''Start''" action is also provided in the standard library.

	In the diagram, autostarted steps are marked with a special "execute" icon at the top-left corner of the step's picture (in older expecco versions, and some screen shots in the documentation, this used to be a yellow lightning symbol, but has been replaced with a gear-wheel like icon, as it tended to be misread as an exception picture).		In the diagram, autostarted steps are marked with a special "''execute''" icon at the top-left corner of the step's picture (in older expecco versions, and some screen shots in the documentation, this used to be a yellow lightning symbol, but has been replaced with a gear-wheel like icon, as it tended to be misread as an exception picture).

	=== Ignore Exceptions ===		=== Ignore Exceptions ===
	By default, an exception or error condition arising during a step's execution leads to the termination of the step's activity, and (unless handled) passed on to the caller activity. I.e. the step which is executing the faulty step's diagram is itself asked to handle the exception. This passing on of the exception continues until either the exception is handled via a step's [[DiagramElements-Pin#Exception Output Pin\|exception pin]] or the step has been marked as "ignoring exceptions", or no outer calling activity is present (i.e. the test case which initiated the action is reached).		By default, an exception or error condition arising during a step's execution leads to the termination of the step's activity, and unless handled, the exception is passed on to the caller activity. I.e. the step which is executing the faulty step's diagram is itself asked to handle the exception. This passing on of the exception continues until either the exception is handled via a step's [[DiagramElements-Pin#Exception Output Pin\|exception pin]] or the step has been marked as "ignoring exceptions", or no outer calling activity is present (i.e. the test case which initiated the action is reached).

	When a step ignores exceptions, it is terminated (and the optional exception output provides the exception information), but the diagram in which the faulting step is located is continued to be executed.		When a step ignores exceptions, it is terminated (and the optional exception output provides the exception information), but the diagram in which the faulting step is located is continued to be executed.
Zeile 100:		Zeile 100:
	=== Skipped Execution ===		=== Skipped Execution ===

	Individual steps in a diagram can be skipped by setting the "''Skipped Execution''" attribute. Such steps will not read any input data, not execute any action and not write any data ~~outputs~~.		Individual steps in a diagram can be skipped by setting the "''Skipped Execution''" attribute. Such steps will not read any input data, not execute any action and will not write to any data output pin.

	However, the [[DiagramElements-Pin#Enable Output Pin\|trigger output pin]] gets a value if present and connected. Therefore, steps in a control flow (i.e. only connected via ~~Enable~~-Input/~~Enable~~-Output pins) can be skipped without a need to short-circuit their control pins. Of course, as skipped pins do not generate any data output, any step which requires those output values would not be triggered.		However, the [[DiagramElements-Pin#Enable Output Pin\|trigger output pin]] gets a value if present and connected. Therefore, steps in a control flow (i.e. only connected via Trigger-Input/Trigger-Output pins) can be skipped without a need to short-circuit their control pins. Of course, as skipped pins do not generate any data output, any step which requires those output values would not be triggered.

	Skipping steps is mostly used when debugging test activities or to skip over long running initial steps when an activity needs to be restarted after a change. They are usually not used after the test development process, in a production test suite.		Skipping steps is mostly used when debugging test activities or to skip over long running initial steps when an activity needs to be restarted after a change. They are usually not used after the test development process, in a production test suite.
Zeile 113:		Zeile 113:
	For very long running tests (hours or days), it is recommended to use this attribute to ensure that the activity log fits the machine's memory size (to avoid running out of memory during the test run).		For very long running tests (hours or days), it is recommended to use this attribute to ensure that the activity log fits the machine's memory size (to avoid running out of memory during the test run).

	You can either unconditionally disable the activity log for a step or its subactivities or conditionally, based on its outcome, or if it part of a loop.		You can either unconditionally disable the activity log for a step or its subactivities or conditionally, based on its outcome, or if it is part of a loop.

	== Augmenting the Step's Name in the Log ==		== Augmenting the Step's Name in the Log ==