ElementaryBlock Element/en - Versionsgeschichte

Cg: /* Groovy Blocks */

2026-05-22T10:38:19Z

Groovy Blocks

← Nächstältere Version		Version vom 22. Mai 2026, 10:38 Uhr
Zeile 362:		Zeile 362:
	== Groovy Blocks ==		== Groovy Blocks ==

	A Groovy action is a bridge action and its code is executed in a Java Virtual Machine (JVM), either locally, on a remote system or inside the system under test (SUT). It is ~~possible~~ to ~~define~~ ~~new~~ ~~classes,~~ ~~new~~ ~~functions~~ ~~and~~ to ~~create~~ ~~objects~~ ~~which~~ ~~persist~~ ~~between Groovy~~ ~~calls~~. It is ~~also~~ ~~possible to define callbacks~~ and ~~other~~ ~~functions~~ ~~which~~ ~~lead~~ ~~back~~ ~~into~~ ~~expecco.~~ ~~Groovy~~ ~~actions are described in more detail in the [[ Expecco_API#Groovy_Elementary_Blocks \| Expecco API documentation on Groovy ]]~~ .		A Groovy action is a bridge action and its code is executed in a Java Virtual Machine (JVM), either locally, on a remote system or inside the system under test (SUT). Groovy's syntax is very Java-like, and wellknown within the Java community as a scripting language for the JVM. It is dynamically compiled and can access Java classes, instantiate Java objects and call functions.

			It is possible to define new classes, new functions and to create objects which persist between Groovy calls. It is also possible to define callbacks and other functions which lead back into expecco.

			Groovy actions are described in more detail in the [[ Expecco_API#Groovy_Elementary_Blocks \| Expecco API documentation on Groovy ]] .

	== C# Action Blocks ==		== C# Action Blocks ==

Cg: /* Specifying the Python Version in an Environment Variable */

2026-05-22T09:26:08Z

Specifying the Python Version in an Environment Variable

← Nächstältere Version		Version vom 22. Mai 2026, 09:26 Uhr
Zeile 824:		Zeile 824:

	The Settings or a corresponding variable then define the Python interpreter (in "''Settings''" -> "''Execution''" -> "''External Language Interpreters''"):		The Settings or a corresponding variable then define the Python interpreter (in "''Settings''" -> "''Execution''" -> "''External Language Interpreters''"):
	* "<code>Python Path</code>" in the settings or the "<code>PYTHON_SHELL</code>" shell environment variable,<br>are used when no explicit version is required, or if all of your scripts require the same Python version,		* "<code>Python Path</code>" in the settings or the "<code>PYTHON_SHELL</code>" shell environment variable,<br>are used when no explicit version is required, or if all of your scripts require the same Python version (which is the case in almost all situations),
	* "<code>Python2 Path</code>" in the settings (or the "<code>PYTHON2_SHELL</code>" shell variable)<br>are used for scripts which have been marked as explicitly requiring python2,		* "<code>Python2 Path</code>" in the settings (or the "<code>PYTHON2_SHELL</code>" shell variable)<br>are used for scripts which have been marked as explicitly requiring python2,
	* "<code>Python3 Path</code>" in the settings (or the "<code>PYTHON3_SHELL</code>" shell variable)<br>for scripts which are marked to require python3		* "<code>Python3 Path</code>" in the settings (or the "<code>PYTHON3_SHELL</code>" shell variable)<br>for scripts which are marked to require python3

Cg: /* Specifying the Python Version in an Environment Variable */

2026-05-22T09:24:43Z

Specifying the Python Version in an Environment Variable

← Nächstältere Version		Version vom 22. Mai 2026, 09:24 Uhr
Zeile 824:		Zeile 824:

	The Settings or a corresponding variable then define the Python interpreter (in "''Settings''" -> "''Execution''" -> "''External Language Interpreters''"):		The Settings or a corresponding variable then define the Python interpreter (in "''Settings''" -> "''Execution''" -> "''External Language Interpreters''"):
	* "Python Path" in the settings or the "<code>PYTHON_SHELL</code>" shell environment variable,<br>are used when no explicit version is required, or if all of your scripts require the same Python version,		* "<code>Python Path</code>" in the settings or the "<code>PYTHON_SHELL</code>" shell environment variable,<br>are used when no explicit version is required, or if all of your scripts require the same Python version,
	* "Python2 Path" in the settings (or the "<code>PYTHON2_SHELL</code>" shell variable)<br>are used for scripts which have been marked as explicitly requiring python2,		* "<code>Python2 Path</code>" in the settings (or the "<code>PYTHON2_SHELL</code>" shell variable)<br>are used for scripts which have been marked as explicitly requiring python2,
	* "Python3 Path" in the settings (or the "<code>PYTHON3_SHELL</code>" shell variable)<br>for scripts which are marked to require python3		* "<code>Python3 Path</code>" in the settings (or the "<code>PYTHON3_SHELL</code>" shell variable)<br>for scripts which are marked to require python3
	* "Jython Path" in the settings (or the "<code>JYTHON_SHELL</code>" shell variable)<br>for scripts which are marked to require jython.		* "<code>Jython Path</code>" in the settings (or the "<code>JYTHON_SHELL</code>" shell variable)<br>for scripts which are marked to require jython.
	* "IronPython Path" in the settings (or the "<code>IRONPYTHON_SHELL</code>" shell variable)<br>for scripts which are marked to require ironPython.		* "<code>IronPython Path</code>" in the settings (or the "<code>IRONPYTHON_SHELL</code>" shell variable)<br>for scripts which are marked to require ironPython.

	Using that double-indirect mechanism, it is still possible to:		Using that double-indirect mechanism, it is still possible to:

Cg: /* Specifying the Python Version in an Environment Variable */

2026-05-22T09:24:03Z

Specifying the Python Version in an Environment Variable

← Nächstältere Version		Version vom 22. Mai 2026, 09:24 Uhr
Zeile 821:		Zeile 821:

	The Python version requirements are defined in the environment of the suite or imported library in which the action is defined.		The Python version requirements are defined in the environment of the suite or imported library in which the action is defined.
	A variable named "PYTHON_VERSION" should be defined, which holdes either a digit "<code>2</code>" or "<code>3</code>" or the string "jython" or "ironPython". This value specifies the version to be used for ALL of the Python actions within that library. Notice, that the environment of the project from which the action was imported is relevant here - not the active environment at execution time, or the suite's top environment. This version number then determines, which of the settings is to be used (i.e. "PYTHON2_SHELL/path", "PYTHON3_SHELL/path", "JYTHON_SHELL/path" or "IRONPYTHON_SHELL/path").		A variable named "<code>PYTHON_VERSION</code>" should be defined, which holdes either a digit "<code>2</code>" or "<code>3</code>" or the string "<code>jython</code>" or "<code>ironPython</code>". This value specifies the version to be used for ALL of the Python actions within that library. Notice, that the environment of the project from which the action was imported is relevant here - not the active environment at execution time, or the suite's top environment. This version number then determines, which of the settings is to be used (i.e. "<code>PYTHON2_SHELL/path</code>", "<code>PYTHON3_SHELL/path</code>", "<code>JYTHON_SHELL/path</code>" or "<code>IRONPYTHON_SHELL/path</code>").

	The Settings or a corresponding variable then define the Python interpreter (in "''Settings''" -> "''Execution''" -> "''External Language Interpreters''"):		The Settings or a corresponding variable then define the Python interpreter (in "''Settings''" -> "''Execution''" -> "''External Language Interpreters''"):

Cg: /* Specifying the Python Version in the Script */

2026-05-22T09:22:39Z

Specifying the Python Version in the Script

← Nächstältere Version		Version vom 22. Mai 2026, 09:22 Uhr
Zeile 813:		Zeile 813:
	If the very first line of your script is (exactly as written, without any whitespace at the left or in between the hash and the identifier) one of:		If the very first line of your script is (exactly as written, without any whitespace at the left or in between the hash and the identifier) one of:
	#PYTHON2		#PYTHON2

	#PYTHON3		#PYTHON3

	#JYTHON		#JYTHON

	#IRONPYTHON		#IRONPYTHON
	then the script will ignore any environment values and executed with that Python version's setup values (see Python settings).		then the script will ignore any environment values and executed with that Python version's setup values (see Python settings).

Cg: /* Scheme Script Blocks */

2026-05-22T09:21:59Z

Scheme Script Blocks

← Nächstältere Version		Version vom 22. Mai 2026, 09:21 Uhr
Zeile 958:		Zeile 958:

	Similar to python scripts, the Scheme interpreter path can be either left unspecified,		Similar to python scripts, the Scheme interpreter path can be either left unspecified,
	or specified in the expecco settings ("''external tools''"), or via an expecco environment variable named "SCHEME_SHELL").		or specified in the expecco settings ("''external tools''"), or via an expecco environment variable named "<code>SCHEME_SHELL</code>").
	The environment variable can be in any environment which is visible in the scope of the Scheme action.		The environment variable can be in any environment which is visible in the scope of the Scheme action.
	If left unspecified, or without an absolute path, the Scheme interpreter should be found along the PATH by the name "scheme".		If left unspecified, or without an absolute path, the Scheme interpreter should be found along the PATH by the name "scheme".
Zeile 990:		Zeile 990:


	A variable named "SCHEME_DIALECT" ~~should~~ be defined, which holds one of the above dialect names"<code>RACKET</code>", "<code>CHEZ</code>" etc. This specification will be used.		A variable named "<code>SCHEME_DIALECT</code>" can be defined, which holds one of the above dialect names"<code>RACKET</code>", "<code>CHEZ</code>" etc. This specification will be used.

	The Settings or a corresponding variable then define the interpreter (in "''Settings''" -> "''Execution''" -> "''External Language Interpreters''"):		The Settings or a corresponding variable then define the interpreter (in "''Settings''" -> "''Execution''" -> "''External Language Interpreters''"):
Zeile 999:		Zeile 999:

	Using that double-indirect mechanism, it is still possible to:		Using that double-indirect mechanism, it is still possible to:
	* import multiple libraries with different ~~python~~-versions requirements		* import multiple libraries with different scheme-versions requirements
	* specify the paths independent of where the ~~Python~~ interpreters are installed (i.e. the machine on which the final suite is executed may have different installation paths than the machine on which the imported libraries were developed).		* specify the paths independent of where the Scheme interpreters are installed (i.e. the machine on which the final suite is executed may have different installation paths than the machine on which the imported libraries were developed).

	=== Any other Scripting Language via Shell Blocks ===		=== Any other Scripting Language via Shell Blocks ===

Cg: /* Standard Input / Standard Output Handling */

2026-02-26T13:59:38Z

Standard Input / Standard Output Handling

← Nächstältere Version		Version vom 26. Februar 2026, 13:59 Uhr
Zeile 475:		Zeile 475:
	These pins can be configured to either provide the whole output as one big string, or linewise either as individual lines or as chunks of multiple lines.		These pins can be configured to either provide the whole output as one big string, or linewise either as individual lines or as chunks of multiple lines.

	[[Datei:bulb.png\|16px]] Notice, that those pins are hidden by default, you have to add them via the action's context menu ("''Special Pins''").		[[Datei:bulb.png\|16px]] Notice, that those pins are hidden by default, you have to add them via the action's context menu ("''Special Pins''") in the schema page.

	===== Buffered vs. Unbuffered Stdout and Stderr =====		===== Buffered vs. Unbuffered Stdout and Stderr =====

Cg: /* Script Execution in General */

2026-02-26T13:58:16Z

Script Execution in General

← Nächstältere Version		Version vom 26. Februar 2026, 13:58 Uhr
Zeile 467:		Zeile 467:
	=== Script Execution in General ===		=== Script Execution in General ===

	The following sections describe the mechanism of script blocks in general, all of this is valid for Shell, Batch and all the other external scripting language action blocks (i.e. python, ruby, tcl, etc.). Be reminded that there is a fundamental difference between ''script actions'' and ''bridged actions'' as described above.		The following sections describe the mechanism of script blocks in general, all of this is valid for Shell, Batch and all the other external scripting language action blocks (i.e. python, ruby, tcl, etc.). Be reminded that there is a fundamental difference between ''script actions'' and [[#Bridged_Actions \| ''bridged actions'']] as described above.

	==== Standard Input / Standard Output Handling ====		==== Standard Input / Standard Output Handling ====

Cg: /* Smalltalk Blocks (Bridged) */

2025-05-10T19:14:25Z

Smalltalk Blocks (Bridged)

← Nächstältere Version		Version vom 10. Mai 2025, 19:14 Uhr
Zeile 449:		Zeile 449:

	The API is described in the [[Expecco_API#Bridged_Smalltalk_Elementary_Blocks\|"Expecco API documentation on Bridged Smalltalk Actions"]].		The API is described in the [[Expecco_API#Bridged_Smalltalk_Elementary_Blocks\|"Expecco API documentation on Bridged Smalltalk Actions"]].

			== Scheme Blocks (Bridged) ==

			Experimental and Unfinished
			Bridged Scheme actions are executed by a separate Scheme process, either on the local machine, or on a remote machine. As with the other bridge implementations, the code is dynamically transported to the target virtual machine and executed there.

			Currently, bridged Scheme execution is supported for GNU-Scheme and Racket/MZScheme.

			The API is described in the [[Expecco_API#Bridged_Scheme_Elementary_Blocks\|"Expecco API documentation on Bridged Scheme Actions"]].

	== Script Action Blocks ==		== Script Action Blocks ==

Cg: /* R Action Blocks */

2025-05-10T16:05:24Z

R Action Blocks

← Nächstältere Version		Version vom 10. Mai 2025, 16:05 Uhr
Zeile 872:		Zeile 872:
	Concrete examples are found in the library "<code>Plot_Graph_Library.ets</code>", which is found in the gnuplot plugin or the demos folder.		Concrete examples are found in the library "<code>Plot_Graph_Library.ets</code>", which is found in the gnuplot plugin or the demos folder.

	=== R ~~Action~~ Blocks ===		=== R Script Blocks ===

	With expecco rel18.1, another new action type was added for 'R' action blocks.		With expecco rel18.1, another new action type was added for 'R' action blocks.