TableDrivenBlock Element/en - Versionsgeschichte

Cg: /* Introduction */

2026-02-26T20:17:08Z

Introduction

← Nächstältere Version		Version vom 26. Februar 2026, 20:17 Uhr
Zeile 1:		Zeile 1:
	== Introduction ==		== Introduction ==
	The table-driven action block (also sometimes called "''keyword action''") describes an action's behavior as a sequential flow of actions. Typically they are used for test steps, therefore you will occasionally find the name "table-driven test" in this documentation.		The table-driven action block (also sometimes called "''keyword action''") describes an action's behavior as a sequential flow of actions. Typically they are used for test steps, therefore you will occasionally find the name "''table-driven test''" in this documentation.

	Each step is represented by one or more rows in the table, where the first row of each step is highlighted by the background color. Further rows represent the in- and output pins of each step.		Each step is represented by one or more rows in the table, where the first row of each step is highlighted by the background color. Further rows represent the in- and output pins of each step.
	<br>		<br>
	If an action turns out to need more complexity (i.e. decisions, loops or ~~parallelity~~) the table driven block can be transformed into a general [[Compound_Block\|compound block]] via a popup menu function in the tree ("Refactoring" -> "Convert to Compound Action"). This will generate a regular compound action, with the individual steps as a sequence, to be changed as required.		If an action turns out to need more complexity (i.e. decisions, loops or parallelism) the table driven block can be transformed into a general [[Compound_Block\|compound block]] via a popup menu function in the tree ("Refactoring" → "Convert to Compound Action"). This will generate a regular compound action, with the individual steps as a sequence, to be changed as required.

	==Introductory Table Driven Block Example==		==Introductory Table Driven Block Example==

Mawalch: Spelling fixes.

2017-05-11T07:07:23Z

Spelling fixes.

← Nächstältere Version		Version vom 11. Mai 2017, 07:07 Uhr
Zeile 4:		Zeile 4:
	Each step is represented by one or more rows in the table, where the first row of each step is highlighted by the background color. Further rows represent the in- and output pins of each step.		Each step is represented by one or more rows in the table, where the first row of each step is highlighted by the background color. Further rows represent the in- and output pins of each step.
	<br>		<br>
	If an action turns out to need more complexity (i.e. decisions, loops or parallelity) the table driven block can be transformed into a general [[Compound_Block\|compound block]] via a popup menu function in the tree ("Refactoring" -> "Convert to Compound Action"). This will generate a regular ~~combound~~ action, with the individual steps as a sequence, to be changed as required.		If an action turns out to need more complexity (i.e. decisions, loops or parallelity) the table driven block can be transformed into a general [[Compound_Block\|compound block]] via a popup menu function in the tree ("Refactoring" -> "Convert to Compound Action"). This will generate a regular compound action, with the individual steps as a sequence, to be changed as required.

	==Introductory Table Driven Block Example==		==Introductory Table Driven Block Example==
Zeile 34:		Zeile 34:

	==== Write Value to Environment Variable(7) ====		==== Write Value to Environment Variable(7) ====
	The data ~~avalable~~ at a output pin can be saved to a environment variable. In the example the value available at outInt is saved to 'environmentVariable2'.		The data available at a output pin can be saved to a environment variable. In the example the value available at outInt is saved to 'environmentVariable2'.

	==== Write Value to Pin (8) ====		==== Write Value to Pin (8) ====
	~~Alternativly~~ the data available at a output pin can be saved to the schemas pin. In the example the value available at outBool is saved to 'outBool'.		Alternatively the data available at a output pin can be saved to the schemas pin. In the example the value available at outBool is saved to 'outBool'.

	== Editors ==		== Editors ==

Cg: /* Introductory Table Driven Block Example */

2016-12-07T18:18:19Z

Introductory Table Driven Block Example

← Nächstältere Version		Version vom 7. Dezember 2016, 18:18 Uhr
Zeile 13:		Zeile 13:

	=== Step Nr (1) ===		=== Step Nr (1) ===
	The unique step number can be used to ~~identidy~~ a explicit step in a table.		The unique step number can be used to identify an explicit step in a table.

	=== Step Name (2) ===		=== Step Name (2) ===

Cg: /* Introduction */

2016-12-07T18:17:32Z

Introduction

← Nächstältere Version		Version vom 7. Dezember 2016, 18:17 Uhr
Zeile 4:		Zeile 4:
	Each step is represented by one or more rows in the table, where the first row of each step is highlighted by the background color. Further rows represent the in- and output pins of each step.		Each step is represented by one or more rows in the table, where the first row of each step is highlighted by the background color. Further rows represent the in- and output pins of each step.
	<br>		<br>
	If an action turns out to need more complexity (i.e. decisions, loops or parallelity) the table driven block can be transformed into a [[Compound_Block\|compound block]] via a popup menu function in the tree ("Refactoring" -> "Convert to Compound Action").		If an action turns out to need more complexity (i.e. decisions, loops or parallelity) the table driven block can be transformed into a general [[Compound_Block\|compound block]] via a popup menu function in the tree ("Refactoring" -> "Convert to Compound Action"). This will generate a regular combound action, with the individual steps as a sequence, to be changed as required.

	==Introductory Table Driven Block Example==		==Introductory Table Driven Block Example==

