TableDrivenBlock Editor-Table Editor/en - Versionsgeschichte

Cg: /* Toolbar */

2022-03-14T20:47:24Z

Toolbar

← Nächstältere Version		Version vom 14. März 2022, 20:47 Uhr
Zeile 22:		Zeile 22:

	*[[Bild:Icon_Collapse.png]] Collapse all step items		*[[Bild:Icon_Collapse.png]] Collapse all step items
	:All In- and ~~Output~~ pins of a step will be hidden. This allows to find a specific step item faster and get a general impression of the table.		:All in- and output pins of a step will be hidden. This allows to find a specific step item faster and get a general impression of the table.

	*[[Bild:Icon_Expand.png]] Expand all step items		*[[Bild:Icon_Expand.png]] Expand all step items
	:All In- and ~~Output~~ pins of a step will be visible. This allows to inspect the interaction between steps and to retrace a run.		:All in- and output pins of a step will be visible. This allows to inspect the interaction between steps and to retrace a run.

	== Tasks ==		== Tasks ==

Cg: /* Toolbar */

2022-03-14T20:46:54Z

Toolbar

← Nächstältere Version		Version vom 14. März 2022, 20:46 Uhr
Zeile 15:		Zeile 15:
	In the left function group of the toolbar you will find the buttons concerning the test execution, in the right area of the toolbar you will find the following functions concerning the presentation.		In the left function group of the toolbar you will find the buttons concerning the test execution, in the right area of the toolbar you will find the following functions concerning the presentation.
	<br><br>		<br><br>
	*[[Bild:Icon Run.png]] Start a test run or continue after a breakpoint or execution pause. This allows for a changed table's functionality to be checked immediately, without a need to create an extra compound block or a testplan-item for it to be executed. If the edited block needs input values or other prerequisite setup for the test run, these should be defined in the tab named "Test/Demo" (which is the rightmost tab of the editor).		*[[Bild:Icon Run.png]] Start a test run or continue after a breakpoint or execution pause.
			:This allows for a changed table's functionality to be checked immediately, without a need to create an extra compound block or a testplan-item for it to be executed. If the edited block needs input values or other prerequisite setup for the test run, these should be defined in the tab named "Test/Demo" (which is the rightmost tab of the editor).

			*[[Bild:Icon_RunWithDebugMode.png]] Start a test run with debug
	*[[Bild:~~Icon_RunWithDebugMode.png]]~~ Start ~~a test~~ run but open a debugger window in case of test failure, even if the debugger is currently disabled in the settings. This kind of run is helpful during test development or error analysis. It enables debugging mode without changing the settings.		:Start run but open a debugger window in case of test failure, even if the debugger is currently disabled in the settings. This kind of run is helpful during test development or error analysis. It enables debugging mode without changing the settings.

	*[[Bild:Icon_Collapse.png]] Collapse all step items~~; all In- and Output pins of a step will be hidden. This allows to find a specific step item faster and get a general impression of the table.~~		*[[Bild:Icon_Collapse.png]] Collapse all step items
			:All In- and Output pins of a step will be hidden. This allows to find a specific step item faster and get a general impression of the table.

	*[[Bild:Icon_Expand.png]] Expand all step items~~; all In- and Output pins of a step will be visible. This allows to inspect the interaction between steps and to retrace a run.~~		*[[Bild:Icon_Expand.png]] Expand all step items
			:All In- and Output pins of a step will be visible. This allows to inspect the interaction between steps and to retrace a run.

	== Tasks ==		== Tasks ==

Cg: /* Toolbar */

2022-03-14T20:45:38Z

Toolbar

