Glossary/en: Unterschied zwischen den Versionen

Aus expecco Wiki (Version 2.x)
Zur Navigation springen Zur Suche springen
Zeile 2: Zeile 2:


== Black Box Test ==
== Black Box Test ==
The test machine and application are completely separated from the System Under Test (SUT). No knowledge about the internals of the SUT is known when testing. The test only operates against official external interfaces, such as protocols, data and configuration files, command line interfaces, GUI interfaces or communication protocols.
The test machine and application are completely separated from the System Under Test (SUT). No knowledge about the internals of the SUT is known when testing. The test only operates against official external interfaces, such as input/output, data and configuration files, command line interfaces, GUI interfaces or communication protocols. The opposite being a "White Box Test", which executes inside the SUT and has full access to all internal details. 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".


== [[CompoundBlock Element|Compound Block]] ==
== [[CompoundBlock Element|Compound Block]] ==

Version vom 7. August 2015, 09:04 Uhr

Please keep this list alphabetically sorted!

Black Box Test[Bearbeiten]

The test machine and application are completely separated from the System Under Test (SUT). No knowledge about the internals of the SUT is known when testing. The test only operates against official external interfaces, such as input/output, data and configuration files, command line interfaces, GUI interfaces or communication protocols. The opposite being a "White Box Test", which executes inside the SUT and has full access to all internal details. 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".

Compound Block[Bearbeiten]

An action block which is defined by an activity diagram. Its execution semantics are defined by a network of interconnected steps. These themselfes can be compound- or elementary steps. See Compound Block in the Tree Elements documentation.

Compound Step[Bearbeiten]

A step inside an activity diagram, whose action definition is a compound block. When triggered, such a step will execute another activity diagram. See Compound Block in the Tree Elements documentation.

Elementary Block[Bearbeiten]

An non-compund action block. I.e. any action which is not defined by an activity diagram, but either built in (well known to expecco), a call to an external function or application, or defined programmatically as a piece of program code in one of the supported programming languages.

Elementary Step[Bearbeiten]

A step inside an activity diagram, whose action definition is an elementary block. When triggered, such a step will execute either a builtin function, an existing function inside a DLL, another program or a piece of code written in one of the programming languages supported by expecco.

Gray Box Test[Bearbeiten]

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 no often no clear line of separation between them.

Groovy[Bearbeiten]

A language interpreter which runs on top of a Java Virtual Machine (JVM), with a language very similar and almost compatible to Java. Used in expecco to call into Java interfaces or define required callback and listener classes, in case the SUT or the interface to the SUT require those. Groovy code is compiled to bytecode inside the JVM, which is further Just-in-Time compiled to fast machine code within the target JVM. Thus, it executes at full Java speed. Expecco allows for Groovy code to be executed both on the local machine (the one on which expecco itself is running) and on remote machines which are reachable from the local machine via a TCP/IP connection. Multiple of these connections are possible and handled simultaneously in parallel, making it possisble to interact with multiple hosts in a distributed system or when testing both ends of a communication protocol. See "Groovy Elementary Blocks" in the Expecco API Document and Elementary Block in the Tree Elements documentation.

Groovy Elementary Block[Bearbeiten]

An action block which is defined by an execute function which is written in the Groovy language. The block's code will be executed by a Groovy interpreter on a Java Virtual Machine (JVM). The JVM may run either on the local or on a remote machine. See "Groovy Elementary Blocks" in the Expecco API Document and Elementary Block in the Tree Elements documentation.

JavaScript Elementary Block[Bearbeiten]

An action block which is defined by an execute function which is written in a JavaScript like language. The block's code will be executed inside expecco itself. See "JavaScript Elementary Blocks" in the Expecco API Document and Elementary Block in the Tree Elements documentation.

Smalltalk Elementary Block[Bearbeiten]

An action block which is defined by an execute function which is written in the Smalltalk language. The block's code will be executed inside expecco itself. See "Smalltalk Elementary Blocks" in the Expecco API Document and Elementary Block in the Tree Elements documentation.

SUT (System Under Test)[Bearbeiten]

The tested system. Expecco interacts with this either in a pure black box (only talking to external interfaces), or gray box fashion (some knowledge about internals of the SUT are known).

White Box Test[Bearbeiten]

The test runs within the System Under Test and uses (but also depends on) the internals of the System Under Test. The test directly creates or manipulates data objects inside the SUT and/or calls internal functions. Most unit tests are typically implemented as white box tests (but not required to be so).



Copyright © 2014-2024 eXept Software AG