Cg: /* Introduction */

2016-12-07T18:16:25Z

Introduction

← Nächstältere Version		Version vom 7. Dezember 2016, 18:16 Uhr
Zeile 1:		Zeile 1:
	== Introduction ==		== Introduction ==
	The table-driven action block (also sometimes called "''keyword action''") describes an action's behavior as sequential ~~test~~ flow.		The table-driven action block (also sometimes called "''keyword action''") describes an action's behavior as a sequential flow of actions. Typically they are used for test steps, therefore you will occasionally find the name "table-driven test" in this documentation.

	Each ~~test~~ step is represented by one or more rows in the table, where the first row of each step is ~~highlited~~ by the background color. Further rows represent the in- and output pins of each step.		Each step is represented by one or more rows in the table, where the first row of each step is highlighted by the background color. Further rows represent the in- and output pins of each step.
	<br>		<br>
	If a action turns out to be or ~~develops~~ ~~more~~ ~~complex~~ the table driven block can be transformed into a [[Compound_Block\|compound block]].		If an action turns out to need more complexity (i.e. decisions, loops or parallelity) the table driven block can be transformed into a [[Compound_Block\|compound block]] via a popup menu function in the tree ("Refactoring" -> "Convert to Compound Action").

	==Introductory Table Driven Block Example==		==Introductory Table Driven Block Example==

Cg: /* Introduction */

2016-12-07T18:13:48Z

Introduction

← Nächstältere Version		Version vom 7. Dezember 2016, 18:13 Uhr
Zeile 1:		Zeile 1:
	== Introduction ==		== Introduction ==
	The table driven block describes an action's behavior as sequential test flow.		The table-driven action block (also sometimes called "''keyword action''") describes an action's behavior as sequential test flow.
	Each test step is represented by one or more rows in the table, where the first row of each step is highlited by the background color. Further rows represent the in- and output pins of each step.		Each test step is represented by one or more rows in the table, where the first row of each step is highlited by the background color. Further rows represent the in- and output pins of each step.
	<br>		<br>

Sv am 18. Dezember 2015 um 10:09 Uhr

2015-12-18T10:09:49Z

← Nächstältere Version		Version vom 18. Dezember 2015, 10:09 Uhr
Zeile 42:		Zeile 42:
	is edited in the [[TableDrivenBlock_Editor-Table_Editor/en\|table editor]]. This is the "internal view" of the block.		is edited in the [[TableDrivenBlock_Editor-Table_Editor/en\|table editor]]. This is the "internal view" of the block.
	The interface of an compound block (e.g. number and type of output pins) can be regarded as its "external view" and can be inspected in the [[Scheme Editor/en\|schema editor]].		The interface of an compound block (e.g. number and type of output pins) can be regarded as its "external view" and can be inspected in the [[Scheme Editor/en\|schema editor]].

			== Backward Compatibility ==
			Table-Driven block elements have been introduced with expecco 2.8. If you load a testsuite with table-driven blocks with a previous expecco version, these blocks will be shown as compound blocks. When saving the testsuite with the previous version, table-driven blocks will be saved as compound blocks.

	[[Category: Tree Elements]]		[[Category: Tree Elements]]

Caellwein am 19. März 2015 um 13:49 Uhr

2015-03-19T13:49:47Z

← Nächstältere Version		Version vom 19. März 2015, 13:49 Uhr
Zeile 3:		Zeile 3:
	Each test step is represented by one or more rows in the table, where the first row of each step is highlited by the background color. Further rows represent the in- and output pins of each step.		Each test step is represented by one or more rows in the table, where the first row of each step is highlited by the background color. Further rows represent the in- and output pins of each step.
	<br>		<br>
	If a action turns out to be or develops more complex the table driven block can be transformed into a [[Compound_Block\|~~compount~~ block]].		If a action turns out to be or develops more complex the table driven block can be transformed into a [[Compound_Block\|compound block]].

	==Introductory Table Driven Block Example==		==Introductory Table Driven Block Example==

Caellwein: /* Write Value to Pin (8) */

2015-03-17T15:07:10Z

Write Value to Pin (8)

← Nächstältere Version		Version vom 17. März 2015, 15:07 Uhr
Zeile 36:		Zeile 36:

	==== Write Value to Pin (8) ====		==== Write Value to Pin (8) ====
			Alternativly the data available at a output pin can be saved to the schemas pin. In the example the value available at outBool is saved to 'outBool'.

	== Editors ==		== Editors ==

Caellwein: /* Write Value to Environment Variable(7) */

2015-03-17T15:06:15Z

Write Value to Environment Variable(7)

← Nächstältere Version		Version vom 17. März 2015, 15:06 Uhr
Zeile 32:		Zeile 32:
	The value at output pins can be compared. In the example the value of outString is checked for equality to the frozen value 'hello world'.		The value at output pins can be compared. In the example the value of outString is checked for equality to the frozen value 'hello world'.

	==== Write Value to Environment Variable(7) ====		==== Write Value to Environment Variable(7) ====
			The data avalable at a output pin can be saved to a environment variable. In the example the value available at outInt is saved to 'environmentVariable2'.

	==== Write Value to Pin (8) ====		==== Write Value to Pin (8) ====