Glossary/en - Versionsgeschichte

Cg: /* VisualWorks */

2026-06-06T08:45:19Z

VisualWorks

← Nächstältere Version		Version vom 6. Juni 2026, 08:45 Uhr
Zeile 367:		Zeile 367:

	== VisualWorks ==		== VisualWorks ==
	[https://en.wkipedia.org/wiki/VisualWorks VisualWorks] (or "''VW''" / "''VW-Smalltalk''") is the brand name of a Smalltalk programming language environment ("''dialect''") from ParcPlace Systems, now Cincom, a US based company. VisualWorks is an ANSI compatible [https://en.wkipedia.org/wiki/Smalltalk Smalltalk], is a direct descendent of the original Smalltalk80 system from Xerox Parc. It shares many APIs with Smalltalk/X, and VisualWorks documentation is mostly also valid for ST/X (differences are in the namespace notation and ST/X language extensions).<br>Starting with expecco 20.2, VisualWorks bridged blocks and VisualWorks GUI tests are supported by expecco via an extension plugin.		[https://en.wkipedia.org/wiki/VisualWorks VisualWorks] (or "''VW''" / "''VW-Smalltalk''") is the brand name of a Smalltalk programming language environment ("''dialect''") from ParcPlace Systems, now Cincom, a US based company. VisualWorks is an ANSI compatible [https://en.wkipedia.org/wiki/Smalltalk Smalltalk], and a direct descendent of the original Smalltalk80 system from Xerox Parc. It shares many APIs with Smalltalk/X, and VisualWorks documentation is mostly also valid for ST/X (differences are in the namespace notation and ST/X language extensions).<br>Starting with expecco 20.2, VisualWorks bridged blocks and VisualWorks GUI tests are supported by expecco via an extension plugin.

	== White Box Test ==		== White Box Test ==

Cg: /* VisualWorks */

2026-06-06T08:44:34Z

VisualWorks

← Nächstältere Version		Version vom 6. Juni 2026, 08:44 Uhr
Zeile 367:		Zeile 367:

	== VisualWorks ==		== VisualWorks ==
	~~VisualWorks~~ [https://en.wkipedia.org/wiki/VisualWorks] ("''VW''") is the brand name of a Smalltalk programming language environment ("''dialect''") from Cincom, a US based company. VisualWorks is an ANSI compatible [https://en.wkipedia.org/wiki/Smalltalk Smalltalk], ~~sharing~~ ~~many~~ of ~~its~~ APIs with Smalltalk/X, and VisualWorks documentation is mostly also valid for ST/X (differences are in the namespace notation and ST/X language extensions).<br>Starting with expecco 20.2, VisualWorks bridged blocks and VisualWorks GUI tests are supported by expecco via an extension plugin.		[https://en.wkipedia.org/wiki/VisualWorks VisualWorks] (or "''VW''" / "''VW-Smalltalk''") is the brand name of a Smalltalk programming language environment ("''dialect''") from ParcPlace Systems, now Cincom, a US based company. VisualWorks is an ANSI compatible [https://en.wkipedia.org/wiki/Smalltalk Smalltalk], is a direct descendent of the original Smalltalk80 system from Xerox Parc. It shares many APIs with Smalltalk/X, and VisualWorks documentation is mostly also valid for ST/X (differences are in the namespace notation and ST/X language extensions).<br>Starting with expecco 20.2, VisualWorks bridged blocks and VisualWorks GUI tests are supported by expecco via an extension plugin.

	== White Box Test ==		== White Box Test ==

Cg: /* VisualAge */

2026-06-06T08:37:40Z

VisualAge

← Nächstältere Version		Version vom 6. Juni 2026, 08:37 Uhr
Zeile 364:		Zeile 364:

	== VisualAge ==		== VisualAge ==
	[https://en.wkipedia.org/wiki/VisualAge VisualAge] ("''VA Smalltalk''") is the brand name of a [https://en.wkipedia.org/wiki/Smalltalk Smalltalk] language implementation and environment originally ~~develloped~~ by OTI, then taken over by IBM and now Instantiations.		[https://en.wkipedia.org/wiki/VisualAge VisualAge] ("''VA Smalltalk''") is the brand name of a [https://en.wkipedia.org/wiki/Smalltalk Smalltalk] language implementation ("''dialect''") and environment originally developed by OTI, then taken over by IBM (aka "''IBM Smalltalk''") and now Instantiations Inc.


	== VisualWorks ==		== VisualWorks ==
	VisualWorks [https://en.wkipedia.org/wiki/VisualWorks] ("''VW''") is the brand name of a Smalltalk programming language environment ("''dialect''") from Cincom, a US based company. VisualWorks is an ANSI compatible [https://en.wkipedia.org/wiki/Smalltalk Smalltalk], sharing many of its APIs with Smalltalk/X, and VisualWorks documentation is mostly also valid for ST/X (differences are in the namespace notation and ST/X language extensions).<br>Starting with expecco 20.2, VisualWorks bridged blocks and VisualWorks GUI tests are supported by expecco via an extension plugin.		VisualWorks [https://en.wkipedia.org/wiki/VisualWorks] ("''VW''") is the brand name of a Smalltalk programming language environment ("''dialect''") from Cincom, a US based company. VisualWorks is an ANSI compatible [https://en.wkipedia.org/wiki/Smalltalk Smalltalk], sharing many of its APIs with Smalltalk/X, and VisualWorks documentation is mostly also valid for ST/X (differences are in the namespace notation and ST/X language extensions).<br>Starting with expecco 20.2, VisualWorks bridged blocks and VisualWorks GUI tests are supported by expecco via an extension plugin.

Cg: /* VisualWorks */

2026-06-06T08:36:06Z

VisualWorks

← Nächstältere Version		Version vom 6. Juni 2026, 08:36 Uhr
Zeile 363:		Zeile 363:
	Every item within expecco (action, type, testcase, testplan, the suite itself etc.) has an associated unique identifier, which is guaranteed to be world-wide unique (a so called "''UUID''"). This guarantees, that these objects can be uniquely identified, even if renamed, or if the same name is used for an action, type etc. in two different test suites. Thus, two suites can always be merged and suites can always be imported without name conflicts.. expecco will internally always refer to any object by its ID, never by its name. The versionID is updated with every change made to an object. Thus it is guaranteed, that no two different objects have the same ID. And vice versa, that the equality (actually identity) can always be checked via the ID.		Every item within expecco (action, type, testcase, testplan, the suite itself etc.) has an associated unique identifier, which is guaranteed to be world-wide unique (a so called "''UUID''"). This guarantees, that these objects can be uniquely identified, even if renamed, or if the same name is used for an action, type etc. in two different test suites. Thus, two suites can always be merged and suites can always be imported without name conflicts.. expecco will internally always refer to any object by its ID, never by its name. The versionID is updated with every change made to an object. Thus it is guaranteed, that no two different objects have the same ID. And vice versa, that the equality (actually identity) can always be checked via the ID.

			== VisualAge ==
			[https://en.wkipedia.org/wiki/VisualAge VisualAge] ("''VA Smalltalk''") is the brand name of a [https://en.wkipedia.org/wiki/Smalltalk Smalltalk] language implementation and environment originally develloped by OTI, then taken over by IBM and now Instantiations.

	== VisualWorks ==		== VisualWorks ==
	VisualWorks ("''VW''") is the brand name of a Smalltalk programming language environment ("''dialect''") from Cincom, a US based company. VisualWorks is an ANSI compatible Smalltalk, sharing many of its APIs with Smalltalk/X, and VisualWorks documentation is mostly also valid for ST/X (differences are in the namespace notation and ST/X language extensions).<br>Starting with expecco 20.2, VisualWorks bridged blocks and VisualWorks GUI tests are supported by expecco via an extension plugin.		VisualWorks [https://en.wkipedia.org/wiki/VisualWorks] ("''VW''") is the brand name of a Smalltalk programming language environment ("''dialect''") from Cincom, a US based company. VisualWorks is an ANSI compatible [https://en.wkipedia.org/wiki/Smalltalk Smalltalk], sharing many of its APIs with Smalltalk/X, and VisualWorks documentation is mostly also valid for ST/X (differences are in the namespace notation and ST/X language extensions).<br>Starting with expecco 20.2, VisualWorks bridged blocks and VisualWorks GUI tests are supported by expecco via an extension plugin.

	== White Box Test ==		== White Box Test ==

Cg: /* VisualWorks */

2026-06-06T08:18:32Z

VisualWorks

← Nächstältere Version		Version vom 6. Juni 2026, 08:18 Uhr
Zeile 364:		Zeile 364:

	== VisualWorks ==		== VisualWorks ==
	VisualWorks ("''VW''") is the brand name of a Smalltalk programming language environment from Cincom, a US based company. Starting with expecco 20.2, VisualWorks bridged blocks and VisualWorks GUI tests are supported by expecco.		VisualWorks ("''VW''") is the brand name of a Smalltalk programming language environment ("''dialect''") from Cincom, a US based company. VisualWorks is an ANSI compatible Smalltalk, sharing many of its APIs with Smalltalk/X, and VisualWorks documentation is mostly also valid for ST/X (differences are in the namespace notation and ST/X language extensions).<br>Starting with expecco 20.2, VisualWorks bridged blocks and VisualWorks GUI tests are supported by expecco via an extension plugin.

	== White Box Test ==		== White Box Test ==

Cg: /* Node Elementary Action Block */

2026-06-06T08:11:50Z

Node Elementary Action Block

← Nächstältere Version		Version vom 6. Juni 2026, 08:11 Uhr
Zeile 180:		Zeile 180:

	== Node Elementary Action Block ==		== Node Elementary Action Block ==
	Node.js (or "''NodeJS''" or simply "''Node''") is a language interpreter for JavaScript, which is used in cloud computing, Alexa, IOT and other internet applications. Node is rapidly gaining interest and many packages are already available, covering a wide range of protocols, file formats and interfaces. Both bridged and scripted Node.js actions are supported, and expecco includes good support for bridged Node.js action blocks, including breakpoints ~~and~~ debugging with single stepping.		Node.js (or "''NodeJS''" or simply "''Node''") is a language interpreter for JavaScript, which is used in cloud computing, Alexa, IOT and other internet applications. Node is rapidly gaining interest and many packages are already available, covering a wide range of protocols, file formats and interfaces. Both bridged and scripted Node.js actions are supported, and expecco includes good support for bridged Node.js action blocks, including breakpoints, debugging with single stepping and object inspectors.
	<br>You have to install "node" and "npm" from the official website: [https://nodejs.org/en/download/ https://nodejs.org/en/download].		<br>You have to install "node" and "npm" from the official website: [https://nodejs.org/en/download/ https://nodejs.org/en/download].
	<br>See [[Expecco API/en#Node.js_.28Bridged.29_Elementary_Blocks\|"NodeJS Elementary Blocks"]] in the Expecco API document and [[ElementaryBlock Element/en\|Elementary Block]] in the [[Tree Elements]] documentation.		<br>See [[Expecco API/en#Node.js_.28Bridged.29_Elementary_Blocks\|"NodeJS Elementary Blocks"]] in the Expecco API document and [[ElementaryBlock Element/en\|Elementary Block]] in the [[Tree Elements]] documentation.

Cg: /* Script Actions */

2026-06-06T08:10:11Z

Script Actions

← Nächstältere Version		Version vom 6. Juni 2026, 08:10 Uhr
Zeile 240:		Zeile 240:
	In contrast to "''bridged actions''", these are called as host-commands, where a new interpreter is		In contrast to "''bridged actions''", these are called as host-commands, where a new interpreter is
	started for every action invokation. This has the advantage, that any existing script can be		started for every action invokation. This has the advantage, that any existing script can be
	easily used/embedded into a testsuite, but the disadvantage that the action's execution is somewhat slowed down due to the startup/shutdown times of the external interpreter, and that no state (open files, connections, objects etc.) can be passed from one action to another.		easily used/embedded into a testsuite, but the disadvantage that the action's execution is somewhat slowed down due to the startup/shutdown times of the external interpreter, and that no state (open files, connections, objects etc.) can be passed from one action to another. Any input/output must be either through files or encoded/decoded and passed via stdin/stdout.

	== SFTP (Secure File Transfer) ==		== SFTP (Secure File Transfer) ==

Cg: /* Stdout */

2026-06-06T08:06:18Z

Stdout

← Nächstältere Version		Version vom 6. Juni 2026, 08:06 Uhr
Zeile 286:		Zeile 286:

	== Stdout ==		== Stdout ==
	Short for "Standard Output". This is any program's standard output stream. If running in a console window, this is typically displayed there. If running without a console window it may be lost or redirected into a logfile.		Short for "Standard Output". This is any program's standard output stream. Every well behaving program will send error messages to stderr and regular output to stdout, making it possible to divert these to different destinations. If running in a console window, this is typically displayed there. If running without a console window it may be lost or redirected into a logfile.
	If expecco starts other programs, you have the option of redirecting their stdout to the expecco Transcript (which is the expecco console). There, this will be prefixed by "1:" and colorized in blue (to indicate that this is text from stdout, as opposed to stderr). The setting is found in "''Extras''" → "''Settings''" → "''Execution''" → "''Tracing''" → "''Show Stdout/Stderr in Transcript''".		If expecco starts other programs, you have the option of redirecting their stdout to the expecco Transcript (which is the expecco console). There, this will be prefixed by "1:" and colorized in blue (to indicate that this is text from stdout, as opposed to stderr). The setting is found in "''Extras''" → "''Settings''" → "''Execution''" → "''Tracing''" → "''Show Stdout/Stderr in Transcript''".

Cg: /* Stderr */

2026-06-06T08:05:48Z

Stderr

← Nächstältere Version		Version vom 6. Juni 2026, 08:05 Uhr
Zeile 278:		Zeile 278:

	== Stderr ==		== Stderr ==
	Short for "Standard Error". This is any program's standard error output stream. If running in a console window, this is typically displayed there. If running without a console window it may be lost or redirected into a logfile.		Short for "Standard Error". This is any program's standard error output stream. Every well behaving program will send error messages to stderr and regular output to stdout, making it possible to divert these to different destinations. If running in a console window, this is typically displayed there. If running without a console window it may be lost or redirected into a logfile.
	If expecco starts other programs, you have the option of redirecting their stderr to the expecco Transcript (which is the expecco console). There, this will be prefixed by "2:" and colorized in red (to indicate that this is text from stderr, as opposed to stdout). The setting is found in "''Extras''" → "''Settings''" → "''Execution''" → "''Tracing''" → "''Show Stdout/Stderr in Transcript''".		If expecco starts other programs, you have the option of redirecting their stderr to the expecco Transcript (which is the expecco console). There, this will be prefixed by "2:" and colorized in red (to indicate that this is text from stderr, as opposed to stdout). The setting is found in "''Extras''" → "''Settings''" → "''Execution''" → "''Tracing''" → "''Show Stdout/Stderr in Transcript''".

Cg: /* Tag */

2026-06-06T08:01:36Z

Tag

← Nächstältere Version		Version vom 6. Juni 2026, 08:01 Uhr
Zeile 306:		Zeile 306:

	== Tag ==		== Tag ==
	A token (word) attached to an element. Multiple tags can be attached and are used to search, group or otherwise mark tree items, steps and other elements of the test suite. For example, you can define an icon to be shown in the left project tree if the item has a particular tag.		A token (word) attached to an element. Multiple tags can be attached and are used to search, group or otherwise mark tree items, steps and other elements of the test suite.<br>In addition to support searching and grouping, additional other behavior can be controlled by tags.<br>For example, you can define an icon or color to be shown in the left project tree if the item has a particular tag.<br>You can also use tags to control the execution, for filtering log entries or to control the generation of logs.

	== Tagged Value ==		== Tagged Value ==