← Nächstältere Version		Version vom 14. März 2022, 20:45 Uhr
Zeile 16:		Zeile 16:
	<br><br>		<br><br>
	*[[Bild:Icon Run.png]] Start a test run or continue after a breakpoint or execution pause. This allows for a changed table's functionality to be checked immediately, without a need to create an extra compound block or a testplan-item for it to be executed. If the edited block needs input values or other prerequisite setup for the test run, these should be defined in the tab named "Test/Demo" (which is the rightmost tab of the editor).		*[[Bild:Icon Run.png]] Start a test run or continue after a breakpoint or execution pause. This allows for a changed table's functionality to be checked immediately, without a need to create an extra compound block or a testplan-item for it to be executed. If the edited block needs input values or other prerequisite setup for the test run, these should be defined in the tab named "Test/Demo" (which is the rightmost tab of the editor).

	<br>
	*[[Bild:Icon_RunWithDebugMode.png]] Start a test run but open a debugger window in case of test failure, even if the debugger is currently disabled in the settings. This kind of run is helpful during test development or error analysis. It enables debugging mode without changing the settings.		*[[Bild:Icon_RunWithDebugMode.png]] Start a test run but open a debugger window in case of test failure, even if the debugger is currently disabled in the settings. This kind of run is helpful during test development or error analysis. It enables debugging mode without changing the settings.

	<br>
	*[[Bild:Icon_Collapse.png]] Collapse all step items; all In- and Output pins of a step will be hidden. This allows to find a specific step item faster and get a general impression of the table.		*[[Bild:Icon_Collapse.png]] Collapse all step items; all In- and Output pins of a step will be hidden. This allows to find a specific step item faster and get a general impression of the table.

	<br>
	*[[Bild:Icon_Expand.png]] Expand all step items; all In- and Output pins of a step will be visible. This allows to inspect the interaction between steps and to retrace a run.		*[[Bild:Icon_Expand.png]] Expand all step items; all In- and Output pins of a step will be visible. This allows to inspect the interaction between steps and to retrace a run.

Cg: /* Indicators */

2019-03-04T17:27:26Z

Indicators

← Nächstältere Version		Version vom 4. März 2019, 17:27 Uhr
Zeile 78:		Zeile 78:
	*[[Bild:BreakWithSuccessLineIndicator.png]] The step has a break with success set at an output pin. When the output pin is triggered, the execution of the table is aborted with success as return value.		*[[Bild:BreakWithSuccessLineIndicator.png]] The step has a break with success set at an output pin. When the output pin is triggered, the execution of the table is aborted with success as return value.

	*[[Bild:BreakPointed.png]] The step has a breakpoint set. When reached during a test run, the executor will pause and wait for either the "Run/Continue" or the "Single-Step" button to be pressed.		*[[Bild:BreakPointed.png]] The step has a breakpoint set. When reached during a test run, the executor will pause and wait for either the "''Run/Continue''" or the "''Single-Step''" button to be pressed.
	<br>		<br>

Cg: /* Save Pin Value */

2019-03-04T17:27:00Z

Save Pin Value

