Plot/Graph Action Blocks

2026-03-03T11:13:55Z

Sv:

== Introduction ==

With expecco18.1, a new block type named "''Plot/Graph Actions''" is introduced.
These behave similar to other script action blocks, in that they are defined by a script
(in this case: gnuplot scripting language) and are placed into the test sequence flow
just like any other block.

However, when executed, these actions generate a graphic document (jpeg, png or postscript),
which is then either added to the activity log, or added as attachment. It will therefore be
available in the generated "<code>elf</code>" execution log file, or shown in the generated "<code>pdf</code>" report file.
Of course, you can do anything you like with the generated graphic file, by feeding the name
of the generated file to another action for further processing.

Notice: if you prefer other graphic packages or other programming languages, you may of course use R language scripts or Python scripts (with matplotlib and/or seaboarn) to generate graphics in a similar way.

== Creating Plot/Graph Action Blocks ==

Plot/graph action blocks are created via the
"''Actions'' - ''More'' - ''Plot/Graph''" menu item.

[[Datei:Plot_Graph_Actions_in_Menu.png|200px]]

Select the "''Plot/Graph''" item, to create a new gnuplot action.
An initial set of input pins and an initial (demo-) script is generated for you.

For details on the scripting language, please refer to the public gnuplot documentation
[http://www.gnuplot.info/docs_5.0/gnuplot.pdf "http://www.gnuplot.info/docs_6.0/Gnuplot_6.pdf"].

Any input pin named "<code><pinName></code>" is available in the script as "<code>%(pinName)</code>".
Thus, the script can be parametrized in arbitrary ways.
A number of pins are already created for you; these are:
* "'''outputFile'''"<br>both an input and an output. If the input is specified, gnuplot will generate the plot into that file. Otherwise, a new temporary file will be created and the output written into that. In any case will the actual outputFileName be available on the corresponding output pin for further processing.

* "'''outputFormat'''"<br>specifies the kind of file to generate. For inclusion into the report, an image format should be chosen (i.e. one of "jpeg", "png" or "gif"). For archival or to generate high quality documents, you can also choose "postscript" or "svg". However, those can (currently) not be automatically converted for the pdf report.<br>On Unix systems, you can also specify "x11" as output format. In this case, a window is opened, displaying the generated graph. Be aware that expecco is (currently) not informed about the window being closed, so you may have to stop the test-run via the expecco-"Stop" button.

* "'''title'''"<br>A title string to be drawn above the graphic (actually, the position of the title is specified by the "set key" gnuplot expression, inside the script)

* "'''data'''"<br>If connected, and a collection of values is present, these values will be written into a temporary data file, and the filename is available in the gnuplot script as "<code>%(data)</code>". Theis will be the raw data, to be processed by the script.

* "'''dataSize'''"<br>There is no pin for that, but the value is available to the script. It provides the number of data points (or rows) in the data file.

* "'''attachToLog'''"<br>if true (the default), the generated graph will be attached to the final pdf report. This pin's value is not forwarded to the gnuplot script.

You can add additional input pins and refer to the corresponding pin value in the script with the "%(...)" notation.

== A Simple Graph Script ==

A typical gnuplot script looks like:

# The code below is sent to gnuplot and the generated output
# will be stored in a file named %%(outputFile)
# (unless explicitly specified, a temporary file is created)
#
set output "%(outputFile)"

#
set term %(outputFormat)

# All input pin values can be used here as %%(nameOfPin).
# so the next line controls the title via the "title" pin
#
set title "%(title)"

# You can add more pins.
# For example, add pins named "min" and "max" with type Number,
# and replace "-10:10" below by "%%(min):%%(max) to parametrize the y-axis range.
set key left box
plot [1:%(dataSize)] [-10:10] "%(data)" title "My Data" with impulses

to plot a simple impulse graph of the data values, as presented at the input pin,
assuming that the pins get the following values:
* "outputFile" - leave unconnected or remove the pin (to let the action choose a temp file)
* "outputFormat" - freeze as "<code>png</code>"
* "title" - any title - such as "Measurement #1"
* "data" - a vector of numbers

Of course, this is actually the simplest possible script to render such data.
Gnuplot provides a wide area of possible plots, both 2D and 3D, with or without colors, etc.
A few examples are provided in the "<code>Plot_Graph Library.ets</code>", but much more is found on the gnuplot
website and gnuplot documentation [http://www.gnuplot.info/docs_5.0/gnuplot.pdf "http://www.gnuplot.info/docs_5.0/gnuplot.pdf"].

== Short List of Useful Script Commands ==

For a full list, please take a look at the gnu plot documentation [http://www.gnuplot.info/docs_5.0/gnuplot.pdf "http://www.gnuplot.info/docs_5.0/gnuplot.pdf"]. The following list is only presenting the most common plot commands:
* <code>plot [xMin:xMax] [yMin:yMax] "nameOfDataFile" title "graph title" with impulses</code><br>You can omit the "[yMin:yMax]" parameter, for a reasonable box to be automatically chosen by gnuplot.<br>Replace "nameOfDataFile" by "%(data)" if the data comes via an input pin and is not already in a file.

*<code>plot [xMin:xMax] [yMin:yMax] "nameOfDataFile" title "graph title"</code><br>Without the "impulses" parameter, a regular graph is drawn (straight lines between points)

*<code>plot [xMin:xMax] [yMin:yMax] "nameOfDataFile" title "graph title" with: lines</code><br>The same as above (straight lines between points)

*<code>plot [xMin:xMax] [yMin:yMax] "nameOfDataFile" title "graph title" with: dots</code><br>Draws dots

*<code>plot [xMin:xMax] [yMin:yMax] "nameOfDataFile" title "graph title" with candlesticks</code><br>the data file should contain multiple colums per line. Select the colums with a "using..." parameter.

*<code>set key left box</code><br>defines the position (left) and type (boxed) of the graph-title (the string comes from the <code>title "graph title"</code> argument in the plot command)

*<code>set title "someTitle"</code><br>defines a headline title

*<code>set term %(outputFormat)</code><br>defines the type of image to be generated. For "%(outputFormat)", the input pin's format is generated. Otherwise, you can also hardcode any of "<code>png</code>", "<code>jpg</code>", etc. here

A few examples are found in the demo library: "Plot_Graph_Library.ets", which is found in the plugin's folder and in the online documentation [http://www.gnuplot.info/docs_5.0/gnuplot.pdf "http://www.gnuplot.info/docs_5.0/gnuplot.pdf"].

== Accessing Data from Attachments ==

You can directly access expecco attachment files by their name inside the script. I.e. if you have an attachment with file named "<code>foo.dat</code>", use <code>... data "foo.dat" ...</code> inside the script. Notice that the attchment's filename is to be used - not its name in the tree.

== Plotting Multiple Graphs into a Single Picture ==

To do this, generate multiple datasets (as ascii files, with one textline per row). Add <code>data<i></code> input pins and feed them the filenames. Add multiple <code>plot</code> commands, each with its own "<code>%(data<i></code>)" argument, and possibly with its own graph-title.

== Changing the Size of the Generated Image ==

By default, the generated image's size is 640 x 400 pixels.
For a fix size, change the script's "<code>set term</code>" statement to:

set term %(outputFormat) size <width>,<height>

where <width> and <height> define the size in pixels.

Alternatively, add two pins named "''width''" and "''height''", and
change the statement to:

set term %(outputFormat) size %(width),%(height)

and provide the desired size (as integers) at the input pins.

== Caveats ==

Do not place <code>pause</code> statements into the script; there is no input stream given to gnuplot, so it will immediately read an EOF (end of file) and proceed.

== Complete Example 1: Gathering Response Times of MQTT Protocol Messages ==

This example demonstrates, how a test suite can gather response times of a remote system,
when sending MQTT messages to it.

==== Step 1: Define the Test Sequence ====

this is a very simple publish-response setup, in that a topic is published to an MQTT broker,
and the time measured, until the notification arrives (in order to run this on your machine,
the expecco MQTT plugin needs to be installed):

Outside (Schema) view of the measuring action:

[[Datei:Schema_Measuring_MQTT.png|400px]]

which is implemented as:

[[Datei:Net_Measuring_MQTT.png|800px]]

The yellow area does the MQTT setup. First, an MQTT client connection is created,
and the client handle forwarded to the Subscribe action, which registers expecco
to react to the "expeccoTesting/test" topic.

The green area does the actual publish operation,
publishing the "Hello from Expecco" string on this topic.

In parallel, the blue area waits for the next incoming event,
(and generates a printed detail info on the received packet for the
activity log).

The red area contains a stopWatch action block, which gets started
with when the publish is done, and stops when the event arrives.

The measurement action is prametrized with the broker's host and port,
and generates the measured timeDuration as output.

==== Step 2: Test Run ====

Assuming that you have an MQTT client running on the local host,
the test sequence can be immediately tried via the Test/Demo page:

[[Datei:Test_Measuring_MQTT.png|300px]]

A good strategy is to package the MQTT broker into a docker file.
Here is the MQTT client's output of the above run:

$ sh rundocker.sh
1522084243: mosquitto version 1.4.8 (build date Thu, 01 Mar 2018 09:34:49 -0500) starting
1522084243: Using default config.
1522084243: Opening ipv4 listen socket on port 1883.
1522084243: Opening ipv6 listen socket on port 1883.
1522084272: New connection from 172.17.0.1 on port 1883.
1522084272: New client connected from 172.17.0.1 as expeccoMQTT (c1, k0).
1522084272: Client expeccoMQTT disconnected.

and here the activitylog in expecco:

[[Datei:Log1_Measuring_MQTT.png|600px]]

with the event info detail:

[[Datei:Log2_Measuring_MQTT.png|600px]]

==== Step 3: Running that Sequence Multiple Times ====

Now that we have verified, that the communication with the MQTT broker works correctly,
we create another action bock, which runs the above action multiple times and collects
all the execution times:

[[Datei:Multiple_Measuring_MQTT.png|700px]]

[ explanation: first, a new empty colletion is created, then, the timing values of
the multi-triggered measure-step are all added to this collection.
When done (no step active), the collection is forwarded (now filled) to the output pin]

Here is the activity log after 10 runs:

[[Datei:Log1_Multiple_Measuring_MQTT.png|700px]]

==== Step 4: Adding the Graph ====

The last step is the easiest: select the "New Plot/Graph" action block from the menu,
name it "Time Measurement Graph"
and change its autogenerated gnuplot script to:

set output "%(outputFile)"
set term %(outputFormat)
set title "%(title)"
set key left box
plot [1:%(dataSize)] [0:100] "%(data)" title "%(lineTitle)" with impulses

then place a step of it into your network and connect the "collectedTimes" output of the above measurement step with the "data" input
of the "Measurement-Graph" step:

[[Datei:Multiple_Measuring_plus_Graph_MQTT.png|500px]]

Running it, and generating the report, produces the following pdf-report (the logging of subactivities was disabled for this report):

[[Datei:Multiple_Measuring_MQTT_Report_img.png|700px]]

[[Datei:Multiple_Measuring_MQTT_Report.pdf]]

== Example 1 Simplified: Using Probes to Gather the Data ==

The above data collection may look a bit complicated, due to the need for start/stop synchronization.
A much nicer and easier to use solution is in using a probe to gather the data.
For this, we need a probe which does no range checks, but instead only collects the incoming values:

[[Datei:Measuring_MQTT_with_Probe.png|700px]]

Here, a probe was added (via the "timeDelta" pin's "Add Probe" menu item),
and specified to "collect incoming data without check":

[[Datei:Measuring_MQTT_with_ProbeMenu.png|500px]]

Now that we have a probe at the roundtrip time,
the outer measurement looks much simpler:

* reset the probe (to clear any previously gathered data)
* prime the probe enable data collecting)
* run the roundtrip-test n-times
* unprime the probe (disable further data collecting)
* fetch the probe's values and pass them to the gnuplot action

[[Datei:Measuring_MQTT_with_Probe2.png|500px]]

== See Also ==
[http://www.gnuplot.info/docs_5.0/gnuplot.pdf Gnuplot Manual]
<br>[https://alvinalexander.com/technology/gnuplot-charts-graphs-examples Collection of Examples]

"[[R Action Blocks]]" which provide similar graph/plot functions in addition to sophisticated mathematical and statistics libraries.
<br>"[[Octave Script Action Tutorial|Octave/Matlab Actions]]" another framework for mathematical computations and/or to generate graphs/plots.



[[Category: Languages ]]

Release Notes 26.x

2026-02-23T13:31:04Z

Sv: /* Release 26.1 (Q2 2026) */

Release Notes 26.x

2026-02-23T13:30:43Z

Sv: Release dates added

See also: [[Release Notes 25.x]]
<br />

== Release 26.2 (Q4 2026) ==

== Release 26.1 (Q" 2026) ==
*Feature: Qt-Plugin supports Qt6.8 ([[QT_Testing/en#ExpeccoTestService_Library%3A_Delivery_in_Expecco_Versions|Delivered versions for QT and build environment]])
* Feature: improved search text box behavior in text editors (type RETURN, CMD-f or CMD-b while box is open) and back to original position button added.

Hauptseite

2026-02-23T13:29:46Z

Sv:

[[Hauptseite/en|English Version]]

Klicken Sie links auf ''"Letzte Änderungen"'' ("Recent changes") um die neuesten Einträge in der Dokumentation zu sehen.<br>Sie sehen dann meist, woran unsere Entwickler gerade vornehmlich arbeiten.

<h2>expecco</h2>

<div style="display:flex; flex-wrap:wrap; padding:0; white-space:nowrap">
<div style="background-color:#ecf0fe; margin:12px 8px 0 0; flex:1 0 auto">

<span style="padding-left:0.6em">[[Datei:Icon_Landingpage.png|30px]]</span><span style="padding:0 1em">Für Einsteiger</span><hr>

<ul style="font-size:0.8em; padding:0.7em 1em 1em 2.4em">


<li>[https://doc.expecco.de/w2.x/index.php?title=Was_ist_expecco%3F Allgemeine Informationen]</li>
<li>[[Expecco Usecases|Einsatzbereiche]]</li>
<li>[[Features|expecco Feature-List]]</li>
<li>[[Tutorials]]</li>
<li>[[usageHints/en|Hinweise zur Bedienung]]</li>
<li>[[Glossary|Begriffserklärung]] (Glossar)</li>

<li>[[FAQ]]</li>
</ul>
</div>

<div style="background-color:#ecf0fe; margin:12px 8px 0 0; flex:1 0 auto">

<span style="padding-left:0.6em">[[Datei:Icon_Landingpage5.png|30px]]</span><span style="padding:0 1em">Installation</span><hr>

<ul style="font-size:0.8em; padding:0.7em 1em 1em 2.4em">
<li>[[Installation]]</li>
<li>[[Installing additional Frameworks/en| Installation zusätzlicher Tools (Node, Python, ...)]]</li>
<li>[[Personal Settings|Persönliche Einstellungen]]</li>
<li>[[Configuration & Setup|Konfiguration]]</li>
<li>[[Anbindung expecco ALM]]</li>
<li>[[SAP_Testing|Anbindung expecco an SAP]]</li>
<li>[[Spezifische Anpassung]]</li>
<li>[[expecco UI]]</li>
<li>[[Expecco_Remote_Control_App|expecco Mobile Remote App]]</li>
<li>[[Probleme & Fehler]]</li>
</ul>
</div>

<div style="background-color:#ecf0fe; margin:12px 8px 0 0; flex:1 0 auto">

<span style="padding-left:0.6em">[[Datei:Icon_Landingpage4.png|30px]]</span><span style="padding:0 1em">Werkzeuge</span><hr>

<ul style="font-size:0.8em; padding:0.7em 1em 1em 2.4em">
<li>[[API von Elementaraktionen]]</li>
<li>[[Debugger]]</li>
<li>[[Editoren]]</li>
<li>[[Standard Libraries/Bibliotheken]]</li>
<li>[[Weitere Werkzeuge]]</li>
<li>[[Weitere Funktionen]]</li>
</ul>
</div>

<div style="background-color:#ecf0fe; margin:12px 8px 0 0; flex:1 0 auto">

<span style="padding-left:0.6em">[[Datei:Icon_Landingpage6.png|30px]]</span><span style="padding:0 1em">Reportgenerierung</span><hr>

<ul style="font-size:0.8em; padding:0.7em 1em 1em 2.4em">
<li>[[Report Generation|Reportgenerierung]]</li>
<li>[[Errors during Execution|Fehler während der Ausführung]]</li>
<li>[[Secret Strings|Geheime Zeichenketten und Passwörter]]</li>
</ul>
</div>

<div style="background-color:#ecf0fe; margin:12px 8px 0 0; flex:1 0 auto">

<span style="padding-left:0.6em">[[Datei:Erweiterung_plugin.png|30px]]</span><span style="padding:0 1em">Erweiterungen (Plugins)</span><hr>

<ul style="font-size:0.8em; padding:0.7em 1em 1em 2.4em">
<li>[[GUI Testing]]
<ul>
<li>[[Java GUI Plugins|Java Swing/FX/SWT UI Testing]]</li>
<li>[[Mobile Testing Plugin|Mobile Testing auf Android und iOS]]</li>
<li>[[WindowsAutomation Reference 2.0|UI Testing mit der Windows Automation Library]]</li>
<li>[[Selenium_WebDriver_Plugin|Web Testing mit Selenium WebDriver]]</li>
<li>[[VNC_Plugin_Reference|VNC UI Testing]]</li>
<li>[[GUI Testing|Weitere GUI Testing Plugins]]</li>
</ul>
</li>
<li>[[Schnittstellen zum SUT]]</li>
<li>[[ManualTest]]</li>
<li>Produktivität
<ul>
<li>[[GIT Plugin]]</li>
<li>[[HG Plugin (Mercurial)]]</li>
<li>[[CVS Plugin]]</li>
<li>[[Anbindung expecco ALM | expeccoALM Schnittstelle]]</li>
</ul>
</li>
<li>[[Weitere Plugins]]</li>
</ul>
</div>

<div style="background-color:#ecf0fe; margin:12px 8px 0 0; flex:1 0 auto">

<span style="padding-left:0.6em">[[Datei:Icon_Landingpage3.png|30px]]</span><span style="padding:0 1em">Elemente der Testsuite</span><hr>

<ul style="font-size:0.8em; padding:0.7em 1em 1em 2.4em">
<li>[[Tree Elements|Tree Elemente]]</li>
<li>[[Folder Element|Ordner]]</li>
<li>[[Testplan Element]]</li>
<li>[[Aktionen/Aktionsblöcke]]</li>
<li>[[Datatype Element|Datentyp Element]]</li>
<li>[[Inventory Element]]</li>
<li>[[Skill Element]]</li>
<li>[[Resource Element|Ressource Element]]</li>
<li>[[Attachment Element|Anhänge]]</li>
<li>[[ReportTemplate Element|Report Templates]]</li>
</ul>
</div>

<div style="background-color:#ecf0fe; margin:12px 8px 0 0; flex:1 0 auto">

<span style="padding-left:0.6em">[[Datei:Icon_Landingpage3.png|30px]]</span><span style="padding:0 1em">API Referenz (Elementarbausteine)</span><hr>

<ul style="font-size:0.8em; padding:0.7em 1em 1em 2.4em">
<li>[[API von Elementaraktionen|Übersicht]]</li>
<li>[[Expecco API#JavaScript_and_Smalltalk_Elementary_Blocks|Smalltalk & JavaScript]]</li>
<li>[[Expecco API#Groovy_Elementary_Blocks|Groovy]]</li>
<li>[[Expecco_API#Node.js_.28Bridged.29_Elementary_Blocks|NodeJS]]</li>
<li>[[Expecco_API#Bridged_Python_Elementary_Blocks|Python]]</li>
<li>[[Expecco_API#Bridged_Ruby_Elementary_Blocks|Ruby]]</li>
<li>[[Expecco_API#Bridged_C_Elementary_Blocks|C]]</li>
<li>[[Expecco API#VisualBasic_Elementary_Blocks|VisualBasic ]]</li>
<li>[[Expecco Scripting API|Shell und Script Languages]]</li>
<p> </p>
<li>[[Useful API Functions|Useful API Functions:]]</li>
<ul>
<li>[[Number API Functions|Number API Functions]]</li>
<li>[[String API Functions|String API Functions]]</li>
<li>[[Collection API Functions|Collection API Functions]]</li>
<li>[[Filename API Functions|Filename API Functions]]</li>
<li>[[Stream API Functions|Stream API Functions]]</li>
<li>[[Date_and_Time_API_Functions|Date & Time API Functions]]</li>
</ul>
</ul>
</div>

<div style="background-color:#ecf0fe; margin:12px 8px 0 0; flex:1 0 auto">

<span style="padding-left:0.6em">[[Datei:Diagramm.png|30px]]</span><span style="padding:0 1em">Diagramm - Elemente</span><hr>

<ul style="font-size:0.8em; padding:0.7em 1em 1em 2.4em">
<li>[[DiagramElements-Step|Schritt]]</li>
<li>[[Pins (Ein - Ausgänge)]]</li>
<li>[[Code Ausführung]]</li>
<li>[[DiagramElements-Connection|Verbindung]]</li>
<li>[[DiagramElements-Pin|Pin Beschreibung]]</li>
<li>[[DiagramElements-Annotation|Notiz]]</li>
<li>[[DiagramElements-Probe|Messfühler]]</li>
</ul>
</div>

<div style="background-color:#ecf0fe; margin:12px 8px 0 0; flex:1 0 auto">

<span style="padding-left:0.6em">[[Datei:Refresh.png|30px]]</span><span style="padding:0 1em">Sonstiges</span><hr>

<ul style="font-size:0.8em; padding:0.7em 1em 1em 2.4em">
<li>[[Release Notes 26.x]]</li>
<li>[[Release Notes 25.x]]</li>
<li>[[Release Notes 24.x]]</li>
<li>[[Release Notes 23.x]]</li>
<li>[[Release Notes 22.x]]</li>
<li>[[Release Notes 21.x]]</li>
<li>[[Release Notes 20.x]]</li>
<li>[[Release Notes 19.x]]</li>
<li>[[Release Notes 18.x]]</li>
<li>[[Release Notes 2.x]]</li>
<li>[[Release Notes 1.x]]</li>
<li>[[Future releases expecco|Zukünftige Releases]]</li>
<li>[[Smalltalk]]</li>
</ul>
</div>

<div style="background-color:#ecf0fe; margin:12px 8px 0 0; flex:1 0 auto">

<span style="padding-left:0.6em">[[Datei:Beispiele_icon.png|30px]]</span><span style="padding:0 1em">Beispiele</span><hr>
<span style="padding:0 1em;font-size:0.9em">Sie haben Fragen, wie ein Projekt aussieht?</span><hr>

<ul style="font-size:0.8em; padding:0.7em 1em 1em 2.4em">
 
<li>[[Beispiele | Hier finden Sie weitere Anwendungsbeispiele.]]</li>
<li>[[Expecco Code Snippets/en | Codeschnipsel]]</li>
</ul>
</div>

<div style="background-color:#ecf0fe; margin:12px 8px 0 0; flex:1 0 auto">

<span style="padding-left:0.6em">[[Datei:Beispiele_icon.png|30px]]</span><span style="padding:0 1em">Unterstützung weiterer Qualitätsmanagement Tools</span><hr>

<ul style="font-size:0.8em; padding:0.7em 1em 1em 2.4em">
<li>[[Jira_Plugin_Reference|Jira]]</li>
<li>[[PolarionPlugin_Reference|Polarion]]</li>
<li>[[Aqua_Plugin_Reference|Aqua]]</li>
<li>[[Starting_expecco_via_Command_Line#Integration_with_Jenkins|Jenkins Integration]]</li>

</ul>
</div>

</div>

<h2 style="clear:left">expecco ALM</h2>

<div style="display:flex; flex-wrap:wrap; padding:0; white-space:nowrap">
<div style="background-color:#ecf0fe; margin:12px 8px 0 0; flex:1 0 auto">

<span style="padding-left:0.6em">[[Datei:Sonstiges-Info.png|30px]]</span><span style="padding:0 1em">Allgemein</span><hr>

<ul style="font-size:0.8em; padding:0.7em 1em 1em 2.4em">
<li>[[Was ist expecco ALM?]]</li>
<li>[[Was ist der expecco Lizenzserver?]]</li>
<li>[[Anbindung expecco ALM]]</li>
<li>[[Rollen und Rechte]]</li>
<li>[[Filter]]</li>
<li>[[FAQ expeccoALM/en | FAQ]]</li>
</ul>
</div>

<div style="background-color:#ecf0fe; margin:12px 8px 0 0; flex:1 0 auto">

<span style="padding-left:0.6em">[[Datei:Icon_Landingpage5.png|30px]]</span><span style="padding:0 1em">Installation/Einrichten</span><hr>

<ul style="font-size:0.8em; padding:0.7em 1em 1em 2.4em">
<li>[[expecco ALM Installation|Installation]]</li>
<li>[[expecco ALM Installation Patches|expecco ALM Installation Patches]]</li>
<li>[[expecco ALM Einrichten Vorgehensweise|expecco ALM Einrichten]]</li>
<li>[[expecco ALM expecco Patch Service |Patchservice für expecco]]</li>
</ul>
</div>

<div style="background-color:#ecf0fe; margin:12px 8px 0 0; flex:1 0 auto">

<span style="padding-left:0.6em">[[Datei:Refresh.png|30px]]</span><span style="padding:0 1em">Plugins</span><hr>

<ul style="font-size:0.8em; padding:0.7em 1em 1em 2.4em">
<li>[[AIDYMO Jira|Atlassian Jira]]</li>
<li>[[CustomerSpecific|Kundenspezifische Portale]]</li>
</ul>
</div>

<div style="background-color:#ecf0fe; margin:12px 8px 0 0; flex:1 0 auto">

<span style="padding-left:0.6em">[[Datei:Refresh.png|30px]]</span><span style="padding:0 1em">Sonstiges</span><hr>

<ul style="font-size:0.8em; padding:0.7em 1em 1em 2.4em">
<li>[[expecco ALM App]]</li>
<li>[[Installation Lizenzserver]]</li>
<li>[[expecco ALM Release Notes|Release Notes]]</li>
<li>[[expecco ALM Known Issues|Known Issues]]</li>
</ul>
</div>
</div>

Settings ExternalScriptInterpreterSettings/en

2026-02-23T12:53:21Z

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

== External Script Interpreter Settings ==

=== General Script Execution ===
===== Additional Path =====
Defines additional paths which are added to the $PATH environment variable (%PATH% on Windows).
This is passed to any external script interpreter.<br>
[[Datei:bulb.png|20px]]Notice, that paths are separated by ":" (colon) under Unix/Linux but ";" (semi) under Windows.
Additional paths are useful if a script calls for other programs, and you do not want to hardcode any paths in the script, in order to allow for the suite to be portable to other machines.

===== Environment Variables =====
Additional environment variables passed to external script interpreters.
To change, enter name and value and press "''Add''", or select a variable from the list and press "''Remove''".

== Subitems under External Script Interpreter Settings ==

* [[ Settings_ExternalScriptInterpreters_Shell_and_BatchSettings/en |Shell & Batch Settings]]
* [[ Settings_ExternalScriptInterpreters_GroovyClassPathSettings/en|Groovy Class Path Settings]]
* [[ Settings_ExternalScriptInterpreters_NodeSettings/en|Node Settings]]
* [[ Settings_ExternalScriptInterpreters_PythonSettings/en|Python Settings]]
* [[ Settings_ExternalScriptInterpreters_Jython_and_IronPythonSettings/en|Jython & IronPython Settings]]
* [[ Settings_ExternalScriptInterpreters_CBridgeSettings/en|CBridge Settings]]
* [[ Settings_ExternalScriptInterpreters_ClingSettings/en|Root/Cling Settings]]
* [[ Settings_ExternalScriptInterpreters_RubySettings/en|Ruby Settings]]
* [[ Settings_ExternalScriptInterpreters_DartSettings/en|Dart Settings]]
* [[ Settings_ExternalScriptInterpreters_JuliaSettings/en|Julia Settings]]
* [[ Settings_ExternalScriptInterpreters_SmalltalkSettings/en|Smalltalk Settings]]
* [[ Settings_ExternalScriptInterpreters_SchemeSettings/en|Scheme Settings]]
* [[ Settings_ExternalScriptInterpreters_OtherSettings/en|Other Settings]]

 
----

See also [[ Installing_additional_Frameworks/en |"Installing additional frameworks"]].

[[ Settings_ExternalScriptInterpreterSettings/en|Back to "External Script Interpreter Settings"]]
<br>
[[ Settings/en|Back to the main page "Settings"]]

[[Category:Settings]]

Settings SSDPSettings/en

2026-02-23T12:50:54Z

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

== Enable SSDP Announcements ==

If enabled, expecco will announce its availability via SSDP multicast messages (also known as UPnP).
These announcements are especially useful for:
* the remote control app which runs on a mobile device
* other expeccos to detect possible execution partners
* expeccoALM to detect possible execution slaves
* administrators looking for machines which might have floating licenses allocated

[[Datei:bulb.png|20px]]Notice, that SSDP messages are UDP messages which are sent in regular time intervals,
and received within your local network (the site), depending on your router/switch and firewall setup.

To reduce traffic in the local network, some (usually bigger) organizations might disable, block or forbid SSDP announcements.
Or their spread may be limited to a subset of your machines (i.e. rooms/departments).
<br>Also, WLAN access points may have to be configured to forward these messages within the segment.

If in doubt, ask your administrator.

For your convenience, expecco includes a monitor window to show incoming SSDP messages ("''Extras''" → "''Debugging''" → "''Network Diagnose''" → "''SSDP Monitor''").

Folder Element/en

2026-02-23T12:48:51Z

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

== Introduction ==
Folder elements are used to group related items. Notice that any action block item can have sub items. Besides being used to specify user-defined action menus (see [[Testsuite Editor-Metadata Editor/en | Testsuite Editor]]), folders have no special semantic relevance.

[[Datei:bulb.png|20px]]Notice that in contrast to other test tools, folders are NOT used to group testcases into test sequences or sub-activities into a composite activities. They are only used for organization - not to specify any execution order or execution behavior.

Folder elements only provide a single editor tab, into which documentation related to the folder can be entered. If this documentation is left empty, the documentation editor presents a short summary of the containing element's documentation texts (read-only).

== Useful Tricks ==

=== Public vs. Private Actions ===

In imported library suites, put stuff which is supposed to be used by importing projects into a separate folder named "API" or "Exported". This makes it easier for other team members to find reusable stuff. You may also want to change the folder's icon color (contextMenu → "''Misc''" → "''IconColor''") to emphasize particular folders (such as "red" for obsolete or experimental actions, "green" for released/public actions etc.)

=== Demos and Examples ===

Add a folder named "Playground", "Sandbox" or "Examples" or similar and place compound action blocks which demonstrate key features or low level access functionality. Other team members may later easily find those and play with the examples. It is also a good idea to place simple connection, communication, [[Glossary/en#SUT_.28System_Under_Test.29|SUT]] is running tests, setup and shutdown blocks there (unless those are commonly used, then put them into API/Exported).

=== Define Useful Actions as Menu Functions ===

Add a folder named "menu Actions" or similar, place and useful actions for test setup, equipment startup and shutdown or calibration into it. When this folder is defined as the project's operation menu folder (in the test suite's "Misc" editor page), you can quickly execute those functions via the main menu. For more information, see [[User Defined Menu Items]].

== See Also ==

[[Tree Elements]]
<br>[[ Navigation Tree ]]

[[Category: Tree Elements]]

Settings WindowsAutomationSettings/en

2026-02-23T12:47:06Z

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

[[Datei:bulb.png|20px]]Notice:<br>The Windows Automation Plugin (WA V1) has been replaced by a new version,
and is only maintained to provide backward compatibility for customers using it.
Please migrate to use the WA2 Plugin, which is described in
"[[WindowsAutomation_Reference_2.0/en| WindowsAutomation Reference 2.0]]".

== Windows-Automation Plugin Settings ==

The Windows-Automation plugin extends the GUI-browser's capabilities to support recording, replay and testing of GUI applications via the Windows-Automation technology.

This settings dialog is only shown/enabled if the plugin is loaded and licensed.
----
Back to [[Online Documentation]]

[[Category: Settings]]