Glossary/en - Versionsgeschichte

Cg: /* Gray Box Test */

2026-05-14T10:52:09Z

Gray Box Test

← Nächstältere Version		Version vom 14. Mai 2026, 10:52 Uhr
Zeile 131:		Zeile 131:
	== Gray Box Test ==		== Gray Box Test ==
	Some knowledge about internal interfaces of the System Under Test are known. For example, data structures or function entries inside the SUT are exploited and used. The categorization of a test as white- or gray box test is vague - there is often no clear line of separation between them.		Some knowledge about internal interfaces of the System Under Test are known. For example, data structures or function entries inside the SUT are exploited and used. The categorization of a test as white- or gray box test is vague - there is often no clear line of separation between them.
	<br>See also [[#Black Box Test\|Black Box Test]], [[#White Box Test\|White Box Test]], [https://en.wikipedia.org/wiki/Gray_box_testing "~~Grey~~ Box Testing"] in Wikipedia.		<br>See also [[#Black Box Test\|Black Box Test]], [[#White Box Test\|White Box Test]], [https://en.wikipedia.org/wiki/Gray_box_testing "Gray Box Testing"] in Wikipedia.

	== Groovy ==		== Groovy ==

Cg: /* Black Box Test */

2026-05-14T10:51:46Z

Black Box Test

← Nächstältere Version		Version vom 14. Mai 2026, 10:51 Uhr
Zeile 37:		Zeile 37:
	Expecco supports both, "Black Box" by various libraries which provide interfaces to commonly used external interfaces, and "White Box" via code injection mechanisms, such as "Groovy", "Python" or "VisualBasic".		Expecco supports both, "Black Box" by various libraries which provide interfaces to commonly used external interfaces, and "White Box" via code injection mechanisms, such as "Groovy", "Python" or "VisualBasic".

	Mixed mode testing is called [https://en.wikipedia.org/wiki/Gray_box_testing "~~Grey~~ Box Testing" (wikipedia)].		Mixed mode testing is called [https://en.wikipedia.org/wiki/Gray_box_testing "Gray Box Testing" (wikipedia)].
	<br>See also: [[#White Box Test\|White Box Test]], [[#Gray Box Test\|Gray Box Test]]		<br>See also: [[#White Box Test\|White Box Test]], [[#Gray Box Test\|Gray Box Test]]

Cg: /* Black Box Test */

2026-05-14T10:51:15Z

Black Box Test

← Nächstältere Version		Version vom 14. Mai 2026, 10:51 Uhr
Zeile 35:		Zeile 35:
	The opposite being a [[#White Box Test\|"White Box Test"]], which executes inside the SUT and has full access to all internal details (i.e. functions, data objects etc.).		The opposite being a [[#White Box Test\|"White Box Test"]], which executes inside the SUT and has full access to all internal details (i.e. functions, data objects etc.).

	Expecco supports both, "Black Box" by various libraries which provide interfaces to commonly used external interfaces, and "White Box" via code injection mechanisms, such as "Groovy" or "VisualBasic".		Expecco supports both, "Black Box" by various libraries which provide interfaces to commonly used external interfaces, and "White Box" via code injection mechanisms, such as "Groovy", "Python" or "VisualBasic".

	Mixed mode testing is called [https://en.wikipedia.org/wiki/Gray_box_testing "Grey Box Testing" (wikipedia)].		Mixed mode testing is called [https://en.wikipedia.org/wiki/Gray_box_testing "Grey Box Testing" (wikipedia)].

Cg: /* SSDP(Simple Service Discovery Protocol) */

2026-05-14T10:47:43Z

SSDP(Simple Service Discovery Protocol)

← Nächstältere Version		Version vom 14. Mai 2026, 10:47 Uhr
Zeile 256:		Zeile 256:
	SOAP is a remote procedure call mechanism based on XML encoded packages which are typically (but not required to be) transmitted via HTTP. The name is a euphemism: SOAP is not (no longer) simple: to be used with ease, a huge XML framework lies underneath, which extracts details for a call from a specification written in WSDL (which is also XML with a complex structure, incl. datatype definitions).		SOAP is a remote procedure call mechanism based on XML encoded packages which are typically (but not required to be) transmitted via HTTP. The name is a euphemism: SOAP is not (no longer) simple: to be used with ease, a huge XML framework lies underneath, which extracts details for a call from a specification written in WSDL (which is also XML with a complex structure, incl. datatype definitions).

	== SSDP(Simple Service Discovery Protocol) ==		== SSDP (Simple Service Discovery Protocol) ==
	Also known as UPnP, the SSDP protocol announces the availability of services via broadcast UDP packages. See [https://en.wikipedia.org/wiki/Simple_Service_Discovery_Protocol Wikipedia SSDP].		Also known as UPnP, the SSDP protocol announces the availability of services via broadcast UDP packages. See [https://en.wikipedia.org/wiki/Simple_Service_Discovery_Protocol Wikipedia SSDP].

			== SSL (Secure Socket Layer)==
			Encrypted and authenticated communication. Expecco includes a pure Smalltalk implementation which is safe from buffer overflows.

	== Stderr ==		== Stderr ==

Cg: /* Smalltalk/X */

2026-05-14T10:45:52Z

Smalltalk/X

← Nächstältere Version		Version vom 14. Mai 2026, 10:45 Uhr
Zeile 251:		Zeile 251:

	== Smalltalk/X ==		== Smalltalk/X ==
	[https://www.smalltalk-x.de Smalltalk/X] ("''ST/X''") is the brand name of a Smalltalk programming language environment from exept / Claus Gittinger. Smalltalk/X is an ANSI compatible [https://en.wikipedia.org/wiki/Smalltalk Smalltalk] ~~programming~~ ~~environment,~~ and the base on which expecco and expeccoALM are built.		[https://www.smalltalk-x.de Smalltalk/X] ("''ST/X''") is the brand name of a Smalltalk programming language environment from exept / Claus Gittinger. Smalltalk/X is an ANSI compatible [https://en.wikipedia.org/wiki/Smalltalk Smalltalk] implementation with some extensions and both just-in-time and ahead-of-time compilation support (ahead-of-time means that dlls with compiled machine code can be built). ST/X is the base on which expecco and expeccoALM/AIDYMO are built.

	== SOAP (Simple Object Access Protocol) ==		== SOAP (Simple Object Access Protocol) ==

Sv: Änderung übernommen aus altem Wiki von cg, 25.11.25

2026-02-23T11:04:12Z

Änderung übernommen aus altem Wiki von cg, 25.11.25

← Nächstältere Version		Version vom 23. Februar 2026, 11:04 Uhr
Zeile 175:		Zeile 175:

	== Jython Elementary Action Block ==		== Jython Elementary Action Block ==
	Bridged Jython actions are supported by expecco. Jython is a python interpreter which runs inside a JVM, and has therefore full access to any Java framework. It can be used as an alternative to Groovy, if Java interfaces are needed.		Bridged Jython actions are supported by expecco. Jython is a python interpreter which runs inside a JVM (Java Virtual Machine), and has therefore full access to any Java framework. It can be used as an alternative to Groovy, if Java interfaces are needed.
	<br>You have to install "jython" from the official website.		<br>You have to install "jython" from the official website.
	<br>See [[Expecco_API/en#Bridged_Python_Elementary_Blocks\|"Bridged Python Elementary Blocks"]] in the Expecco API document.		<br>See [[Expecco_API/en#Bridged_Python_Elementary_Blocks\|"Bridged Python Elementary Blocks"]] in the Expecco API document.

Cg: /* expecco */

2025-10-20T12:00:41Z

expecco

← Nächstältere Version		Version vom 20. Oktober 2025, 12:00 Uhr
Zeile 111:		Zeile 111:
	== expecco ==		== expecco ==
	Does the name "expecco" mean anything?		Does the name "expecco" mean anything?
	No, but it is a pun on the latin word "peccare"/"peccō" which means to make a mistake, an error or to sin. So ex-pecco is our answer to get rid of those.		No, but it is a pun on the latin word "peccare"/"peccō" which means "to make a mistake", "an error" or "to sin". So ex-pecco is our answer to get rid of those.

	== FMI (Functional Mockup Interface) ==		== FMI (Functional Mockup Interface) ==

Cg: /* expeccoALM */

2025-10-20T11:44:18Z

expeccoALM

← Nächstältere Version		Version vom 20. Oktober 2025, 11:44 Uhr
Zeile 109:		Zeile 109:
	"<code>ets</code>" stands for [[#TestSuite Element \|"''Expecco Test Suite''"]]. These are technically zip-containers, containing the test suite in XML-format and any attachments in whatever format they where imported or generated. In addition, an index (manifest) is present, which allows for fast access to certain information without a need to read the whole zip archive. Also, signatures ensure that the manifest and remaining contents are in sync. Therefore, "<code>.ets</code>" files should not be manipulated manually, as the consistency of the suite may be harmed.		"<code>ets</code>" stands for [[#TestSuite Element \|"''Expecco Test Suite''"]]. These are technically zip-containers, containing the test suite in XML-format and any attachments in whatever format they where imported or generated. In addition, an index (manifest) is present, which allows for fast access to certain information without a need to read the whole zip archive. Also, signatures ensure that the manifest and remaining contents are in sync. Therefore, "<code>.ets</code>" files should not be manipulated manually, as the consistency of the suite may be harmed.

	== ~~expeccoALM~~ ==		== expecco ==
			Does the name "expecco" mean anything?
	Application Lifecycle Management. Now renamed to AIDYMO.
			No, but it is a pun on the latin word "peccare"/"peccō" which means to make a mistake, an error or to sin. So ex-pecco is our answer to get rid of those.

	== FMI (Functional Mockup Interface) ==		== FMI (Functional Mockup Interface) ==

Cg: /* Inconclusive State / Test Outcome */

2025-09-08T13:20:11Z

Inconclusive State / Test Outcome

← Nächstältere Version		Version vom 8. September 2025, 13:20 Uhr
Zeile 152:		Zeile 152:
	== Inconclusive State / Test Outcome ==		== Inconclusive State / Test Outcome ==
	See [[#Verdict\| "Verdict"]] in this document.		See [[#Verdict\| "Verdict"]] in this document.
			== IPC ==
			Short for interprocess communication. Typically a socket, pipe or shared memory.

	== IronPython Elementary Action Block ==		== IronPython Elementary Action Block ==

Cg: /* Verdict */

2025-04-29T23:48:45Z

Verdict

← Nächstältere Version		Version vom 29. April 2025, 23:48 Uhr
Zeile 319:		Zeile 319:
	* '''FAIL''' (red)<br>the execution detected an error in the [[#SUT (System Under Test)\| System Under Test (SUT)]].		* '''FAIL''' (red)<br>the execution detected an error in the [[#SUT (System Under Test)\| System Under Test (SUT)]].
	:For example, it measured a wrong/unexpected value, detected invalid behavior, invalid protocol behavior etc.		:For example, it measured a wrong/unexpected value, detected invalid behavior, invalid protocol behavior etc.
	:Usually, this means that the ~~developper~~ of the tested system is to be informed.		:Usually, this means that the developer of the tested system is to be informed.
	* '''ERROR''' (dark red)<br>the test itself ran into some error.		* '''ERROR''' (dark red)<br>the test itself ran into some error.
	:This means that during the test's execution, an error occurred inside expecco or one of the user-defined action blocks. An ERROR state does not provide information about the SUT's state; instead, the test has a problem.		:This means that during the test's execution, an error occurred inside expecco or one of the user-defined action blocks. An ERROR state does not provide information about the SUT's state; instead, the test has a problem.
	:For example, if a file containing test-data could not be found or a division by zero or an index out of bounds error occurred etc.		:For example, if a file containing test-data could not be found or a division by zero or an index out of bounds error occurred etc.
	:Usually, this means that the ~~developper~~ of the test is to be informed.		:Usually, this means that the developer of the test is to be informed.
	* '''INCONCLUSIVE''' (gray)<br>the test had no chance to perform its testing operation(s).		* '''INCONCLUSIVE''' (gray)<br>the test had no chance to perform its testing operation(s).
	:For example, if a machine could not be reached in the network, if it was not powered up or if a resource (operator, measurement device, test-device etc.) was not available, etc. Also, tests or actions which have not been executed (eg. skipped) are marked as inconclusive.		:For example, if a machine could not be reached in the network, if it was not powered up or if a resource (operator, measurement device, test-device etc.) was not available, etc. Also, tests or actions which have not been executed (eg. skipped) are marked as inconclusive.