← Nächstältere Version		Version vom 4. März 2019, 17:27 Uhr
Zeile 72:		Zeile 72:
	*[[Bild:WriteToEnvironment.png]] '''Write to Environment Variable'''<br> Write the value to a variable.		*[[Bild:WriteToEnvironment.png]] '''Write to Environment Variable'''<br> Write the value to a variable.

	*[[Bild:WriteToOutput.png]] '''Write to Output'''<br> Write the value to the table driven block's output pin. The value can be ~~accessed~~ in the sequence the block is executed in, but not ~~be accessed~~ in the table driven block itself.		*[[Bild:WriteToOutput.png]] '''Write to Output'''<br> Write the value to the table driven block's output pin. The value can be used in the sequence/diagram in which the block is executed, but not in the table driven block itself.
	<br>		<br>

Cg: /* Save Pin Value */

2019-03-04T17:26:26Z

Save Pin Value

← Nächstältere Version		Version vom 4. März 2019, 17:26 Uhr
Zeile 70:		Zeile 70:
	The following operations can be used to make the value, available at this pin, accessible:		The following operations can be used to make the value, available at this pin, accessible:

	*[[Bild:WriteToEnvironment.png]] '''Write to Environment Variable'''<br> Write the value to a ~~environment~~ variable ~~to further use~~.		*[[Bild:WriteToEnvironment.png]] '''Write to Environment Variable'''<br> Write the value to a variable.

	*[[Bild:WriteToOutput.png]] '''Write to Output'''<br> Write the value to the table driven ~~blocks~~ output pin. The value can be accessed in the ~~sequenze~~ the block is executed in, but not be accessed in the table driven block itself.		*[[Bild:WriteToOutput.png]] '''Write to Output'''<br> Write the value to the table driven block's output pin. The value can be accessed in the sequence the block is executed in, but not be accessed in the table driven block itself.
	<br>		<br>

Cg: /* Compare Pin Value */

2019-03-04T17:25:38Z

Compare Pin Value

← Nächstältere Version		Version vom 4. März 2019, 17:25 Uhr
Zeile 56:		Zeile 56:
	The following operations can be used to ensure a specific value at a pin:		The following operations can be used to ensure a specific value at a pin:

	*[[Bild:ValueMustBeEqualTo.png]] '''value must be equal to'''<br> The value at this pin must be equal to the value accessed as identified. Otherwise ~~the test of~~ the table driven block will ~~fail~~.		*[[Bild:ValueMustBeEqualTo.png]] '''value must be equal to'''<br> The value at this pin must be equal to the value accessed as identified. Otherwise the table driven block will report a failure.

	*[[Bild:ValueMayNOTBeEqualTo.png]] '''value may NOT be equal to'''<br> The value at this pin may not be equal to the value accessed as identified. Otherwise ~~the test of~~ the table driven block will ~~fail~~.		*[[Bild:ValueMayNOTBeEqualTo.png]] '''value may NOT be equal to'''<br> The value at this pin may not be equal to the value accessed as identified. Otherwise the table driven block will report a failure.

	*[[Bild:BreakWithSuccessIndicator.png]] '''Break with success'''<br> If this pin is triggered the execution of the table driven block will stop with success.		*[[Bild:BreakWithSuccessIndicator.png]] '''Break with success'''<br> If this pin is triggered the execution of the table driven block will stop with success.

Cg: /* Compare Pin Value */

2019-03-04T17:24:51Z

Compare Pin Value

← Nächstältere Version		Version vom 4. März 2019, 17:24 Uhr
Zeile 60:		Zeile 60:
	*[[Bild:ValueMayNOTBeEqualTo.png]] '''value may NOT be equal to'''<br> The value at this pin may not be equal to the value accessed as identified. Otherwise the test of the table driven block will fail.		*[[Bild:ValueMayNOTBeEqualTo.png]] '''value may NOT be equal to'''<br> The value at this pin may not be equal to the value accessed as identified. Otherwise the test of the table driven block will fail.

	*[[Bild:BreakWithSuccessIndicator.png]] '''Break with success'''<br> If this pin is triggered the execution of the table driven block will ~~break~~ with success.		*[[Bild:BreakWithSuccessIndicator.png]] '''Break with success'''<br> If this pin is triggered the execution of the table driven block will stop with success.

	*[[Bild:BreakWithFailureIndicator.png]] '''Failed'''<br> If this pin is triggered the execution of the table driven block will ~~break~~ with a failure.		*[[Bild:BreakWithFailureIndicator.png]] '''Failed'''<br> If this pin is triggered the execution of the table driven block will stop with a failure.

	*[[Bild:Inconclusive.png]] '''Inconclusive'''<br> If this pin is triggered the execution of the table driven block will stop and the execution status will be inconclusive.		*[[Bild:Inconclusive.png]] '''Inconclusive'''<br> If this pin is triggered the execution of the table driven block will stop and the execution status will be inconclusive.

Cg am 13. Februar 2019 um 21:57 Uhr

2019-02-13T21:57:48Z

← Nächstältere Version		Version vom 13. Februar 2019, 21:57 Uhr
Zeile 166:		Zeile 166:
	== Settings ==		== Settings ==
	Visible aspects and behavior of a table driven block can be affected via the [[Settings TableDrivenBlock/en\|Settings Dialog]].		Visible aspects and behavior of a table driven block can be affected via the [[Settings TableDrivenBlock/en\|Settings Dialog]].

			[[Category: Editors ]]

Cg: /* Selecting Steps */

2019-02-13T21:57:12Z

Selecting Steps

← Nächstältere Version		Version vom 13. Februar 2019, 21:57 Uhr
Zeile 35:		Zeile 35:

	=== Selecting Steps ===		=== Selecting Steps ===
	A step can be selected by left-clicking it. Additional steps are selected by holding down the Shift-key in conjunction to the left mouse button. In a similar way, press the Control-key (CTRL or STRG) and click to toggle steps into or out of the selection.		A step can be selected by left-clicking it. Additional steps are selected by holding down the Shift-key in conjunction to the left mouse button. In a similar way, press the Control-key (<kbd>CTRL</kbd> or <kbd>STRG</kbd>) and click to toggle steps into or out of the selection.

	Another possibility to select multiple steps at a time is to mark a selection rectangle area with the mouse, which selects all steps (and other elements) that are within that area.		Another possibility to select multiple steps at a time is to mark a selection rectangle area with the mouse, which selects all steps (and other elements) that are within that area.