expecco Wiki (Version 25.x) - Benutzerbeiträge [de]

Release Notes 25.x

2025-11-04T14:15:39Z

Alkurz: /* Release 25.2 */

See also: [[Release Notes 26.x]] 
See also: [[Release Notes 24.x]]
 

== Release 25.2 ==
*Improvement: Inspector shows XML Dom if it starts with '<' and ends with '>' and is parsable without error.
*Improvement: Handles very long index-lists (eg. 100k) more graceful
*Improvement: Bundled python3 installer updated to version 3.13.7
*Feature: groovy version 5.0.0 (needed for Java 25 and later)
*Fix: (Windows) reading the linkInfo of a link file to a wide-char file returned wrong (non-wide) info
*Settings: Treat the test result "Pass (Warning)" as "Pass' ([[Settings_DebuggerSettings/en#Treat_test_result_"Pass_(Warning)"_as_"Pass"|Settings: DebuggerSettings]])

== Release 25.1 ==
*Improvement: additional "Info" tab in inspector views
*Improvement: less memory usage in the activity log
*Improvement: better error messages and more links to settings from the activity log's error message
*Improvement: additional units and conversions in the [[PhysicalValues/en|physical values framework]]
*Improvement: more precision in the [[Numeric_Limits/en#Higher_Precision_Numbers|high precision trigonometric and math functions]]
*Improvement: WindowsAutomation: Plugin Update to FlaUI 5
*Improvement: Mobile Testing: Better Device Lock/Unlock Support
*Improvement: StandardLibrary: "File [ *CSV ]" blocks got an additional "characterEncoding" pin (useful for reading/writing e.g. utf-8 encoded CSV files)
*Improvement: ExcelLib: better documentation. Now requires the openpyxl package version >= 3.1.5.
*Improvement: better model language editor (translate and fetch-strings functions)
*Improvement: ODBCLibrary: improved compatibility with different database vendors (supports the CedarDB database)
*Feature: translate and spell check in the workspace window
*Feature: EditLock of suites loaded from expeccoALM / AIDYMO
*Feature: Start Test in expeccoALM / AIDYMO (via expecco)
*Feature: new library containing expeccoALM control actions (those from the AIDYMO menu)
*Fix: the version diff viewer (did not correctly copy changed attachment files)

Settings DebuggerSettings/en

2025-11-04T14:10:41Z

Alkurz: /* Debug Pin and Field Value Types */

== Debugger Settings ==
These are found in "''Settings''" - "''Execution''" - "''Debugging''".

=== Overview ===

These settings control if a debugger is to be shown when
errors, exceptions and breakpoints are encountered.
For free running tests (and also, if expecco is executed under the control of
another QM master), these flags should be off. In that case, breakpoints are
ignored and errors/exceptions lead to the corresponding activity/testcase
to fail.

However, during test development, the debugger is a very useful tool which
helps a lot in finding errors inside the testsuite itself.
You will probably want to enable the debugger then.

Notice, that the individual block test/demo execution offers two run buttons,
one using the settings as set in the expecco settings (i.e. the same that will
be active when the suite is executed as a whole),
and another (with a little bug in its icon), which enables debugging,
no matter what was specified in the settings.

During test development, you will usually want to use that debug-run.

=== Allow Invalid Pin and Field Value Types ===
Controls if at execution time, generated output pin values are consistent with the pin's datatype.
By default, this is not checked (i.e. allowed) and expecco "trusts" the code inside elementary blocks.
This can be disabled during test development and enabled for test execution
(it will slow down the execution a little bit)

=== Allow Empty Compound Activities (no Steps) ===
Controls if empty compound actions (i.e. unimplemented) are reported as an error.

=== Check for Empty Baskets when Compound Finished ===
If on, all input-pin baskets of the inner steps of a compound action's network are
checked for being empty, when a compound action is finished.
This ensures, that no missing trigger / missing data prevents other values from being processed.

=== Debug Pin and Field Value Types ===
Similar to the above "Allow Invalid Pin and Field Value Types" (which will lead to an Error exception),
enable this to have a debugger opened when the situation arises.

=== Treat test result "Pass (Warning)" as "Pass" ===

(New in 25.2) Since version 25.1, test cases that contain a warning are marked with the status “Pass (Warning)” and displayed with a yellow check mark.

This behavior can be disabled using this flag. The test result will then be “Pass” again.

=== Freeze Values are Immutable ===
(New in 18.1) Enable this (now the default) to make freeze value collections (especially strings and arrays)
immutable. If passed to tother steps, which try to modify the contents, an error will be reported.
Typically this happens, when a frozen String or Array is passed to an "ElementAt:Put" block,
or the string is modified inside a user written elementary block.
If your old test suite does actually depend on a mutable freeze value (which is unlikely, bad style and should be punished),
disable this feature in the settings.

=== Enable Halt Messages ===
By placing a "<CODE>halt()</CODE>" call into your code, explicit (programmed) breakpoints can be added
to your elementary code. Typically, this is a statement like "<CODE>this.halt()</CODE>" or simply "<CODE>halt()</CODE>"
in JavaScript, or "<CODE>self halt</CODE>" in Smalltalk code.
This flag controls if a debugger is opened when such a program breakpoint is reached.
For debugging, these halts can be put into elementary code, where a debugger is opened
for single stepping or to look at the activities' local variables. For real test execution,
halts should be disabled.
The default is to ignore halts.


=== Debug all Exceptions ===
Controls if a debugger should be opened for all exceptions;
this includes internal notifications, such as inconclusive, success and failure notifications.
Also, this affects the behavior for non-coded elementary actions.
With this flag on, executions behave the same as if started with the
"Debug-Run"-button: [[Datei:RunWithDebugger.png]]

=== Debug Activity Code ===
Controls if a debugger is opened for errors/exceptions which happen while
an activities' elementary code is being executed.
This only applies to user-coded elementary actions (i.e. those with Smalltalk or JavaScript code).
No debugger is opened for errors in remote procedure calls.
Also, no debugger is opened if the exception is handled or ignored by the current activity.

=== Debug Handled Exceptions in Activity Code ===
Controls if a debugger is opened for errors/exceptions which happen while
an activities' elementary code is being executed.
This only applies to user-coded actions (i.e. those with Smalltalk or JavaScript code).
No debugger is opened for errors in remote procedure calls.

=== Debug Pin and Field Value Types ===
Controls if a debugger is opened for invalid typed values of pins and field values. If off, an error is reported and the action is finished (unless the exception is handled).

=== Debug Expecco ===
Controls if a debugger is opened for errors/exceptions which happen inside
expecco itself (i.e. not related to user-written activity code or test execution).
In the best of all worlds, there are no such events, but well...
This should normally only be turned on by the expecco development team.

=== Suppress DialogBoxes for Warnings from alert() and warn: ===
If checked, no such dialog boxes are opened
Such code is often left in elementary code, during debugging
of the test suite or while debveloping.
For a test run you may temporarily disable them,
in case your boss wants to see a quick demo run.

=== Suspend new Actions while a Debugger is Open ===
If checked (which is the default), new activities are blocked from being executed
in parallel, whenever a debugger is already open.
This prevents the popping of many debuggers, if there is an error (or an explicit halt)
in a step's activity, which is triggered multiple times. Especially, if it is triggered
by incoming streamed values.

You should only uncheck this, if you are about to debug producer/consumer scenarios,
in which you want to single step through multiple activities in parallel.

[[Category:Settings]]

QT Testing

2025-11-03T08:35:55Z

Alkurz: /* Windows */

'''Deutsche Version''' | [[ QT Testing/en | English Version ]]

==Vorbedingungen==
===Qt-Download===
https://www.qt.io/download

===Unterstützte Versionen===
Expecco unterstützt das Testen von Qt-Applikationen unter Windows und Linux, Qt Quick/QML-Anwendungen ab der '''Qt Version 5'''.

Für die verschiedenen Qt-Versionen, Betriebssysteme, Entwicklungsumgebungen (VisualStudio, ...) und Rechnerarchitekturen (32/64 bit) stellen wir eigens erzeugte Bibliotheken (dll, so) zur Verfügung. Einige davon werden standardmäßig mit expecco ausgeliefert. Für andere Versionen erzeugen wir die Bibliothek auf Anfrage.

Eine Übersicht über die ausgelieferten Bibliotheken und ihren Versionsstand finden sie [[#ExpeccoTestService-Bibliothek: Auslieferung in Expecco-Versionen|hier]].

==Testen von Qt-Programmen==

===Testvorbereitungen===

====Einbinden der expeccoTestService-Bibliothek====

Um mit expecco ein Qt-Programm zu testen, wird in das zu testenden Programms die von uns ausgelieferte Bibliothek ''expeccoTestService.[dll/so]'' eingebunden. Dies erfolgt über ein Batch- bzw. Shell-Skript ohne Eingriff in den Sourcecode des zu testenden Programms. Diese DLL übernimmt die Kommunikation zwischen dem Qt-Program und expecco über eine Socketverbindung.

Im Batch- bzw. Shell-Skript können Sie auch das Logging für die expeccoTestService-Bibliothek aktivieren.

Eine Anleitung für das jeweilige Betriebssystem des Testrechners finden Sie hier:
* [[Qt Inject Windows#Inject expeccoTestService-Library|Qt Inject für Windows]]
* [[Qt Inject Linux#Inject expeccoTestService-Library|Qt Inject für Linux / macOS]].

Alternativ kann der Aufruf der ExpeccoTestService-Bibliothek auch in den Sourcecode der zu testenden Applikation eingefügt werden ([[Qt Inject Windows#Insert into Source Code (alternative)|Beschreibung]]).

====Startparameter====

Die ExpeccoTestService-Bibliothek kann über Umgebungsvariablen eingestellt werden:
* Log-Level: <code>ETS_QT_LOG_LEVEL</code> 
: <code>0</code> keine Logausgaben (Standardwert)
: vor expecco-Version 24.1: <code>2</code>: Debug-Logausgaben
: ab expecco-Version 24.1: <code>2</code> or <code>DEBUG</code> (Debug-Logausgaben), <code>3</code> or <code>INFO</code> (Info-Logausgaben), <code>4</code> or <code>WARN</code> (Warnungen und Fehler)

* Log-File: <code>ETS_QT_LOG_FILE</code> (Standardwert: c:\Windows\temp\etsQt.log bzw. /tmp/etsQt.log)
* Server-Port: <code>ETS_QT_PORT_NUMBER</code> (Standardwert: 8866)
* Timeout Vorschau im ms (nur Qt Quick): <code>ETS_TIMEOUT_QUICK_IMAGE</code> (Standardwert: 200)

====Benötigte Qt-Bibliotheken zur Laufzeit====

Die ExpeccoTestService-Bibliothek ist abhängig von folgenden Qt-Bibliotheken:
* Qt5Core
* Qt5Gui
* Qt5Network
* Qt5Qml
* Qt5Quick (V2 mit Qt Quick-Integration (expecco 21.2))
* Qt5QmlModel (V2 mit Qt Quick-Integration (expecco 21.2))
* Qt5Widgets

===Verbinden mit expecco GUI Browser===

Mit dem GUI Browser kann eine Verbindung zum zu testenden Programm aufgebaut werden:

<code>Verbinden</code> - <code>Qt</code>

Im nachfolgenden Dialog die Netzwerkadresse des Rechners, auf dem die Applikation läuft eingeben sowie den Port für die Verbindung (Standardmäßig 8866)

Anleitung [[Expecco GUI Tests_Extension Reference|GUI Browser]].

==Qt Quick-/QML-Programme==

Qt Quick-/QML-Anwendungen können ab expecco 21.2 mit der expecco QtLibrary getestet werden.

Hierfür wird eine neue ExpeccoTextService-Bibliothek mit dem Namenszusatz V2 ausgeliefert. Die Bibliothek ist von zusätzlichen Qt-Bibliotheken abhängig (siehe [[#Benötigte Qt-Bibliotheken zur Laufzeit|Benötigte Qt-Bibliotheken zur Laufzeit]]).

{| class="wikitable"
| '''Nur expecco 21.2''' Es wird nur eine ExpeccoTextService-Bibliothek ausgeliefert, die aber bereits Qt Quick-/QML-Support bietet. Erst ab Version 22.1 werden zwei separate Bibliotheken bereitsgestellt.
|-
|}

===Qt Quick/QML-Aktionen===

Für den Test von Qt Quick-/QML-Programmen können fast alle Aktionen der QtLibrary verwendet werden, die für das Testen von Qt-Programmen auf Basis von QWidget / QApplication definiert sind.

QWidget-Aktionen sind dabei für Qt Quick-Elemente, die sich von QQuickItem ableiten, anwendbar.
QQuickItemView-Aktionen sind für die Listen-Elemente von Qt Quick geeignet.

Die unterschiedliche Behandlung kapselt der ExpeccoTestService. Die Aktion und die Eingangs- und Ausgangspins bleiben somit für beide Qt-Technologien gleich.

Die Aktionen, die auch für Tests von Qt Quick-/QML-Programmen geeignet sind, sind mit dem Etikett / Tag <code>qt-quick</code> versehen. Die Aktionen können dadurch mit einer konfigurierbaren Farbe dargestellt werden ([[Settings TagColorSettings/en|Extras - Einstellungen - Look & Feel - Farben per Etikett (Tag)]]).

===Qt Quick-/QML-Besonderheiten===

====Steuerung über Eigenschaften / Properties====

Basis aller Qt Quick-/QML-Oberflächenelemente ist die Klasse QQuickItem. Über Properties / Eigenschaften können in ihr die meisten Eigenschaften eingestellt werden. Von QQuickItem gibt es eine Vielzahl von Ableitungen. Expecco stellt dafür keine speziellen Bausteine zur Verfügung, die Elemente sind aber über ihre Eigenschaften steuerbar.

{| class="wikitable"
! Qt Quick-Element !! Eigenschaft !! Kommentar
|-
| Tumbler || currentIndex ||
|-
| Switch|| checked || Geeignete Aktionen: <code>QCheckButton::GetState</code> <code>QCheckButton::SetState = %2</code>
|-
|colspan="3"| wird fortgesetzt
|-
|}

====Aktionen für selektiertes Element====
Die Anzeige von Aktionen für GUI-Elemente im GUI-Browser ist nicht vollständig, da Qt Quick/QML nicht für jeden Oberflächenelement vordefinierte Elemente hat.

====Noch nicht implementiert====
* TreeView
* Menu
* Selektion von Zellen - bisher kann nur eine Zeile selektiert werden

==Bekannte Probleme==

===XPath-Implementierung===

Mit XPath kann auf Übereinstimmung von Namen oder Index der Elemente gesucht werden. Filterung nach Namensteilen (Anfang, Ende, Mitte) wird derzeit nicht unterstützt.

===QApplication::ShortCutEvent===

Aufgrund von internen Änderungen in Qt Version 5 funktioniert der Baustein nicht mehr. Ein Workaround besteht darin, die Tastenereignisse separat zu senden, wie im Beispiel im Reiter Test/Demo der Aktion gezeigt.

==ExpeccoTestService-Bibliothek: Auslieferung in Expecco-Versionen==

Aufstellung der Expecco-Versionen mit der letzten Aktualisierung der ''ExpeccoTestService''-Bibliothek für die verschieden Qt-Versionen und Buildsysteme.

Weitere Versionen können auf Anfrage geliefert werden.

===Windows===
{| class="wikitable"
! Expecco-Version !! Qt Version !! Architektur !! Build-System !! Verzeichnis !! Kommentar
|-

|rowspan="4" valign="top"|2026-1
|| 6.8.3 || x64 || vs2022 || vs2022_x64_Qt6.8.3 || rowspan="4" valign="top"|
|-
|| 6.2.4 || x64 || vs2019 || vs2019_x64_Qt6.2.4 ||
|-
|| 5.15.0 || x64 || vs2022 || vs2022_x64_Qt5.15.0
|-
|| 5.15.0 || x64 || vs2019 || vs2019_x64_Qt5.15.0
|-

|rowspan="3" valign="top"|2024-1
|| 6.2.4 || x64 || vs2019 || vs2019_x64_Qt6.2.4 || rowspan="3" valign="top"|
* Protokollierung mit Einstellungen <code>DEBUG</code>, <code>INFO</code> und <code>WARN</code>
* Mausereignis "Move" wurde überarbeitet (QT:OS-MouseEvent...)
|-
|| 5.15.0 || x64 || vs2022 || vs2022_x64_Qt5.15.0
|-
|| 5.15.0 || x64 || vs2019 || vs2019_x64_Qt5.15.0
|-

|rowspan="3" valign="top"|2023-2
|| 6.2.4 || x64 || vs2019 || vs2019_x64_Qt6.2.4 || rowspan="3" valign="top"|
* Neuer Baustein ''QButton::Click'': Direkter Klick, nicht an Thread delegiert
|-
|| 5.15.0 || x64 || vs2022 || vs2022_x64_Qt5.15.0
|-
|| 5.15.0 || x64 || vs2019 || vs2019_x64_Qt5.15.0
|-

|rowspan="2" valign="top"|2023-1
|| 6.2.4 || x64 || vs2019 || vs2019_x64_Qt6.2.4 || rowspan="2" valign="top"|
* Anbindung von Qt 6-Programmen
* Bugfix QtQuick: MouseClick
|-
|| 5.15.0 || x64 || vs2019 || vs2019_x64_Qt5.15.0
|-

|rowspan="3" valign="top"|2022-2
|| 5.15.0 || x64 || vs2019 || vs2019_x64_Qt5.15.0 || rowspan="3" valign="top"|
* Ausgabe von QT-Version und Buildparameter in Log-Datei bei DLL-Start
|-
|| 5.15.0 || x86 || vs2019 || vs2019_Qt5.15.0
|-
|| 5.14.2 || x86 || vs2017 || vs2017_Qt5.14.2
|-

|rowspan="3" valign="top"|2022-1
|| 5.15.0 || x64 || vs2019 || vs2019_x64_Qt5.15.0 || rowspan="3" valign="top"|
* Separate DLLs für QtQuick/QWidget und nur QWidget
* Feature: Auslesen Vertikaler Header bei Tabellen
* Feature: Screenshot bei Fehler
|-
|| 5.15.0 || x86 || vs2019 || vs2019_Qt5.15.0
|-
|| 5.14.2 || x86 || vs2017 || vs2017_Qt5.14.2
|-

|rowspan="4" valign="top"|2021-2
|| 5.15.0 || x64 || vs2019 || vs2019_x64_Qt5.15.0 || rowspan="4" valign="top"| QtQuick / QML
|-
|| 5.15.0 || x86 || vs2019 || vs2019_Qt5.15.0
|-
|| 5.9.3 || x64 || vs2015 || vs2015_x64_Qt5.9.3
|-
|| 5.9.1 || x64 || vs2015 || vs2015_x64_Qt5.9.1
|-

|rowspan="1" valign="top"|2021-1
|| 5.9.3 || x86 || vs2015 || vs2015_x86_Qt5.9.3 ||
|-

|rowspan="1" valign="top"|2020-1
|| 5.8.0 || x86 || vs2013 || vs2013_Qt5.8.0 ||
|-

|rowspan="2" valign="top"|2019-2
|| 5.9.3 || x64 || vs2013 || vs2013_x64_Qt5.9.3 ||
|-
|| 5.9.1 || x64 || vs2013 || vs2013_x64_Qt5.9.1 ||
|-

|rowspan="1" valign="top"|2018-2
|| 5.4.2 || x86 || vs2010 || vs2010_Qt5.4.2 ||
|-

|}

===Linux / macOS===

{| class="wikitable"
! Expecco-Version !! Qt Version !! Architektur !! Build-System !! Verzeichnis !! Kommentar
|-

|rowspan="2" valign="top"|2023-2
| valign="top"| 6.2.4 || valign="top"| x64 || valign="top"| gcc || valign="top"| gcc_x64_Qt6.2.4 ||rowspan="2" valign="top"|
* Neuer Baustein QButton::Click: Direkter Klick, nicht an Thread delegiert
|-
| valign="top"| 5.15.0 || valign="top"| x64 || valign="top"| gcc || valign="top"| gcc_x64_Qt5.15.0
|-

|rowspan="2" valign="top"|2023-1
| valign="top"| 6.2.4 || valign="top"| x64 || valign="top"| gcc || valign="top"| gcc_x64_Qt6.2.4 ||rowspan="2" valign="top"|
* Anbindung von Qt 6-Programmen
* Bugfix QtQuick: MouseClick
|-
| valign="top"| 5.15.0 || valign="top"| x64 || valign="top"| gcc || valign="top"| gcc_x64_Qt5.15.0
|-

|rowspan="1" valign="top"|2022-2
| valign="top"| 5.15.0 || valign="top"| x64 || valign="top"| gcc || valign="top"| gcc_x64_Qt5.15.0 ||
* Ausgabe von QT-Version und Buildparameter in Log-Datei bei DLL-Start
|-

|rowspan="1" valign="top"|2022-1
| valign="top"| 5.15.0 || valign="top"| x64 || valign="top"| gcc || valign="top"| gcc_x64_Qt5.15.0 ||
* Separate DLLs für QtQuick/QWidget und nur QWidget
* Feature: Auslesen Vertikaler Header bei Tabellen
* Feature: Screenshot bei Fehler
|-

|rowspan="1" valign="top"|2021-2
|| 5.15.0 || x64 || gcc || gcc_x64_Qt5.15.0 || QtQuick / QML
|-

|rowspan="2" valign="top"|2021-1
|| 5.12.2 || arm32 || gcc || gcc_arm32_Qt.12.2 ||
|-
|| 5.9.5 || x64 || gcc || gcc_x64_Qt5.9.5 ||
|-

|rowspan="1" valign="top"|2020-2
|| 5.9.1 || x64 || gcc || gcc_x64_Qt5.9.1 ||
|-

|rowspan="1" valign="top"|2020-1
|| 5.12.3 || x64 || gcc || gcc_x64_Qt5.12.3 ||
|-

|}

----
Zurück zu [[Qt Plugin Reference]]

QT Testing/en

2025-11-03T08:35:28Z

Alkurz: /* Windows */

[[QT_Testing|Deutsche Version]] | '''English Version'''

==Pre-requisites==
===Qt download===
https://www.qt.io/download

===Supported Versions===
Expecco supports testing of Qt applications on Windows and Linux, Qt Quick/QML applications from '''Qt version 5''''.

For the different Qt versions, operating systems, development environments (VisualStudio, ...) and computer architectures (32/64 bit) we provide specially generated libraries (dll, so). Some of them are delivered with expecco by default. For other versions we generate the library on request.

An overview of the delivered libraries and their version status can be found [[#ExpeccoTestService Library: Delivery in Expecco Versions|here]].

==Testing Qt Programs==

===Test Preparations===

====Integrating the ExpeccoTestService Library====

To test a Qt program with expecco, the library ''expeccoTestService.[dll/so]'' delivered by us is included in the program to be tested. This is done via a batch or shell script without intervention in the source code of the program to be tested. This DLL implements the communication between the Qt program and expecco.

You can also activate logging for the expeccoTestService library in the batch or shell script.

Instructions for the respective operating system of the test computer can be found here:
* [[Qt Inject Windows#Inject expeccoTestService-Library|Qt Inject for Windows]]
* [[Qt Inject Linux#Inject expeccoTestService-Library|Qt Inject for Linux / macOS]].

Alternatively, the ExpeccoTestService library call can be inserted into the source code of the application under test ([[Qt Inject Windows/en#Insert into Source Code (alternative)|Description]]).

====Start Parameters====

The ExpeccoTestService library can be set via environment variables:
* Log level: <code>ETS_QT_LOG_LEVEL</code> 
: <code>0</code> no logging (default value) 
: before expecco version 24.1: <code>2</code>: logging (debug) 
: from expecco version 24.1: <code>2</code> or <code>DEBUG</code> (debug), <code>3</code> or <code>INFO</code> (info), <code>4</code> or <code>WARN</code> (warnings and errors)
* Log file: <code>ETS_QT_LOG_FILE</code> (default value: c:\Windows\temp\etsQt.log or /tmp/etsQt.log).
* Server port: <code>ETS_QT_PORT_NUMBER</code> (default value: 8866).
* Timeout preview in ms (only Qt Quick): <code>ETS_TIMEOUT_QUICK_IMAGE</code> (default value: 200)

====Required Qt Libraries at Runtime====

The ExpeccoTestService library depends on the following Qt libraries:
* Qt5Core
* Qt5Gui
* Qt5Network
* Qt5Qml
* Qt5Quick (V2 with Qt Quick integration (expecco 21.2))
* Qt5QmlModel (V2 with Qt Quick integration (expecco 21.2))
* Qt5Widgets

===Connecting with Expecco GUI Browser===

The GUI Browser can be used to connect to the program under test:

<code>Connect</code> - <code>Qt</code>.

In the following dialog, enter the network address of the computer running the application and the port for the connection (8866 by default).

Manual [[Expecco GUI Tests_Extension Reference|GUI Browser]].

==Qt Quick/QML Programs==
Qt Quick/QML applications can be tested with the expecco QtLibrary starting with expecco 21.2.

For this purpose, a new ExpeccoTextService library with the name suffix V2 is delivered. The library depends on additional Qt libraries (see [[#Required Qt Libraries at Runtime|Required Qt Libraries at Runtime]])

{| class="wikitable"
| '''Only expecco 21.2''' 
Only one ExpeccoTextService library is delivered, but it already offers Qt Quick/QML support. Only from version 22.1 two separate libraries are provided.
|-
|}

===Qt Quick/QML Actions===

For testing Qt Quick/QML programs almost all actions of the QtLibrary can be used, which are defined for testing Qt programs based on QWidget / QApplication.

QWidget actions are applicable to Qt Quick items derived from QQuickItem.
QQuickItemView actions are applicable to Qt Quick list items.

The different handling is encapsulated by the ExpeccoTestService. Thus, the action and the input and output pins remain the same for both Qt technologies.

The actions, which are also suitable for tests of Qt Quick/QML programmes, are provided with the label / tag <code>qt-quick</code>. The actions can thus be displayed with a configurable colour ([[Settings TagColorSettings/en|Extras - Settings - Look & Feel - Colours per Label (Tag)]]).

===Qt Quick/QML Peculiarities===

====Control via Properties====

The basis of all Qt Quick/QML interface elements is the QQuickItem class. Most of its properties can be set via properties. There are many derivations of QQuickItem. Expecco does not provide any special building blocks for this, but the elements can be controlled via their properties.

{| class="wikitable"
! Qt Quick element !! property !! Comment
|-
| Tumbler || currentIndex ||
|-
| Switch|| checked || Suitable actions: <code>QCheckButton::GetState</code> <code>QCheckButton::SetState = %2</code>
|-
|colspan="3"| will be continued
|-
|}

====Actions for Selected Element====
The display of actions for GUI elements in the GUI browser is not complete because Qt Quick/QML does not have predefined elements for each interface element.

====Not yet implemented====
* TreeView
* Menu
* Selection of cells - so far only one row can be selected

==Qt Known Problems==

===XPath implementation===

XPath can be used to search for matching names or index of elements. Filtering by name parts (starts-with, ends-with, contains) is currently not supported.

===QApplication::ShortCutEvent===

Due to internal changes in Qt version 5, the module no longer works. A workaround is to send the key events separately, as shown in the example in the Test/Demo tab of the action.

==ExpeccoTestService Library: Delivery in Expecco Versions==

List of Expecco versions with the latest update of the ''ExpeccoTestService'' library for the different Qt versions and build systems.

Further versions can be delivered on request.

===Windows===
{| class="wikitable"
! Expecco Version !! Qt Version !! Architecture !! Build System !! Directory !! Comment
|-

|rowspan="4" valign="top"|2026-1
|| 6.8.3 || x64 || vs2022 || vs2022_x64_Qt6.8.3 || rowspan="4" valign="top"|
|-
|| 6.2.4 || x64 || vs2019 || vs2019_x64_Qt6.2.4 ||
|-
|| 5.15.0 || x64 || vs2022 || vs2022_x64_Qt5.15.0
|-
|| 5.15.0 || x64 || vs2019 || vs2019_x64_Qt5.15.0
|-

|rowspan="3" valign="top"|2024-1
|| 6.2.4 || x64 || vs2019 || vs2019_x64_Qt6.2.4 || rowspan="3" valign="top"|
* Logging with Loglevels <code>DEBUG</code>, <code>INFO</code> and <code>WARN</code>
* Mouse event Move has been revised (QT:OS-MouseEvent...)
|-
|| 5.15.0 || x64 || vs2022 || vs2022_x64_Qt5.15.0
|-
|| 5.15.0 || x64 || vs2019 || vs2019_x64_Qt5.15.0
|-

|rowspan="3" valign="top"|2023-2
|| 6.2.4 || x64 || vs2019 || vs2019_x64_Qt6.2.4 || rowspan="3" valign="top"|
* New Step ''QButton::Click'': Direct click, not delegated to thread
|-
|| 5.15.0 || x64 || vs2022 || vs2022_x64_Qt5.15.0
|-
|| 5.15.0 || x64 || vs2019 || vs2019_x64_Qt5.15.0
|-

|rowspan="2" valign="top"|2023-1
|| 6.2.4 || x64 || vs2019 || vs2019_x64_Qt6.2.4 || rowspan="2" valign="top"|
* QT6 support
* Bugfix QtQuick: MouseClick
|-
|| 5.15.0 || x64 || vs2019 || vs2019_x64_Qt5.15.0
|-

|rowspan="3" valign="top"|2022-2
|| 5.15.0 || x64 || vs2019 || vs2019_x64_Qt5.15.0 || rowspan="3" valign="top"|
* Output version and build date in etsLog at start-up
|-
|| 5.15.0 || x86 || vs2019 || vs2019_Qt5.15.0
|-
|| 5.14.2 || x86 || vs2017 || vs2017_Qt5.14.2
|-

|rowspan="3" valign="top"|2022-1
|| 5.15.0 || x64 || vs2019 || vs2019_x64_Qt5.15.0 || rowspan="3" valign="top"|
* Separate DLLs for QtQuick/QWidget and only QWidget
* Feature: Reading vertical headers for tables
* Feature: Screenshot in case of error
|-
|| 5.15.0 || x86 || vs2019 || vs2019_Qt5.15.0
|-
|| 5.14.2 || x86 || vs2017 || vs2017_Qt5.14.2
|-

|rowspan="4" valign="top"|2021-2
|| 5.15.0 || x64 || vs2019 || vs2019_x64_Qt5.15.0 || rowspan="4" valign="top"| QtQuick / QML
|-
|| 5.15.0 || x86 || vs2019 || vs2019_Qt5.15.0
|-
|| 5.9.3 || x64 || vs2015 || vs2015_x64_Qt5.9.3
|-
|| 5.9.1 || x64 || vs2015 || vs2015_x64_Qt5.9.1
|-

|rowspan="1" valign="top"|2021-1
|| 5.9.3 || x86 || vs2015 || vs2015_x86_Qt5.9.3 ||
|-

|rowspan="1" valign="top"|2020-1
|| 5.8.0 || x86 || vs2013 || vs2013_Qt5.8.0 ||
|-

|rowspan="2" valign="top"|2019-2
|| 5.9.3 || x64 || vs2013 || vs2013_x64_Qt5.9.3 ||
|-
|| 5.9.1 || x64 || vs2013 || vs2013_x64_Qt5.9.1 ||
|-

|rowspan="1" valign="top"|2018-2
|| 5.4.2 || x86 || vs2010 || vs2010_Qt5.4.2 ||
|-

|}

===Linux / macOS===
{| class="wikitable"
! Expecco Version !! Qt Version !! Architecture !! Build System !! Directory !! Comment
|-

|rowspan="2" valign="top"|2024-1
|| 6.2.4 || x64 || gcc || gcc_x64_Qt6.2.4 || rowspan="2" valign="top"|
* Logging with Loglevels <code>DEBUG</code>, <code>INFO</code> and <code>WARN</code>
|-
|| 5.15.0 || x64 || gcc || gcc_x64_Qt5.15.0
|-

|rowspan="2" valign="top"|2023-1
|| 6.2.4 || x64 || gcc || gcc_x64_Qt6.2.4 || rowspan="2" valign="top"| QT6 support
|-
|| 5.15.0 || x64 || gcc || gcc_x64_Qt5.15.0
|-

|rowspan="1" valign="top"|2022-2
| valign="top"| 5.15.0 || valign="top"| x64 || valign="top"| gcc || valign="top"| gcc_x64_Qt5.15.0 || valign="top" | Output version and build date in etsLog at start-up
|-

|rowspan="1" valign="top"|2022-1
| valign="top"| 5.15.0 || valign="top"| x64 || valign="top"| gcc || valign="top"| gcc_x64_Qt5.15.0 ||
* Separate DLLs for QtQuick/QWidget and only QWidget
* Feature: Reading vertical headers for tables
* Feature: Screenshot in case of error
|-

|rowspan="1" valign="top"|2021-2
|| 5.15.0 || x64 || gcc || gcc_x64_Qt5.15.0 || QtQuick / QML
|-

|rowspan="2" valign="top"|2021-1
|| 5.12.2 || arm32 || gcc || gcc_arm32_Qt.12.2 ||
|-
|| 5.9.5 || x64 || gcc || gcc_x64_Qt5.9.5 ||
|-

|rowspan="1" valign="top"|2020-2
|| 5.9.1 || x64 || gcc || gcc_x64_Qt5.9.1 ||
|-

|rowspan="1" valign="top"|2020-1
|| 5.12.3 || x64 || gcc || gcc_x64_Qt5.12.3 ||
|-

|}

----

Back to [[Qt Plugin Reference/en|Qt Plugin Reference]]

Release Notes 26.x

2025-11-03T08:32:55Z

Alkurz: Die Seite wurde neu angelegt: „See also: Release Notes 25.x == Release 26.2 == == Release 26.1 == *Feature: Qt-Plugin supports Qt6.8 (QT_Testing/en#ExpeccoTestService_Library%…“

See also: [[Release Notes 25.x]]
 

== Release 26.2 ==

== Release 26.1 ==
*Feature: Qt-Plugin supports Qt6.8 ([[QT_Testing/en#ExpeccoTestService_Library%3A_Delivery_in_Expecco_Versions|Delivered versions for QT and build environment]])

Release Notes 25.x

2025-11-03T08:31:08Z

Alkurz:

See also: [[Release Notes 26.x]] 
See also: [[Release Notes 24.x]]
 

== Release 25.2 ==
*Improvement: Inspector shows XML Dom if it starts with '<' and ends with '>' and is parsable without error.
*Improvement: Handles very long index-lists (eg. 100k) more graceful
*Improvement: Bundled python3 installer updated to version 3.13.7
*Feature: groovy version 5.0.0 (needed for Java 25 and later)
*Fix: (Windows) reading the linkInfo of a link file to a wide-char file returned wrong (non-wide) info

== Release 25.1 ==
*Improvement: additional "Info" tab in inspector views
*Improvement: less memory usage in the activity log
*Improvement: better error messages and more links to settings from the activity log's error message
*Improvement: additional units and conversions in the [[PhysicalValues/en|physical values framework]]
*Improvement: more precision in the [[Numeric_Limits/en#Higher_Precision_Numbers|high precision trigonometric and math functions]]
*Improvement: WindowsAutomation: Plugin Update to FlaUI 5
*Improvement: Mobile Testing: Better Device Lock/Unlock Support
*Improvement: StandardLibrary: "File [ *CSV ]" blocks got an additional "characterEncoding" pin (useful for reading/writing e.g. utf-8 encoded CSV files)
*Improvement: ExcelLib: better documentation. Now requires the openpyxl package version >= 3.1.5.
*Improvement: better model language editor (translate and fetch-strings functions)
*Improvement: ODBCLibrary: improved compatibility with different database vendors (supports the CedarDB database)
*Feature: translate and spell check in the workspace window
*Feature: EditLock of suites loaded from expeccoALM / AIDYMO
*Feature: Start Test in expeccoALM / AIDYMO (via expecco)
*Feature: new library containing expeccoALM control actions (those from the AIDYMO menu)
*Fix: the version diff viewer (did not correctly copy changed attachment files)

Release Notes 25.x

2025-11-03T08:30:35Z

Alkurz:

See also: [[Release Notes 26.x]]
See also: [[Release Notes 24.x]]
 

== Release 25.2 ==
*Improvement: Inspector shows XML Dom if it starts with '<' and ends with '>' and is parsable without error.
*Improvement: Handles very long index-lists (eg. 100k) more graceful
*Improvement: Bundled python3 installer updated to version 3.13.7
*Feature: groovy version 5.0.0 (needed for Java 25 and later)
*Fix: (Windows) reading the linkInfo of a link file to a wide-char file returned wrong (non-wide) info

== Release 25.1 ==
*Improvement: additional "Info" tab in inspector views
*Improvement: less memory usage in the activity log
*Improvement: better error messages and more links to settings from the activity log's error message
*Improvement: additional units and conversions in the [[PhysicalValues/en|physical values framework]]
*Improvement: more precision in the [[Numeric_Limits/en#Higher_Precision_Numbers|high precision trigonometric and math functions]]
*Improvement: WindowsAutomation: Plugin Update to FlaUI 5
*Improvement: Mobile Testing: Better Device Lock/Unlock Support
*Improvement: StandardLibrary: "File [ *CSV ]" blocks got an additional "characterEncoding" pin (useful for reading/writing e.g. utf-8 encoded CSV files)
*Improvement: ExcelLib: better documentation. Now requires the openpyxl package version >= 3.1.5.
*Improvement: better model language editor (translate and fetch-strings functions)
*Improvement: ODBCLibrary: improved compatibility with different database vendors (supports the CedarDB database)
*Feature: translate and spell check in the workspace window
*Feature: EditLock of suites loaded from expeccoALM / AIDYMO
*Feature: Start Test in expeccoALM / AIDYMO (via expecco)
*Feature: new library containing expeccoALM control actions (those from the AIDYMO menu)
*Fix: the version diff viewer (did not correctly copy changed attachment files)

Release Notes 25.x

2025-11-03T08:28:22Z

Alkurz: /* Release 25.2 */

See also: [[Release Notes 24.x]]
 

== Release 25.2 ==
*Improvement: Inspector shows XML Dom if it starts with '<' and ends with '>' and is parsable without error.
*Improvement: Handles very long index-lists (eg. 100k) more graceful
*Improvement: Bundled python3 installer updated to version 3.13.7
*Feature: groovy version 5.0.0 (needed for Java 25 and later)
*Fix: (Windows) reading the linkInfo of a link file to a wide-char file returned wrong (non-wide) info

== Release 25.1 ==
*Improvement: additional "Info" tab in inspector views
*Improvement: less memory usage in the activity log
*Improvement: better error messages and more links to settings from the activity log's error message
*Improvement: additional units and conversions in the [[PhysicalValues/en|physical values framework]]
*Improvement: more precision in the [[Numeric_Limits/en#Higher_Precision_Numbers|high precision trigonometric and math functions]]
*Improvement: WindowsAutomation: Plugin Update to FlaUI 5
*Improvement: Mobile Testing: Better Device Lock/Unlock Support
*Improvement: StandardLibrary: "File [ *CSV ]" blocks got an additional "characterEncoding" pin (useful for reading/writing e.g. utf-8 encoded CSV files)
*Improvement: ExcelLib: better documentation. Now requires the openpyxl package version >= 3.1.5.
*Improvement: better model language editor (translate and fetch-strings functions)
*Improvement: ODBCLibrary: improved compatibility with different database vendors (supports the CedarDB database)
*Feature: translate and spell check in the workspace window
*Feature: EditLock of suites loaded from expeccoALM / AIDYMO
*Feature: Start Test in expeccoALM / AIDYMO (via expecco)
*Feature: new library containing expeccoALM control actions (those from the AIDYMO menu)
*Fix: the version diff viewer (did not correctly copy changed attachment files)

QT Testing

2025-10-23T10:53:44Z

Alkurz: /* Windows */

'''Deutsche Version''' | [[ QT Testing/en | English Version ]]

==Vorbedingungen==
===Qt-Download===
https://www.qt.io/download

===Unterstützte Versionen===
Expecco unterstützt das Testen von Qt-Applikationen unter Windows und Linux, Qt Quick/QML-Anwendungen ab der '''Qt Version 5'''.

Für die verschiedenen Qt-Versionen, Betriebssysteme, Entwicklungsumgebungen (VisualStudio, ...) und Rechnerarchitekturen (32/64 bit) stellen wir eigens erzeugte Bibliotheken (dll, so) zur Verfügung. Einige davon werden standardmäßig mit expecco ausgeliefert. Für andere Versionen erzeugen wir die Bibliothek auf Anfrage.

Eine Übersicht über die ausgelieferten Bibliotheken und ihren Versionsstand finden sie [[#ExpeccoTestService-Bibliothek: Auslieferung in Expecco-Versionen|hier]].

==Testen von Qt-Programmen==

===Testvorbereitungen===

====Einbinden der expeccoTestService-Bibliothek====

Um mit expecco ein Qt-Programm zu testen, wird in das zu testenden Programms die von uns ausgelieferte Bibliothek ''expeccoTestService.[dll/so]'' eingebunden. Dies erfolgt über ein Batch- bzw. Shell-Skript ohne Eingriff in den Sourcecode des zu testenden Programms. Diese DLL übernimmt die Kommunikation zwischen dem Qt-Program und expecco über eine Socketverbindung.

Im Batch- bzw. Shell-Skript können Sie auch das Logging für die expeccoTestService-Bibliothek aktivieren.

Eine Anleitung für das jeweilige Betriebssystem des Testrechners finden Sie hier:
* [[Qt Inject Windows#Inject expeccoTestService-Library|Qt Inject für Windows]]
* [[Qt Inject Linux#Inject expeccoTestService-Library|Qt Inject für Linux / macOS]].

Alternativ kann der Aufruf der ExpeccoTestService-Bibliothek auch in den Sourcecode der zu testenden Applikation eingefügt werden ([[Qt Inject Windows#Insert into Source Code (alternative)|Beschreibung]]).

====Startparameter====

Die ExpeccoTestService-Bibliothek kann über Umgebungsvariablen eingestellt werden:
* Log-Level: <code>ETS_QT_LOG_LEVEL</code> 
: <code>0</code> keine Logausgaben (Standardwert)
: vor expecco-Version 24.1: <code>2</code>: Debug-Logausgaben
: ab expecco-Version 24.1: <code>2</code> or <code>DEBUG</code> (Debug-Logausgaben), <code>3</code> or <code>INFO</code> (Info-Logausgaben), <code>4</code> or <code>WARN</code> (Warnungen und Fehler)

* Log-File: <code>ETS_QT_LOG_FILE</code> (Standardwert: c:\Windows\temp\etsQt.log bzw. /tmp/etsQt.log)
* Server-Port: <code>ETS_QT_PORT_NUMBER</code> (Standardwert: 8866)
* Timeout Vorschau im ms (nur Qt Quick): <code>ETS_TIMEOUT_QUICK_IMAGE</code> (Standardwert: 200)

====Benötigte Qt-Bibliotheken zur Laufzeit====

Die ExpeccoTestService-Bibliothek ist abhängig von folgenden Qt-Bibliotheken:
* Qt5Core
* Qt5Gui
* Qt5Network
* Qt5Qml
* Qt5Quick (V2 mit Qt Quick-Integration (expecco 21.2))
* Qt5QmlModel (V2 mit Qt Quick-Integration (expecco 21.2))
* Qt5Widgets

===Verbinden mit expecco GUI Browser===

Mit dem GUI Browser kann eine Verbindung zum zu testenden Programm aufgebaut werden:

<code>Verbinden</code> - <code>Qt</code>

Im nachfolgenden Dialog die Netzwerkadresse des Rechners, auf dem die Applikation läuft eingeben sowie den Port für die Verbindung (Standardmäßig 8866)

Anleitung [[Expecco GUI Tests_Extension Reference|GUI Browser]].

==Qt Quick-/QML-Programme==

Qt Quick-/QML-Anwendungen können ab expecco 21.2 mit der expecco QtLibrary getestet werden.

Hierfür wird eine neue ExpeccoTextService-Bibliothek mit dem Namenszusatz V2 ausgeliefert. Die Bibliothek ist von zusätzlichen Qt-Bibliotheken abhängig (siehe [[#Benötigte Qt-Bibliotheken zur Laufzeit|Benötigte Qt-Bibliotheken zur Laufzeit]]).

{| class="wikitable"
| '''Nur expecco 21.2''' Es wird nur eine ExpeccoTextService-Bibliothek ausgeliefert, die aber bereits Qt Quick-/QML-Support bietet. Erst ab Version 22.1 werden zwei separate Bibliotheken bereitsgestellt.
|-
|}

===Qt Quick/QML-Aktionen===

Für den Test von Qt Quick-/QML-Programmen können fast alle Aktionen der QtLibrary verwendet werden, die für das Testen von Qt-Programmen auf Basis von QWidget / QApplication definiert sind.

QWidget-Aktionen sind dabei für Qt Quick-Elemente, die sich von QQuickItem ableiten, anwendbar.
QQuickItemView-Aktionen sind für die Listen-Elemente von Qt Quick geeignet.

Die unterschiedliche Behandlung kapselt der ExpeccoTestService. Die Aktion und die Eingangs- und Ausgangspins bleiben somit für beide Qt-Technologien gleich.

Die Aktionen, die auch für Tests von Qt Quick-/QML-Programmen geeignet sind, sind mit dem Etikett / Tag <code>qt-quick</code> versehen. Die Aktionen können dadurch mit einer konfigurierbaren Farbe dargestellt werden ([[Settings TagColorSettings/en|Extras - Einstellungen - Look & Feel - Farben per Etikett (Tag)]]).

===Qt Quick-/QML-Besonderheiten===

====Steuerung über Eigenschaften / Properties====

Basis aller Qt Quick-/QML-Oberflächenelemente ist die Klasse QQuickItem. Über Properties / Eigenschaften können in ihr die meisten Eigenschaften eingestellt werden. Von QQuickItem gibt es eine Vielzahl von Ableitungen. Expecco stellt dafür keine speziellen Bausteine zur Verfügung, die Elemente sind aber über ihre Eigenschaften steuerbar.

{| class="wikitable"
! Qt Quick-Element !! Eigenschaft !! Kommentar
|-
| Tumbler || currentIndex ||
|-
| Switch|| checked || Geeignete Aktionen: <code>QCheckButton::GetState</code> <code>QCheckButton::SetState = %2</code>
|-
|colspan="3"| wird fortgesetzt
|-
|}

====Aktionen für selektiertes Element====
Die Anzeige von Aktionen für GUI-Elemente im GUI-Browser ist nicht vollständig, da Qt Quick/QML nicht für jeden Oberflächenelement vordefinierte Elemente hat.

====Noch nicht implementiert====
* TreeView
* Menu
* Selektion von Zellen - bisher kann nur eine Zeile selektiert werden

==Bekannte Probleme==

===XPath-Implementierung===

Mit XPath kann auf Übereinstimmung von Namen oder Index der Elemente gesucht werden. Filterung nach Namensteilen (Anfang, Ende, Mitte) wird derzeit nicht unterstützt.

===QApplication::ShortCutEvent===

Aufgrund von internen Änderungen in Qt Version 5 funktioniert der Baustein nicht mehr. Ein Workaround besteht darin, die Tastenereignisse separat zu senden, wie im Beispiel im Reiter Test/Demo der Aktion gezeigt.

==ExpeccoTestService-Bibliothek: Auslieferung in Expecco-Versionen==

Aufstellung der Expecco-Versionen mit der letzten Aktualisierung der ''ExpeccoTestService''-Bibliothek für die verschieden Qt-Versionen und Buildsysteme.

Weitere Versionen können auf Anfrage geliefert werden.

===Windows===
{| class="wikitable"
! Expecco-Version !! Qt Version !! Architektur !! Build-System !! Verzeichnis !! Kommentar
|-

|rowspan="4" valign="top"|2025-2
|| 6.8.3 || x64 || vs2022 || vs2022_x64_Qt6.8.3 || rowspan="4" valign="top"|
|-
|| 6.2.4 || x64 || vs2019 || vs2019_x64_Qt6.2.4 ||
|-
|| 5.15.0 || x64 || vs2022 || vs2022_x64_Qt5.15.0
|-
|| 5.15.0 || x64 || vs2019 || vs2019_x64_Qt5.15.0
|-

|rowspan="3" valign="top"|2024-1
|| 6.2.4 || x64 || vs2019 || vs2019_x64_Qt6.2.4 || rowspan="3" valign="top"|
* Protokollierung mit Einstellungen <code>DEBUG</code>, <code>INFO</code> und <code>WARN</code>
* Mausereignis "Move" wurde überarbeitet (QT:OS-MouseEvent...)
|-
|| 5.15.0 || x64 || vs2022 || vs2022_x64_Qt5.15.0
|-
|| 5.15.0 || x64 || vs2019 || vs2019_x64_Qt5.15.0
|-

|rowspan="3" valign="top"|2023-2
|| 6.2.4 || x64 || vs2019 || vs2019_x64_Qt6.2.4 || rowspan="3" valign="top"|
* Neuer Baustein ''QButton::Click'': Direkter Klick, nicht an Thread delegiert
|-
|| 5.15.0 || x64 || vs2022 || vs2022_x64_Qt5.15.0
|-
|| 5.15.0 || x64 || vs2019 || vs2019_x64_Qt5.15.0
|-

|rowspan="2" valign="top"|2023-1
|| 6.2.4 || x64 || vs2019 || vs2019_x64_Qt6.2.4 || rowspan="2" valign="top"|
* Anbindung von Qt 6-Programmen
* Bugfix QtQuick: MouseClick
|-
|| 5.15.0 || x64 || vs2019 || vs2019_x64_Qt5.15.0
|-

|rowspan="3" valign="top"|2022-2
|| 5.15.0 || x64 || vs2019 || vs2019_x64_Qt5.15.0 || rowspan="3" valign="top"|
* Ausgabe von QT-Version und Buildparameter in Log-Datei bei DLL-Start
|-
|| 5.15.0 || x86 || vs2019 || vs2019_Qt5.15.0
|-
|| 5.14.2 || x86 || vs2017 || vs2017_Qt5.14.2
|-

|rowspan="3" valign="top"|2022-1
|| 5.15.0 || x64 || vs2019 || vs2019_x64_Qt5.15.0 || rowspan="3" valign="top"|
* Separate DLLs für QtQuick/QWidget und nur QWidget
* Feature: Auslesen Vertikaler Header bei Tabellen
* Feature: Screenshot bei Fehler
|-
|| 5.15.0 || x86 || vs2019 || vs2019_Qt5.15.0
|-
|| 5.14.2 || x86 || vs2017 || vs2017_Qt5.14.2
|-

|rowspan="4" valign="top"|2021-2
|| 5.15.0 || x64 || vs2019 || vs2019_x64_Qt5.15.0 || rowspan="4" valign="top"| QtQuick / QML
|-
|| 5.15.0 || x86 || vs2019 || vs2019_Qt5.15.0
|-
|| 5.9.3 || x64 || vs2015 || vs2015_x64_Qt5.9.3
|-
|| 5.9.1 || x64 || vs2015 || vs2015_x64_Qt5.9.1
|-

|rowspan="1" valign="top"|2021-1
|| 5.9.3 || x86 || vs2015 || vs2015_x86_Qt5.9.3 ||
|-

|rowspan="1" valign="top"|2020-1
|| 5.8.0 || x86 || vs2013 || vs2013_Qt5.8.0 ||
|-

|rowspan="2" valign="top"|2019-2
|| 5.9.3 || x64 || vs2013 || vs2013_x64_Qt5.9.3 ||
|-
|| 5.9.1 || x64 || vs2013 || vs2013_x64_Qt5.9.1 ||
|-

|rowspan="1" valign="top"|2018-2
|| 5.4.2 || x86 || vs2010 || vs2010_Qt5.4.2 ||
|-

|}

===Linux / macOS===

{| class="wikitable"
! Expecco-Version !! Qt Version !! Architektur !! Build-System !! Verzeichnis !! Kommentar
|-

|rowspan="2" valign="top"|2023-2
| valign="top"| 6.2.4 || valign="top"| x64 || valign="top"| gcc || valign="top"| gcc_x64_Qt6.2.4 ||rowspan="2" valign="top"|
* Neuer Baustein QButton::Click: Direkter Klick, nicht an Thread delegiert
|-
| valign="top"| 5.15.0 || valign="top"| x64 || valign="top"| gcc || valign="top"| gcc_x64_Qt5.15.0
|-

|rowspan="2" valign="top"|2023-1
| valign="top"| 6.2.4 || valign="top"| x64 || valign="top"| gcc || valign="top"| gcc_x64_Qt6.2.4 ||rowspan="2" valign="top"|
* Anbindung von Qt 6-Programmen
* Bugfix QtQuick: MouseClick
|-
| valign="top"| 5.15.0 || valign="top"| x64 || valign="top"| gcc || valign="top"| gcc_x64_Qt5.15.0
|-

|rowspan="1" valign="top"|2022-2
| valign="top"| 5.15.0 || valign="top"| x64 || valign="top"| gcc || valign="top"| gcc_x64_Qt5.15.0 ||
* Ausgabe von QT-Version und Buildparameter in Log-Datei bei DLL-Start
|-

|rowspan="1" valign="top"|2022-1
| valign="top"| 5.15.0 || valign="top"| x64 || valign="top"| gcc || valign="top"| gcc_x64_Qt5.15.0 ||
* Separate DLLs für QtQuick/QWidget und nur QWidget
* Feature: Auslesen Vertikaler Header bei Tabellen
* Feature: Screenshot bei Fehler
|-

|rowspan="1" valign="top"|2021-2
|| 5.15.0 || x64 || gcc || gcc_x64_Qt5.15.0 || QtQuick / QML
|-

|rowspan="2" valign="top"|2021-1
|| 5.12.2 || arm32 || gcc || gcc_arm32_Qt.12.2 ||
|-
|| 5.9.5 || x64 || gcc || gcc_x64_Qt5.9.5 ||
|-

|rowspan="1" valign="top"|2020-2
|| 5.9.1 || x64 || gcc || gcc_x64_Qt5.9.1 ||
|-

|rowspan="1" valign="top"|2020-1
|| 5.12.3 || x64 || gcc || gcc_x64_Qt5.12.3 ||
|-

|}

----
Zurück zu [[Qt Plugin Reference]]

QT Testing

2025-10-23T10:50:46Z

Alkurz: /* Windows */

'''Deutsche Version''' | [[ QT Testing/en | English Version ]]

==Vorbedingungen==
===Qt-Download===
https://www.qt.io/download

===Unterstützte Versionen===
Expecco unterstützt das Testen von Qt-Applikationen unter Windows und Linux, Qt Quick/QML-Anwendungen ab der '''Qt Version 5'''.

Für die verschiedenen Qt-Versionen, Betriebssysteme, Entwicklungsumgebungen (VisualStudio, ...) und Rechnerarchitekturen (32/64 bit) stellen wir eigens erzeugte Bibliotheken (dll, so) zur Verfügung. Einige davon werden standardmäßig mit expecco ausgeliefert. Für andere Versionen erzeugen wir die Bibliothek auf Anfrage.

Eine Übersicht über die ausgelieferten Bibliotheken und ihren Versionsstand finden sie [[#ExpeccoTestService-Bibliothek: Auslieferung in Expecco-Versionen|hier]].

==Testen von Qt-Programmen==

===Testvorbereitungen===

====Einbinden der expeccoTestService-Bibliothek====

Um mit expecco ein Qt-Programm zu testen, wird in das zu testenden Programms die von uns ausgelieferte Bibliothek ''expeccoTestService.[dll/so]'' eingebunden. Dies erfolgt über ein Batch- bzw. Shell-Skript ohne Eingriff in den Sourcecode des zu testenden Programms. Diese DLL übernimmt die Kommunikation zwischen dem Qt-Program und expecco über eine Socketverbindung.

Im Batch- bzw. Shell-Skript können Sie auch das Logging für die expeccoTestService-Bibliothek aktivieren.

Eine Anleitung für das jeweilige Betriebssystem des Testrechners finden Sie hier:
* [[Qt Inject Windows#Inject expeccoTestService-Library|Qt Inject für Windows]]
* [[Qt Inject Linux#Inject expeccoTestService-Library|Qt Inject für Linux / macOS]].

Alternativ kann der Aufruf der ExpeccoTestService-Bibliothek auch in den Sourcecode der zu testenden Applikation eingefügt werden ([[Qt Inject Windows#Insert into Source Code (alternative)|Beschreibung]]).

====Startparameter====

Die ExpeccoTestService-Bibliothek kann über Umgebungsvariablen eingestellt werden:
* Log-Level: <code>ETS_QT_LOG_LEVEL</code> 
: <code>0</code> keine Logausgaben (Standardwert)
: vor expecco-Version 24.1: <code>2</code>: Debug-Logausgaben
: ab expecco-Version 24.1: <code>2</code> or <code>DEBUG</code> (Debug-Logausgaben), <code>3</code> or <code>INFO</code> (Info-Logausgaben), <code>4</code> or <code>WARN</code> (Warnungen und Fehler)

* Log-File: <code>ETS_QT_LOG_FILE</code> (Standardwert: c:\Windows\temp\etsQt.log bzw. /tmp/etsQt.log)
* Server-Port: <code>ETS_QT_PORT_NUMBER</code> (Standardwert: 8866)
* Timeout Vorschau im ms (nur Qt Quick): <code>ETS_TIMEOUT_QUICK_IMAGE</code> (Standardwert: 200)

====Benötigte Qt-Bibliotheken zur Laufzeit====

Die ExpeccoTestService-Bibliothek ist abhängig von folgenden Qt-Bibliotheken:
* Qt5Core
* Qt5Gui
* Qt5Network
* Qt5Qml
* Qt5Quick (V2 mit Qt Quick-Integration (expecco 21.2))
* Qt5QmlModel (V2 mit Qt Quick-Integration (expecco 21.2))
* Qt5Widgets

===Verbinden mit expecco GUI Browser===

Mit dem GUI Browser kann eine Verbindung zum zu testenden Programm aufgebaut werden:

<code>Verbinden</code> - <code>Qt</code>

Im nachfolgenden Dialog die Netzwerkadresse des Rechners, auf dem die Applikation läuft eingeben sowie den Port für die Verbindung (Standardmäßig 8866)

Anleitung [[Expecco GUI Tests_Extension Reference|GUI Browser]].

==Qt Quick-/QML-Programme==

Qt Quick-/QML-Anwendungen können ab expecco 21.2 mit der expecco QtLibrary getestet werden.

Hierfür wird eine neue ExpeccoTextService-Bibliothek mit dem Namenszusatz V2 ausgeliefert. Die Bibliothek ist von zusätzlichen Qt-Bibliotheken abhängig (siehe [[#Benötigte Qt-Bibliotheken zur Laufzeit|Benötigte Qt-Bibliotheken zur Laufzeit]]).

{| class="wikitable"
| '''Nur expecco 21.2''' Es wird nur eine ExpeccoTextService-Bibliothek ausgeliefert, die aber bereits Qt Quick-/QML-Support bietet. Erst ab Version 22.1 werden zwei separate Bibliotheken bereitsgestellt.
|-
|}

===Qt Quick/QML-Aktionen===

Für den Test von Qt Quick-/QML-Programmen können fast alle Aktionen der QtLibrary verwendet werden, die für das Testen von Qt-Programmen auf Basis von QWidget / QApplication definiert sind.

QWidget-Aktionen sind dabei für Qt Quick-Elemente, die sich von QQuickItem ableiten, anwendbar.
QQuickItemView-Aktionen sind für die Listen-Elemente von Qt Quick geeignet.

Die unterschiedliche Behandlung kapselt der ExpeccoTestService. Die Aktion und die Eingangs- und Ausgangspins bleiben somit für beide Qt-Technologien gleich.

Die Aktionen, die auch für Tests von Qt Quick-/QML-Programmen geeignet sind, sind mit dem Etikett / Tag <code>qt-quick</code> versehen. Die Aktionen können dadurch mit einer konfigurierbaren Farbe dargestellt werden ([[Settings TagColorSettings/en|Extras - Einstellungen - Look & Feel - Farben per Etikett (Tag)]]).

===Qt Quick-/QML-Besonderheiten===

====Steuerung über Eigenschaften / Properties====

Basis aller Qt Quick-/QML-Oberflächenelemente ist die Klasse QQuickItem. Über Properties / Eigenschaften können in ihr die meisten Eigenschaften eingestellt werden. Von QQuickItem gibt es eine Vielzahl von Ableitungen. Expecco stellt dafür keine speziellen Bausteine zur Verfügung, die Elemente sind aber über ihre Eigenschaften steuerbar.

{| class="wikitable"
! Qt Quick-Element !! Eigenschaft !! Kommentar
|-
| Tumbler || currentIndex ||
|-
| Switch|| checked || Geeignete Aktionen: <code>QCheckButton::GetState</code> <code>QCheckButton::SetState = %2</code>
|-
|colspan="3"| wird fortgesetzt
|-
|}

====Aktionen für selektiertes Element====
Die Anzeige von Aktionen für GUI-Elemente im GUI-Browser ist nicht vollständig, da Qt Quick/QML nicht für jeden Oberflächenelement vordefinierte Elemente hat.

====Noch nicht implementiert====
* TreeView
* Menu
* Selektion von Zellen - bisher kann nur eine Zeile selektiert werden

==Bekannte Probleme==

===XPath-Implementierung===

Mit XPath kann auf Übereinstimmung von Namen oder Index der Elemente gesucht werden. Filterung nach Namensteilen (Anfang, Ende, Mitte) wird derzeit nicht unterstützt.

===QApplication::ShortCutEvent===

Aufgrund von internen Änderungen in Qt Version 5 funktioniert der Baustein nicht mehr. Ein Workaround besteht darin, die Tastenereignisse separat zu senden, wie im Beispiel im Reiter Test/Demo der Aktion gezeigt.

==ExpeccoTestService-Bibliothek: Auslieferung in Expecco-Versionen==

Aufstellung der Expecco-Versionen mit der letzten Aktualisierung der ''ExpeccoTestService''-Bibliothek für die verschieden Qt-Versionen und Buildsysteme.

Weitere Versionen können auf Anfrage geliefert werden.

===Windows===
{| class="wikitable"
! Expecco-Version !! Qt Version !! Architektur !! Build-System !! Verzeichnis !! Kommentar
|-

|rowspan="4" valign="top"|2025-2
|| 6.8.3 || x64 || vs2022 || vs2022_x64_Qt6.8.3 || rowspan="4" valign="top"|
|-
|| 6.2.4 || x64 || vs2019 || vs2019_x64_Qt6.2.4 ||
|-
|| 5.15.0 || x64 || vs2022 || vs2022_x64_Qt5.15.0
|-
|| 5.15.0 || x64 || vs2019 || vs2019_x64_Qt5.15.0
|-

|rowspan="3" valign="top"|2024-1
|| 6.2.4 || x64 || vs2019 || vs2019_x64_Qt6.2.4 || rowspan="3" valign="top"|
* Logging with Loglevels <code>DEBUG</code>, <code>INFO</code> and <code>WARN</code>
* Mouse event Move has been revised (QT:OS-MouseEvent...)
|-
|| 5.15.0 || x64 || vs2022 || vs2022_x64_Qt5.15.0
|-
|| 5.15.0 || x64 || vs2019 || vs2019_x64_Qt5.15.0
|-

|rowspan="3" valign="top"|2023-2
|| 6.2.4 || x64 || vs2019 || vs2019_x64_Qt6.2.4 || rowspan="3" valign="top"|
* Neuer Baustein ''QButton::Click'': Direkter Klick, nicht an Thread delegiert
|-
|| 5.15.0 || x64 || vs2022 || vs2022_x64_Qt5.15.0
|-
|| 5.15.0 || x64 || vs2019 || vs2019_x64_Qt5.15.0
|-

|rowspan="2" valign="top"|2023-1
|| 6.2.4 || x64 || vs2019 || vs2019_x64_Qt6.2.4 || rowspan="2" valign="top"|
* Anbindung von Qt 6-Programmen
* Bugfix QtQuick: MouseClick
|-
|| 5.15.0 || x64 || vs2019 || vs2019_x64_Qt5.15.0
|-

|rowspan="3" valign="top"|2022-2
|| 5.15.0 || x64 || vs2019 || vs2019_x64_Qt5.15.0 || rowspan="3" valign="top"|
* Ausgabe von QT-Version und Buildparameter in Log-Datei bei DLL-Start
|-
|| 5.15.0 || x86 || vs2019 || vs2019_Qt5.15.0
|-
|| 5.14.2 || x86 || vs2017 || vs2017_Qt5.14.2
|-

|rowspan="3" valign="top"|2022-1
|| 5.15.0 || x64 || vs2019 || vs2019_x64_Qt5.15.0 || rowspan="3" valign="top"|
* Separate DLLs für QtQuick/QWidget und nur QWidget
* Feature: Auslesen Vertikaler Header bei Tabellen
* Feature: Screenshot bei Fehler
|-
|| 5.15.0 || x86 || vs2019 || vs2019_Qt5.15.0
|-
|| 5.14.2 || x86 || vs2017 || vs2017_Qt5.14.2
|-

|rowspan="4" valign="top"|2021-2
|| 5.15.0 || x64 || vs2019 || vs2019_x64_Qt5.15.0 || rowspan="4" valign="top"| QtQuick / QML
|-
|| 5.15.0 || x86 || vs2019 || vs2019_Qt5.15.0
|-
|| 5.9.3 || x64 || vs2015 || vs2015_x64_Qt5.9.3
|-
|| 5.9.1 || x64 || vs2015 || vs2015_x64_Qt5.9.1
|-

|rowspan="1" valign="top"|2021-1
|| 5.9.3 || x86 || vs2015 || vs2015_x86_Qt5.9.3 ||
|-

|rowspan="1" valign="top"|2020-1
|| 5.8.0 || x86 || vs2013 || vs2013_Qt5.8.0 ||
|-

|rowspan="2" valign="top"|2019-2
|| 5.9.3 || x64 || vs2013 || vs2013_x64_Qt5.9.3 ||
|-
|| 5.9.1 || x64 || vs2013 || vs2013_x64_Qt5.9.1 ||
|-

|rowspan="1" valign="top"|2018-2
|| 5.4.2 || x86 || vs2010 || vs2010_Qt5.4.2 ||
|-

|}

===Linux / macOS===

{| class="wikitable"
! Expecco-Version !! Qt Version !! Architektur !! Build-System !! Verzeichnis !! Kommentar
|-

|rowspan="2" valign="top"|2023-2
| valign="top"| 6.2.4 || valign="top"| x64 || valign="top"| gcc || valign="top"| gcc_x64_Qt6.2.4 ||rowspan="2" valign="top"|
* Neuer Baustein QButton::Click: Direkter Klick, nicht an Thread delegiert
|-
| valign="top"| 5.15.0 || valign="top"| x64 || valign="top"| gcc || valign="top"| gcc_x64_Qt5.15.0
|-

|rowspan="2" valign="top"|2023-1
| valign="top"| 6.2.4 || valign="top"| x64 || valign="top"| gcc || valign="top"| gcc_x64_Qt6.2.4 ||rowspan="2" valign="top"|
* Anbindung von Qt 6-Programmen
* Bugfix QtQuick: MouseClick
|-
| valign="top"| 5.15.0 || valign="top"| x64 || valign="top"| gcc || valign="top"| gcc_x64_Qt5.15.0
|-

|rowspan="1" valign="top"|2022-2
| valign="top"| 5.15.0 || valign="top"| x64 || valign="top"| gcc || valign="top"| gcc_x64_Qt5.15.0 ||
* Ausgabe von QT-Version und Buildparameter in Log-Datei bei DLL-Start
|-

|rowspan="1" valign="top"|2022-1
| valign="top"| 5.15.0 || valign="top"| x64 || valign="top"| gcc || valign="top"| gcc_x64_Qt5.15.0 ||
* Separate DLLs für QtQuick/QWidget und nur QWidget
* Feature: Auslesen Vertikaler Header bei Tabellen
* Feature: Screenshot bei Fehler
|-

|rowspan="1" valign="top"|2021-2
|| 5.15.0 || x64 || gcc || gcc_x64_Qt5.15.0 || QtQuick / QML
|-

|rowspan="2" valign="top"|2021-1
|| 5.12.2 || arm32 || gcc || gcc_arm32_Qt.12.2 ||
|-
|| 5.9.5 || x64 || gcc || gcc_x64_Qt5.9.5 ||
|-

|rowspan="1" valign="top"|2020-2
|| 5.9.1 || x64 || gcc || gcc_x64_Qt5.9.1 ||
|-

|rowspan="1" valign="top"|2020-1
|| 5.12.3 || x64 || gcc || gcc_x64_Qt5.12.3 ||
|-

|}

----
Zurück zu [[Qt Plugin Reference]]

QT Testing/en

2025-10-23T10:50:17Z

Alkurz: /* Windows */

[[QT_Testing|Deutsche Version]] | '''English Version'''

==Pre-requisites==
===Qt download===
https://www.qt.io/download

===Supported Versions===
Expecco supports testing of Qt applications on Windows and Linux, Qt Quick/QML applications from '''Qt version 5''''.

For the different Qt versions, operating systems, development environments (VisualStudio, ...) and computer architectures (32/64 bit) we provide specially generated libraries (dll, so). Some of them are delivered with expecco by default. For other versions we generate the library on request.

An overview of the delivered libraries and their version status can be found [[#ExpeccoTestService Library: Delivery in Expecco Versions|here]].

==Testing Qt Programs==

===Test Preparations===

====Integrating the ExpeccoTestService Library====

To test a Qt program with expecco, the library ''expeccoTestService.[dll/so]'' delivered by us is included in the program to be tested. This is done via a batch or shell script without intervention in the source code of the program to be tested. This DLL implements the communication between the Qt program and expecco.

You can also activate logging for the expeccoTestService library in the batch or shell script.

Instructions for the respective operating system of the test computer can be found here:
* [[Qt Inject Windows#Inject expeccoTestService-Library|Qt Inject for Windows]]
* [[Qt Inject Linux#Inject expeccoTestService-Library|Qt Inject for Linux / macOS]].

Alternatively, the ExpeccoTestService library call can be inserted into the source code of the application under test ([[Qt Inject Windows/en#Insert into Source Code (alternative)|Description]]).

====Start Parameters====

The ExpeccoTestService library can be set via environment variables:
* Log level: <code>ETS_QT_LOG_LEVEL</code> 
: <code>0</code> no logging (default value) 
: before expecco version 24.1: <code>2</code>: logging (debug) 
: from expecco version 24.1: <code>2</code> or <code>DEBUG</code> (debug), <code>3</code> or <code>INFO</code> (info), <code>4</code> or <code>WARN</code> (warnings and errors)
* Log file: <code>ETS_QT_LOG_FILE</code> (default value: c:\Windows\temp\etsQt.log or /tmp/etsQt.log).
* Server port: <code>ETS_QT_PORT_NUMBER</code> (default value: 8866).
* Timeout preview in ms (only Qt Quick): <code>ETS_TIMEOUT_QUICK_IMAGE</code> (default value: 200)

====Required Qt Libraries at Runtime====

The ExpeccoTestService library depends on the following Qt libraries:
* Qt5Core
* Qt5Gui
* Qt5Network
* Qt5Qml
* Qt5Quick (V2 with Qt Quick integration (expecco 21.2))
* Qt5QmlModel (V2 with Qt Quick integration (expecco 21.2))
* Qt5Widgets

===Connecting with Expecco GUI Browser===

The GUI Browser can be used to connect to the program under test:

<code>Connect</code> - <code>Qt</code>.

In the following dialog, enter the network address of the computer running the application and the port for the connection (8866 by default).

Manual [[Expecco GUI Tests_Extension Reference|GUI Browser]].

==Qt Quick/QML Programs==
Qt Quick/QML applications can be tested with the expecco QtLibrary starting with expecco 21.2.

For this purpose, a new ExpeccoTextService library with the name suffix V2 is delivered. The library depends on additional Qt libraries (see [[#Required Qt Libraries at Runtime|Required Qt Libraries at Runtime]])

{| class="wikitable"
| '''Only expecco 21.2''' 
Only one ExpeccoTextService library is delivered, but it already offers Qt Quick/QML support. Only from version 22.1 two separate libraries are provided.
|-
|}

===Qt Quick/QML Actions===

For testing Qt Quick/QML programs almost all actions of the QtLibrary can be used, which are defined for testing Qt programs based on QWidget / QApplication.

QWidget actions are applicable to Qt Quick items derived from QQuickItem.
QQuickItemView actions are applicable to Qt Quick list items.

The different handling is encapsulated by the ExpeccoTestService. Thus, the action and the input and output pins remain the same for both Qt technologies.

The actions, which are also suitable for tests of Qt Quick/QML programmes, are provided with the label / tag <code>qt-quick</code>. The actions can thus be displayed with a configurable colour ([[Settings TagColorSettings/en|Extras - Settings - Look & Feel - Colours per Label (Tag)]]).

===Qt Quick/QML Peculiarities===

====Control via Properties====

The basis of all Qt Quick/QML interface elements is the QQuickItem class. Most of its properties can be set via properties. There are many derivations of QQuickItem. Expecco does not provide any special building blocks for this, but the elements can be controlled via their properties.

{| class="wikitable"
! Qt Quick element !! property !! Comment
|-
| Tumbler || currentIndex ||
|-
| Switch|| checked || Suitable actions: <code>QCheckButton::GetState</code> <code>QCheckButton::SetState = %2</code>
|-
|colspan="3"| will be continued
|-
|}

====Actions for Selected Element====
The display of actions for GUI elements in the GUI browser is not complete because Qt Quick/QML does not have predefined elements for each interface element.

====Not yet implemented====
* TreeView
* Menu
* Selection of cells - so far only one row can be selected

==Qt Known Problems==

===XPath implementation===

XPath can be used to search for matching names or index of elements. Filtering by name parts (starts-with, ends-with, contains) is currently not supported.

===QApplication::ShortCutEvent===

Due to internal changes in Qt version 5, the module no longer works. A workaround is to send the key events separately, as shown in the example in the Test/Demo tab of the action.

==ExpeccoTestService Library: Delivery in Expecco Versions==

List of Expecco versions with the latest update of the ''ExpeccoTestService'' library for the different Qt versions and build systems.

Further versions can be delivered on request.

===Windows===
{| class="wikitable"
! Expecco Version !! Qt Version !! Architecture !! Build System !! Directory !! Comment
|-

|rowspan="4" valign="top"|2025-2
|| 6.8.3 || x64 || vs2022 || vs2022_x64_Qt6.8.3 || rowspan="4" valign="top"|
|-
|| 6.2.4 || x64 || vs2019 || vs2019_x64_Qt6.2.4 ||
|-
|| 5.15.0 || x64 || vs2022 || vs2022_x64_Qt5.15.0
|-
|| 5.15.0 || x64 || vs2019 || vs2019_x64_Qt5.15.0
|-

|rowspan="3" valign="top"|2024-1
|| 6.2.4 || x64 || vs2019 || vs2019_x64_Qt6.2.4 || rowspan="3" valign="top"|
* Logging with Loglevels <code>DEBUG</code>, <code>INFO</code> and <code>WARN</code>
* Mouse event Move has been revised (QT:OS-MouseEvent...)
|-
|| 5.15.0 || x64 || vs2022 || vs2022_x64_Qt5.15.0
|-
|| 5.15.0 || x64 || vs2019 || vs2019_x64_Qt5.15.0
|-

|rowspan="3" valign="top"|2023-2
|| 6.2.4 || x64 || vs2019 || vs2019_x64_Qt6.2.4 || rowspan="3" valign="top"|
* New Step ''QButton::Click'': Direct click, not delegated to thread
|-
|| 5.15.0 || x64 || vs2022 || vs2022_x64_Qt5.15.0
|-
|| 5.15.0 || x64 || vs2019 || vs2019_x64_Qt5.15.0
|-

|rowspan="2" valign="top"|2023-1
|| 6.2.4 || x64 || vs2019 || vs2019_x64_Qt6.2.4 || rowspan="2" valign="top"|
* QT6 support
* Bugfix QtQuick: MouseClick
|-
|| 5.15.0 || x64 || vs2019 || vs2019_x64_Qt5.15.0
|-

|rowspan="3" valign="top"|2022-2
|| 5.15.0 || x64 || vs2019 || vs2019_x64_Qt5.15.0 || rowspan="3" valign="top"|
* Output version and build date in etsLog at start-up
|-
|| 5.15.0 || x86 || vs2019 || vs2019_Qt5.15.0
|-
|| 5.14.2 || x86 || vs2017 || vs2017_Qt5.14.2
|-

|rowspan="3" valign="top"|2022-1
|| 5.15.0 || x64 || vs2019 || vs2019_x64_Qt5.15.0 || rowspan="3" valign="top"|
* Separate DLLs for QtQuick/QWidget and only QWidget
* Feature: Reading vertical headers for tables
* Feature: Screenshot in case of error
|-
|| 5.15.0 || x86 || vs2019 || vs2019_Qt5.15.0
|-
|| 5.14.2 || x86 || vs2017 || vs2017_Qt5.14.2
|-

|rowspan="4" valign="top"|2021-2
|| 5.15.0 || x64 || vs2019 || vs2019_x64_Qt5.15.0 || rowspan="4" valign="top"| QtQuick / QML
|-
|| 5.15.0 || x86 || vs2019 || vs2019_Qt5.15.0
|-
|| 5.9.3 || x64 || vs2015 || vs2015_x64_Qt5.9.3
|-
|| 5.9.1 || x64 || vs2015 || vs2015_x64_Qt5.9.1
|-

|rowspan="1" valign="top"|2021-1
|| 5.9.3 || x86 || vs2015 || vs2015_x86_Qt5.9.3 ||
|-

|rowspan="1" valign="top"|2020-1
|| 5.8.0 || x86 || vs2013 || vs2013_Qt5.8.0 ||
|-

|rowspan="2" valign="top"|2019-2
|| 5.9.3 || x64 || vs2013 || vs2013_x64_Qt5.9.3 ||
|-
|| 5.9.1 || x64 || vs2013 || vs2013_x64_Qt5.9.1 ||
|-

|rowspan="1" valign="top"|2018-2
|| 5.4.2 || x86 || vs2010 || vs2010_Qt5.4.2 ||
|-

|}

===Linux / macOS===
{| class="wikitable"
! Expecco Version !! Qt Version !! Architecture !! Build System !! Directory !! Comment
|-

|rowspan="2" valign="top"|2024-1
|| 6.2.4 || x64 || gcc || gcc_x64_Qt6.2.4 || rowspan="2" valign="top"|
* Logging with Loglevels <code>DEBUG</code>, <code>INFO</code> and <code>WARN</code>
|-
|| 5.15.0 || x64 || gcc || gcc_x64_Qt5.15.0
|-

|rowspan="2" valign="top"|2023-1
|| 6.2.4 || x64 || gcc || gcc_x64_Qt6.2.4 || rowspan="2" valign="top"| QT6 support
|-
|| 5.15.0 || x64 || gcc || gcc_x64_Qt5.15.0
|-

|rowspan="1" valign="top"|2022-2
| valign="top"| 5.15.0 || valign="top"| x64 || valign="top"| gcc || valign="top"| gcc_x64_Qt5.15.0 || valign="top" | Output version and build date in etsLog at start-up
|-

|rowspan="1" valign="top"|2022-1
| valign="top"| 5.15.0 || valign="top"| x64 || valign="top"| gcc || valign="top"| gcc_x64_Qt5.15.0 ||
* Separate DLLs for QtQuick/QWidget and only QWidget
* Feature: Reading vertical headers for tables
* Feature: Screenshot in case of error
|-

|rowspan="1" valign="top"|2021-2
|| 5.15.0 || x64 || gcc || gcc_x64_Qt5.15.0 || QtQuick / QML
|-

|rowspan="2" valign="top"|2021-1
|| 5.12.2 || arm32 || gcc || gcc_arm32_Qt.12.2 ||
|-
|| 5.9.5 || x64 || gcc || gcc_x64_Qt5.9.5 ||
|-

|rowspan="1" valign="top"|2020-2
|| 5.9.1 || x64 || gcc || gcc_x64_Qt5.9.1 ||
|-

|rowspan="1" valign="top"|2020-1
|| 5.12.3 || x64 || gcc || gcc_x64_Qt5.12.3 ||
|-

|}

----

Back to [[Qt Plugin Reference/en|Qt Plugin Reference]]

Release Notes 25.x

2025-10-23T10:48:06Z

Alkurz: /* Release 25.2 */

See also: [[Release Notes 24.x]]
 

== Release 25.2 ==
*Improvement: Inspector shows XML Dom if it starts with '<' and ends with '>' and is parsable without error.
*Improvement: Handles very long index-lists (eg. 100k) more graceful
*Improvement: Bundled python3 installer updated to version 3.13.7
*Qt-Plugin supports Qt6.8 ([[QT_Testing/en#ExpeccoTestService_Library%3A_Delivery_in_Expecco_Versions|Delivered versions for QT and build environment]])

== Release 25.1 ==
*Improvement: additional "Info" tab in inspector views
*Improvement: less memory usage in the activity log
*Improvement: better error messages and more links to settings from the activity log's error message
*Improvement: additional units and conversions in the [[PhysicalValues/en|physical values framework]]
*Improvement: more precision in the [[Numeric_Limits/en#Higher_Precision_Numbers|high precision trigonometric and math functions]]
*Improvement: WindowsAutomation: Plugin Update to FlaUI 5
*Improvement: Mobile Testing: Better Device Lock/Unlock Support
*Improvement: StandardLibrary: "File [ *CSV ]" blocks got an additional "characterEncoding" pin (useful for reading/writing e.g. utf-8 encoded CSV files)
*Improvement: ExcelLib: better documentation. Now requires the openpyxl package version >= 3.1.5.
*Improvement: better model language editor (translate and fetch-strings functions)
*Improvement: ODBCLibrary: improved compatibility with different database vendors (supports the CedarDB database)
*Feature: translate and spell check in the workspace window
*Feature: EditLock of suites loaded from expeccoALM / AIDYMO
*Feature: Start Test in expeccoALM / AIDYMO (via expecco)
*Feature: new library containing expeccoALM control actions (those from the AIDYMO menu)
*Fix: the version diff viewer (did not correctly copy changed attachment files)

Release Notes 25.x

2025-10-23T10:47:32Z

Alkurz: /* Release 25.2 */

See also: [[Release Notes 24.x]]
 

== Release 25.2 ==
*Improvement: Inspector shows XML Dom if it starts with '<' and ends with '>' and is parsable without error.
*Improvement: Handles very long index-lists (eg. 100k) more graceful
*Improvement: Bundled python3 installer updated to version 3.13.7
*Qt-Plugin supports Qt6.8 [[QT_Testing/en#ExpeccoTestService_Library%3A_Delivery_in_Expecco_Versions|Delivered versions for QT and build environment]]

== Release 25.1 ==
*Improvement: additional "Info" tab in inspector views
*Improvement: less memory usage in the activity log
*Improvement: better error messages and more links to settings from the activity log's error message
*Improvement: additional units and conversions in the [[PhysicalValues/en|physical values framework]]
*Improvement: more precision in the [[Numeric_Limits/en#Higher_Precision_Numbers|high precision trigonometric and math functions]]
*Improvement: WindowsAutomation: Plugin Update to FlaUI 5
*Improvement: Mobile Testing: Better Device Lock/Unlock Support
*Improvement: StandardLibrary: "File [ *CSV ]" blocks got an additional "characterEncoding" pin (useful for reading/writing e.g. utf-8 encoded CSV files)
*Improvement: ExcelLib: better documentation. Now requires the openpyxl package version >= 3.1.5.
*Improvement: better model language editor (translate and fetch-strings functions)
*Improvement: ODBCLibrary: improved compatibility with different database vendors (supports the CedarDB database)
*Feature: translate and spell check in the workspace window
*Feature: EditLock of suites loaded from expeccoALM / AIDYMO
*Feature: Start Test in expeccoALM / AIDYMO (via expecco)
*Feature: new library containing expeccoALM control actions (those from the AIDYMO menu)
*Fix: the version diff viewer (did not correctly copy changed attachment files)

QT Testing

2025-10-23T10:40:55Z

Alkurz: /* Windows */

'''Deutsche Version''' | [[ QT Testing/en | English Version ]]

==Vorbedingungen==
===Qt-Download===
https://www.qt.io/download

===Unterstützte Versionen===
Expecco unterstützt das Testen von Qt-Applikationen unter Windows und Linux, Qt Quick/QML-Anwendungen ab der '''Qt Version 5'''.

Für die verschiedenen Qt-Versionen, Betriebssysteme, Entwicklungsumgebungen (VisualStudio, ...) und Rechnerarchitekturen (32/64 bit) stellen wir eigens erzeugte Bibliotheken (dll, so) zur Verfügung. Einige davon werden standardmäßig mit expecco ausgeliefert. Für andere Versionen erzeugen wir die Bibliothek auf Anfrage.

Eine Übersicht über die ausgelieferten Bibliotheken und ihren Versionsstand finden sie [[#ExpeccoTestService-Bibliothek: Auslieferung in Expecco-Versionen|hier]].

==Testen von Qt-Programmen==

===Testvorbereitungen===

====Einbinden der expeccoTestService-Bibliothek====

Um mit expecco ein Qt-Programm zu testen, wird in das zu testenden Programms die von uns ausgelieferte Bibliothek ''expeccoTestService.[dll/so]'' eingebunden. Dies erfolgt über ein Batch- bzw. Shell-Skript ohne Eingriff in den Sourcecode des zu testenden Programms. Diese DLL übernimmt die Kommunikation zwischen dem Qt-Program und expecco über eine Socketverbindung.

Im Batch- bzw. Shell-Skript können Sie auch das Logging für die expeccoTestService-Bibliothek aktivieren.

Eine Anleitung für das jeweilige Betriebssystem des Testrechners finden Sie hier:
* [[Qt Inject Windows#Inject expeccoTestService-Library|Qt Inject für Windows]]
* [[Qt Inject Linux#Inject expeccoTestService-Library|Qt Inject für Linux / macOS]].

Alternativ kann der Aufruf der ExpeccoTestService-Bibliothek auch in den Sourcecode der zu testenden Applikation eingefügt werden ([[Qt Inject Windows#Insert into Source Code (alternative)|Beschreibung]]).

====Startparameter====

Die ExpeccoTestService-Bibliothek kann über Umgebungsvariablen eingestellt werden:
* Log-Level: <code>ETS_QT_LOG_LEVEL</code> 
: <code>0</code> keine Logausgaben (Standardwert)
: vor expecco-Version 24.1: <code>2</code>: Debug-Logausgaben
: ab expecco-Version 24.1: <code>2</code> or <code>DEBUG</code> (Debug-Logausgaben), <code>3</code> or <code>INFO</code> (Info-Logausgaben), <code>4</code> or <code>WARN</code> (Warnungen und Fehler)

* Log-File: <code>ETS_QT_LOG_FILE</code> (Standardwert: c:\Windows\temp\etsQt.log bzw. /tmp/etsQt.log)
* Server-Port: <code>ETS_QT_PORT_NUMBER</code> (Standardwert: 8866)
* Timeout Vorschau im ms (nur Qt Quick): <code>ETS_TIMEOUT_QUICK_IMAGE</code> (Standardwert: 200)

====Benötigte Qt-Bibliotheken zur Laufzeit====

Die ExpeccoTestService-Bibliothek ist abhängig von folgenden Qt-Bibliotheken:
* Qt5Core
* Qt5Gui
* Qt5Network
* Qt5Qml
* Qt5Quick (V2 mit Qt Quick-Integration (expecco 21.2))
* Qt5QmlModel (V2 mit Qt Quick-Integration (expecco 21.2))
* Qt5Widgets

===Verbinden mit expecco GUI Browser===

Mit dem GUI Browser kann eine Verbindung zum zu testenden Programm aufgebaut werden:

<code>Verbinden</code> - <code>Qt</code>

Im nachfolgenden Dialog die Netzwerkadresse des Rechners, auf dem die Applikation läuft eingeben sowie den Port für die Verbindung (Standardmäßig 8866)

Anleitung [[Expecco GUI Tests_Extension Reference|GUI Browser]].

==Qt Quick-/QML-Programme==

Qt Quick-/QML-Anwendungen können ab expecco 21.2 mit der expecco QtLibrary getestet werden.

Hierfür wird eine neue ExpeccoTextService-Bibliothek mit dem Namenszusatz V2 ausgeliefert. Die Bibliothek ist von zusätzlichen Qt-Bibliotheken abhängig (siehe [[#Benötigte Qt-Bibliotheken zur Laufzeit|Benötigte Qt-Bibliotheken zur Laufzeit]]).

{| class="wikitable"
| '''Nur expecco 21.2''' Es wird nur eine ExpeccoTextService-Bibliothek ausgeliefert, die aber bereits Qt Quick-/QML-Support bietet. Erst ab Version 22.1 werden zwei separate Bibliotheken bereitsgestellt.
|-
|}

===Qt Quick/QML-Aktionen===

Für den Test von Qt Quick-/QML-Programmen können fast alle Aktionen der QtLibrary verwendet werden, die für das Testen von Qt-Programmen auf Basis von QWidget / QApplication definiert sind.

QWidget-Aktionen sind dabei für Qt Quick-Elemente, die sich von QQuickItem ableiten, anwendbar.
QQuickItemView-Aktionen sind für die Listen-Elemente von Qt Quick geeignet.

Die unterschiedliche Behandlung kapselt der ExpeccoTestService. Die Aktion und die Eingangs- und Ausgangspins bleiben somit für beide Qt-Technologien gleich.

Die Aktionen, die auch für Tests von Qt Quick-/QML-Programmen geeignet sind, sind mit dem Etikett / Tag <code>qt-quick</code> versehen. Die Aktionen können dadurch mit einer konfigurierbaren Farbe dargestellt werden ([[Settings TagColorSettings/en|Extras - Einstellungen - Look & Feel - Farben per Etikett (Tag)]]).

===Qt Quick-/QML-Besonderheiten===

====Steuerung über Eigenschaften / Properties====

Basis aller Qt Quick-/QML-Oberflächenelemente ist die Klasse QQuickItem. Über Properties / Eigenschaften können in ihr die meisten Eigenschaften eingestellt werden. Von QQuickItem gibt es eine Vielzahl von Ableitungen. Expecco stellt dafür keine speziellen Bausteine zur Verfügung, die Elemente sind aber über ihre Eigenschaften steuerbar.

{| class="wikitable"
! Qt Quick-Element !! Eigenschaft !! Kommentar
|-
| Tumbler || currentIndex ||
|-
| Switch|| checked || Geeignete Aktionen: <code>QCheckButton::GetState</code> <code>QCheckButton::SetState = %2</code>
|-
|colspan="3"| wird fortgesetzt
|-
|}

====Aktionen für selektiertes Element====
Die Anzeige von Aktionen für GUI-Elemente im GUI-Browser ist nicht vollständig, da Qt Quick/QML nicht für jeden Oberflächenelement vordefinierte Elemente hat.

====Noch nicht implementiert====
* TreeView
* Menu
* Selektion von Zellen - bisher kann nur eine Zeile selektiert werden

==Bekannte Probleme==

===XPath-Implementierung===

Mit XPath kann auf Übereinstimmung von Namen oder Index der Elemente gesucht werden. Filterung nach Namensteilen (Anfang, Ende, Mitte) wird derzeit nicht unterstützt.

===QApplication::ShortCutEvent===

Aufgrund von internen Änderungen in Qt Version 5 funktioniert der Baustein nicht mehr. Ein Workaround besteht darin, die Tastenereignisse separat zu senden, wie im Beispiel im Reiter Test/Demo der Aktion gezeigt.

==ExpeccoTestService-Bibliothek: Auslieferung in Expecco-Versionen==

Aufstellung der Expecco-Versionen mit der letzten Aktualisierung der ''ExpeccoTestService''-Bibliothek für die verschieden Qt-Versionen und Buildsysteme.

Weitere Versionen können auf Anfrage geliefert werden.

===Windows===
{| class="wikitable"
! Expecco-Version !! Qt Version !! Architektur !! Build-System !! Verzeichnis !! Kommentar
|-

|rowspan="4" valign="top"|2025-2
|| 6.8.3 || x64 || vs2022 || vs2022_x64_Qt6.8.3 || rowspan="4" valign="top"|
|-
|| 6.2.4 || x64 || vs2019 || vs2019_x64_Qt6.2.4 ||
|-
|| 5.15.0 || x64 || vs2022 || vs2022_x64_Qt5.15.0
|-
|| 5.15.0 || x64 || vs2019 || vs2019_x64_Qt5.15.0
|-

|rowspan="3" valign="top"|2023-2
|| 6.2.4 || x64 || vs2019 || vs2019_x64_Qt6.2.4 || rowspan="3" valign="top"|
* Neuer Baustein ''QButton::Click'': Direkter Klick, nicht an Thread delegiert
|-
|| 5.15.0 || x64 || vs2022 || vs2022_x64_Qt5.15.0
|-
|| 5.15.0 || x64 || vs2019 || vs2019_x64_Qt5.15.0
|-

|rowspan="2" valign="top"|2023-1
|| 6.2.4 || x64 || vs2019 || vs2019_x64_Qt6.2.4 || rowspan="2" valign="top"|
* Anbindung von Qt 6-Programmen
* Bugfix QtQuick: MouseClick
|-
|| 5.15.0 || x64 || vs2019 || vs2019_x64_Qt5.15.0
|-

|rowspan="3" valign="top"|2022-2
|| 5.15.0 || x64 || vs2019 || vs2019_x64_Qt5.15.0 || rowspan="3" valign="top"|
* Ausgabe von QT-Version und Buildparameter in Log-Datei bei DLL-Start
|-
|| 5.15.0 || x86 || vs2019 || vs2019_Qt5.15.0
|-
|| 5.14.2 || x86 || vs2017 || vs2017_Qt5.14.2
|-

|rowspan="3" valign="top"|2022-1
|| 5.15.0 || x64 || vs2019 || vs2019_x64_Qt5.15.0 || rowspan="3" valign="top"|
* Separate DLLs für QtQuick/QWidget und nur QWidget
* Feature: Auslesen Vertikaler Header bei Tabellen
* Feature: Screenshot bei Fehler
|-
|| 5.15.0 || x86 || vs2019 || vs2019_Qt5.15.0
|-
|| 5.14.2 || x86 || vs2017 || vs2017_Qt5.14.2
|-

|rowspan="4" valign="top"|2021-2
|| 5.15.0 || x64 || vs2019 || vs2019_x64_Qt5.15.0 || rowspan="4" valign="top"| QtQuick / QML
|-
|| 5.15.0 || x86 || vs2019 || vs2019_Qt5.15.0
|-
|| 5.9.3 || x64 || vs2015 || vs2015_x64_Qt5.9.3
|-
|| 5.9.1 || x64 || vs2015 || vs2015_x64_Qt5.9.1
|-

|rowspan="1" valign="top"|2021-1
|| 5.9.3 || x86 || vs2015 || vs2015_x86_Qt5.9.3 ||
|-

|rowspan="1" valign="top"|2020-1
|| 5.8.0 || x86 || vs2013 || vs2013_Qt5.8.0 ||
|-

|rowspan="2" valign="top"|2019-2
|| 5.9.3 || x64 || vs2013 || vs2013_x64_Qt5.9.3 ||
|-
|| 5.9.1 || x64 || vs2013 || vs2013_x64_Qt5.9.1 ||
|-

|rowspan="1" valign="top"|2018-2
|| 5.4.2 || x86 || vs2010 || vs2010_Qt5.4.2 ||
|-

|}

===Linux / macOS===

{| class="wikitable"
! Expecco-Version !! Qt Version !! Architektur !! Build-System !! Verzeichnis !! Kommentar
|-

|rowspan="2" valign="top"|2023-2
| valign="top"| 6.2.4 || valign="top"| x64 || valign="top"| gcc || valign="top"| gcc_x64_Qt6.2.4 ||rowspan="2" valign="top"|
* Neuer Baustein QButton::Click: Direkter Klick, nicht an Thread delegiert
|-
| valign="top"| 5.15.0 || valign="top"| x64 || valign="top"| gcc || valign="top"| gcc_x64_Qt5.15.0
|-

|rowspan="2" valign="top"|2023-1
| valign="top"| 6.2.4 || valign="top"| x64 || valign="top"| gcc || valign="top"| gcc_x64_Qt6.2.4 ||rowspan="2" valign="top"|
* Anbindung von Qt 6-Programmen
* Bugfix QtQuick: MouseClick
|-
| valign="top"| 5.15.0 || valign="top"| x64 || valign="top"| gcc || valign="top"| gcc_x64_Qt5.15.0
|-

|rowspan="1" valign="top"|2022-2
| valign="top"| 5.15.0 || valign="top"| x64 || valign="top"| gcc || valign="top"| gcc_x64_Qt5.15.0 ||
* Ausgabe von QT-Version und Buildparameter in Log-Datei bei DLL-Start
|-

|rowspan="1" valign="top"|2022-1
| valign="top"| 5.15.0 || valign="top"| x64 || valign="top"| gcc || valign="top"| gcc_x64_Qt5.15.0 ||
* Separate DLLs für QtQuick/QWidget und nur QWidget
* Feature: Auslesen Vertikaler Header bei Tabellen
* Feature: Screenshot bei Fehler
|-

|rowspan="1" valign="top"|2021-2
|| 5.15.0 || x64 || gcc || gcc_x64_Qt5.15.0 || QtQuick / QML
|-

|rowspan="2" valign="top"|2021-1
|| 5.12.2 || arm32 || gcc || gcc_arm32_Qt.12.2 ||
|-
|| 5.9.5 || x64 || gcc || gcc_x64_Qt5.9.5 ||
|-

|rowspan="1" valign="top"|2020-2
|| 5.9.1 || x64 || gcc || gcc_x64_Qt5.9.1 ||
|-

|rowspan="1" valign="top"|2020-1
|| 5.12.3 || x64 || gcc || gcc_x64_Qt5.12.3 ||
|-

|}

----
Zurück zu [[Qt Plugin Reference]]

Lizenzserver expecco ALM

2025-09-04T09:10:56Z

Alkurz: /* Voraussetzungen */

==Übersicht==

Der expecco Lizenzserver dient der zentralen Verwaltung von expecco Lizenzen. Durch den Lizenzserver kann expecco auf verschiedenen Rechnern (sowohl Entwicklungs- als auch reine Testausführungsrechner) ohne Dongle und lokale Lizenzdatei auf allen erreichbaren Rechnern im Netz installiert und ausgeführt werden.

Lizenzen werden dabei von den expecco-Rechnern vom Lizenzserver angefordert, im Lizenzserver reserviert,
und nach der Sitzung bzw. Testlauf wieder zurückgegeben. Damit können mehr Nutzer (allerdings nicht gleichzeitig) mit expecco arbeiten als Lizenzen erworben wurden.

Lizenzen sind kryptographisch gesicherte Dateien, welche nur in Verbindung mit einem von eXept gelieferten Lizenzserver-Dongle gelesen bzw. genutzt werden können. Lizenzen sind Dongle-spezifisch. Es ist also nicht notwendig, Maßnahmen zum Schutz vor Diebstahl oder Kopieren von Lizenzdateien zu ergreifen. Allerdings ist ein Verlust des Dongles aus nahe liegenden Gründen zu vermeiden.

{{SEITENTITEL:Lizenzservice Installation}}

== Voraussetzungen ==
Wir empfehlen, expecco ALM auf einem durchgehend verfügbaren Server mit Windows Server 2012 / Windows 10 oder höher zu installieren. Die Installation auf anderen Betriebssystemen (wie z.B. Linux) wäre bei Bedarf auch möglich. Ebenso ist die Installation in einer Cloud möglich, dort ist der Betrieb ohne Dongle möglich.

Damit expecco ALM flüssig arbeiten kann, werden folgende Hardware-Anforderungen an den Server gestellt:
 - ein "dezidierter" Prozessor mit mindestens 2 GHz
 - mindestens 1 GB Arbeitsspeicher (ausschließlich für expecco ALM)
 - mindestens 10 GB Festplattenspeicher (je nach Größe der Daten die expecco ALM verwalten soll)

Stellen Sie sicher, dass dieser Server für alle Clients erreichbar ist. Clients sind alle Rechner der expecco ALM Benutzer, Rechner die expecco ALM zur Testausführung dienen und Rechner mit "Floating" lizenziertem expecco. Bei Problemen bezüglich der Erreichbarkeit wenden Sie sich bitte an Ihren Netzwerkadministrator.

== Installation ==

Bitte halten Sie Ihre Lizenzdatei und ggfs. den Dongle für die Installation von expecco ALM bereit. 
Für die Installation in der Cloud benötigen Sie keinen Dongle; wir liefern dann eine Lizenzdatei, die an die MAC-Adresse des Servers gebunden ist. Falls sich der Server und damit dessen MAC-Adresse ändert, erhalten Sie eine neue angepasste Lizenzdatei von uns.

Ihre Lizenzdatei und eine Verknüpfung zum aktuellen expecco ALM Setup haben wir Ihnen per E-Mail zu kommen lassen. Der Installer hat folgenden Namen "expecco ALM 24.2.0 Setup.exe", wobei die Versionsnummer abweichen kann. Den Dongle haben wir per Post an Sie versendet (es sei denn Sie evaluieren expecco ALM oder nutzen die Cloud Variante mit der MAC-Adressen-Bindung).

Gehen Sie bitte wie folgt vor:
* Laden Sie den expecco ALM Installer auf dem Server, auf dem expecco ALM künftig laufen soll, herunter
* Legen Sie Ihre Lizenzdatei ebenfalls auf dem Server ab
* Verbinden Sie Ihren Dongle mit dem Server (Wenn Sie expecco ALM evaluieren oder die Cloud Variante mit der MAC-Adressen-Bindung nutzen, überspringen Sie diesen Schritt)
* Führen Sie den expecco ALM Installer ("expecco ALM ?.?.?.? Setup.exe" bzw. unter Linux "expecco ALM ?.?.?.? Setup.package") aus

Für Linux werden zusätzliche Pakete der Linux-Distribution benötigt. Diese sind [[Installation#Installation_von_expecco_auf_Linux|hier]] aufgeführt.

Nachdem der Installer erfolgreich ausgeführt wurde, läuft expecco ALM bereits als Service. Auf Ihrem Desktop wurde eine Verknüpfung zu expecco ALM angelegt. Es wurde auch ein Ordner für expecco ALM in Ihrem Startmenü erstellt. Dort können Sie unter "Konfiguration" den Port ändern (Standard ist Port 8081) oder über die "Logdatei" eventuelle Probleme feststellen.

[[Datei:InstallAlmLicense.png|mini|Anhang 1]]
Über die Verknüpfung auf Ihrem Desktop lässt sich expecco ALM mit Ihrem Standardbrowser öffnen. Es wird eine Seite zum Installieren Ihrer expecco ALM Lizenz angezeigt (Anhang 1). Über "Lizenzdatei installieren" können Sie Ihre Lizenzdatei (die Sie bereits auf dem Server abgelegt haben) auswählen. Nach dem expecco ALM Ihre Lizenzdatei akzeptiert hat, können Sie diese entfernen. Wenn bereits eine gültige Lizenz installiert ist, wird stattdessen die Anmeldeseite angezeigt. Falls es sich bei Ihnen um eine Erstinstallation handelt, können Sie sich mit Anmeldenamen "admin" und Kennwort "admin" anmelden.

Falls eine leere Seite oder eine Fehlerseite angezeigt wird, probieren Sie einen anderen Port aus und/oder schauen Sie in der Logdatei nach Fehlermeldungen.

== SSL-Verschlüsselung / Proxy-Server ==
expecco ALM unterstützt aktuell noch nicht direkt SSL-Verschlüsselung. Über einen Proxy-Server ist diese aber problemlos einzurichten, z.B. über einen Apache-Server. Falls auf ihrem Server weitere Webseiten gehostet werden, ist dies ja ohnehin erforderlich, da sich nicht mehrere Prozesse gleichzeitig an den Port 443 binden können.

Eine Apache2 VirtualHost-Konfiguration würde entsprechend so aussehen (angenommen expecco ALM läuft mit Port 8465 - erforderliche Anpassung für ihre Konfiguration fett):
<VirtualHost *:443>
ServerName expeccoalm.xyz.de
ServerAdmin webmaster@xyz.de

Include /etc/letsencrypt/ssl-xyz.de.conf

SSLProxyEngine On

RewriteEngine on
RewriteCond %{HTTP:Upgrade} =websocket [NC]
RewriteRule /(.*) ws://localhost:8465/$1 [P,L]
RewriteCond %{HTTP:Upgrade} !=websocket [NC]

ProxyPass / http://localhost:8465/ nocanon
ProxyPassReverse / http://localhost:8465/
</VirtualHost>

Die SSL-Parameter mit dem Pfaden zu Ihren Zertifkaten uns Schlüsseln würden in diesem Konfigurations-Beispiel in der Apache-globalen Datei /etc/letsencrypt/ssl-xyz.de.conf liegen.

== Hinweise zur Lizenzierung ==
Wenn Sie expecco ALM erworben haben, erhalten Sie einen Dongle und eine Lizenzdatei. Falls Sie expecco ALM evaluieren, erhalten Sie ausschließlich die Lizenzdatei. Die Lizenzdatei beinhaltet eine für Sie individuelle expecco ALM Lizenz. So sind zum Beispiel: Der Name Ihrer Firma, für Sie freigeschaltete Module oder die Gültigkeitsdauer in der Lizenz hinterlegt. Der Dongle muss (insofern Sie expecco ALM erworben haben) ständig mit dem Server, auf dem expecco ALM ausgeführt wird, verbunden sein. Falls Sie den Dongle während des Betriebs abziehen, wird expecco ALM seinen Dienst einstellen.

== Lizenz wechseln ==
[[Datei:ChangeAlmLicense.png|mini|Anhang 2]]
Falls Sie eine aktuelle expecco ALM Version haben, können Sie eine neue Lizenzdatei "expecco ALM Lizenz *.lic" über das Webinterface von expecco ALM einspielen. Betrachten Sie dazu den angehängten Screenshot (Anhang 2).

Fall Sie eine ältere expecco ALM Version haben, müssen Sie folgendermaßen vorgehen:
 - Da Sie expecco ALM später neustarten müssen, tätigen Sie entsprechende Vorsorgemaßnahmen (Bspw. Benutzer abmelden, Datenbank sichern usw.)
 - Melden Sie sich auf dem Computer, der expecco ALM betreibt an
 - Begeben Sie sich in folgendes Verzeichnis "C:\Windows\SysWOW64\config\systemprofile\AppData\Roaming\expecco_ALM" oder falls es sich um ein 32Bit Betriebssystem handelt "C:\Windows\system32\config\systemprofile\AppData\Roaming\expecco_ALM" und löschen Sie die Datei "expecco_ALM.lic"
 - Starten Sie den expecco ALM Service über den Windows-Service-Manager neu oder beenden Sie über den Windows-Task-Manager den Prozess "expecco_ALM.exe", in letzterem Fall wird der Windows-Service-Manager expecco ALM automatisch neustarten.
 - Nun können Sie das expecco ALM Webinterface aufrufen. Es wird eine Seite zum Installieren Ihrer expecco ALM Lizenz angezeigt (Anhang 1). Über "Lizenzdatei installieren" können Sie Ihre Lizenzdatei. auswählen. Nach dem expecco ALM Ihre Lizenzdatei akzeptiert hat, können Sie diese entfernen.

== Einbringen von expecco Floating-Lizenzen ==
Der Lizenzservice von expecco ALM vergibt verfügbare expecco Floating-Lizenzen aus einem bestimmten Pool. 
In diesen zunächst leeren Pool können von eXept erworbene expecco Floating-Lizenzen eingebracht werden.
 
Diese expecco Floating-Lizenzen erhalten Sie als Lizenzdatei(en) üblicherweise per E-Mail. 
Eine Lizenzdatei kann eine oder mehrere expecco Floating-Lizenzen auch für verschiedene Komponenten (Basissystem, Plugins und Erweiterungen) enthalten. 
Sie können auch jederzeit weitere expecco Floating-Lizenzen erwerben und in den Pool einbringen.
 
expecco Floating-Lizenzen werden immer spezifisch für eine expecco ALM Lizenz erstellt und sind nur mit dieser und deren Dongle nutzbar. 
Es ist also nicht notwendig solche Lizenzdateien unter Verschluss zu halten oder über eine sichere Verbindung auszutauschen. 
Allerdings sollten Sie den Dongle sicher aufbewahren bzw. Diebstahl vorbeugen.
 
Zur Einbringen einer expecco Floating-Lizenz öffnen Sie expecco ALM und melden Sie sich an. 
Jetzt navigieren Sie über die obere Hauptnavigationsleiste zum "Lizenzservice" Modul.
 
Sie befinden sich nun im Lizenzservice und Ihnen wird die Liste der installierten expecco Floating-Lizenzen angezeigt. 
Wechseln Sie zur Registerkarte "expecco Lizenzdateien". 
Navigieren Sie mithilfe des Navigationsmenüs auf der linken Seite zu "Hochladen/Upload". 
Hier können Sie nun durch ein einfaches Hochladen Ihrer expecco Floating-Lizenzen selbige in den Pool einbringen. 
In der zuvor genannte Liste werden nun die eben hochgeladenen expecco Floating-Lizenzen anzeigt. 
Diese sind von nun an auch von entfernten expecco Clients abrufbar. 
Sie können auch jederzeit weitere expecco Floating-Lizenzen erwerben und in den Pool einbringen.

== Lizenz Übersicht ==
Welche einzelnen expecco Floating-Lizenzen verfügbar oder vergeben sind, 
erfahren Sie indem Sie zur Registerkarte "expecco Lizenzen" wechseln. 
Insbesondere ist hieraus ersichtlich, welcher Rechner/Benutzer welche expecco Floating-Lizenz aktuell nutzt. 
Dies ist beispielsweise sinnvoll, wenn ein expecco Client seine Sitzung versehentlich nicht beendet hat, 
und andere Nutzer eine entsprechende Lizenz benötigen.

Release Notes 25.x

2025-07-23T07:20:30Z

Alkurz: /* Release 25.1 */

See also: [[Release Notes 24.x]]
 

== Release 25.1 ==
*Improvement: additional "Info" tab in inspector views
*Improvement: less memory usage in the activity log
*Improvement: better error messages and more links to settings from the activity log's error message
*Improvement: additional units and conversions in the [[PhysicalValues/en|physical values framework]]
*Improvement: more precision in the [[Numeric_Limits/en#Higher_Precision_Numbers|high precision trigonometric and math functions]]
*Improvement: WindowsAutomation: Plugin Update to FlaUI 5
*Improvement: Mobile Testing: Better Device Lock/Unlock Support
*Improvement: StandardLibrary: "File [ *CSV ]" blocks got an additional "characterEncoding" pin (useful for reading/writing e.g. utf-8 encoded CSV files)
*Improvement: ExcelLib: better documentation. Now requires the openpyxl package version >= 3.1.5.
*Improvement: better model language editor (translate and fetch-strings functions)
*Improvement: ODBCLibrary: improved compatibility with different database vendors (supports the CedarDB database)
*Feature: translate and spell check in the workspace window
*Feature: EditLock of suites loaded from expeccoALM / AIDYMO
*Feature: Start Test in expeccoALM / AIDYMO (via expecco)
*Feature: new library containing expeccoALM control actions (those from the AIDYMO menu)
*Fix: the version diff viewer (did not correctly copy changed attachment files)

Expecco wiki:Impressum

2025-03-26T07:30:56Z

Alkurz:

eXept Software AG 
Talstr. 3 
74321 Bietigheim-Bissingen 
Germany 

Tel.: +49 7142 91948-0 
Fax: +49 7142 91948-44

E-Mail: info@exept.de 
Internet: www.exept.de

Vorstand: 
Stefan Vogel

Aufsichtsrat: 
Claus Gittinger (Vorsitzender)

Registereinträge: 
Registergericht: Amtsgericht Stuttgart 
Registernummer: HRB 301567 

Umsatzsteuer-Identifikationsnummer: 
DE 178373827 

Haftungsausschluss: 
Die eXept AG distanziert sich in dieser Internetpräsenz ausdrücklich von allen Inhalten, die über Verweise (Links) von dieser Domain aus erreichbar sind, sofern diese Inhalte anstößig oder strafbar sind. Zum Zeitpunkt der Erstellung dieser Seiten war kein Inhalt, auf den von diesem Webangebot verwiesen wird, anstößig oder gar strafbar.

Expecco ALM Einrichten Vorgehensweise

2025-03-13T16:38:45Z

Alkurz: /* Schnellstart */

{{SEITENTITEL:expecco ALM einrichten Vorgehensweise}}

==Vorab Informationen==
Nachdem Sie expecco ALM das erste Mal installiert haben, wird dies mit einer leeren Datenbank hochfahren. Jetzt können Sie expecco ALM entsprechend Ihrer Anforderungen einrichten. Hierzu sollten Sie Ihre Anforderungen genau definieren und auf ein Minimum herunterbrechen. Denn je komplexer Ihre Anforderungen sind, desto mehr müssen Sie sich mit den Konzepten und Funktionsweisen von expecco ALM auseinandersetzen, um auch in der Lage zu sein, diese komplexen Anforderungen in expecco ALM abzubilden.

Selbstverständlich können Sie sich auch gerne an uns wenden und Ihre Anforderungen durchgeben. Unsere Profis werden Ihre Anforderungen bestmöglich auf expecco ALM abbilden und Ihnen das daraus entstandene Setup als Ausgangsdatenbank zukommen lassen.

Definieren Sie Ihre Anforderungen anhand folgender Fragen:
* Was möchten Sie mit expecco ALM alles machen?
* Wie viele Aufgaben und welche soll expecco ALM übernehmen?
* Sollen mehrere Projekte abgebildet werden, oder brauchen Sie gar keine Projekte?
* Müssen den Benutzern verschiedene Rechte pro Projekt zugeteilt werden?
* Haben die Benutzer in allen Projekten die gleichen Aufgaben?
* Ist es überhaupt nötig individuelle Benutzerrechte zu vergeben?
* Dürfen auch Ihre Kunden Sicht in Ihr expecco ALM erhalten, und falls ja, auf welche Felder?
* Sollen die Benutzer von expecco ALM bei der Bearbeitung an Workflows gebunden sein?

==Schnellstart==
Wenn Sie schnell starten wollen, werden minimal benötigt:
* Teilnehmende Personen
:In kleinen Entwicklerteams können Sie auf individuelle Rollenvergabe verzichten und jedes Teammitglied "projektverantwortlich" machen. Damit haben erst einmal alle gleiche Rechte. Oder sie können sie in die Gruppen "Entwickler", "Tester" und "Kunden/Anwender" aufteilen, und dabei letzteren lediglich Zugriff auf Fehler und Anforderungen geben, sie aber vom Testbetrieb ausschließen.
:
:Sie können jederzeit alles später wieder ändern, Personen anderen Gruppen zuteilen oder neue Rechte vergeben.

* Mindestens ein Projekt

==Organisation==
Unter dem Menüpunkt "''Organisation''" legen Sie Personen, Gruppen, Kunden und Orte an;
Bei Bedarf werden hier eigene Rollen und Rechte eingerichtet und eigene Workflows konfiguriert.

Für einen optimalen Start, bearbeiten Sie die Reiter nacheinander von links nach rechts.

===Personen===
Hier werden die Personen mit Vor- und Nachnamen angelegt und erhalten ein Kennwort für den Zugang zum System. Das Kennwort kann jederzeit über "''Einstellungen/Kennwort''" geändert werden.

ACHTUNG: dringend die Kontaktdaten eingeben, über welche der Benutzer seine Benachrichtigungen erhalten soll.

Die Rechte der Benutzer werden unter "''Gruppe''" vergeben.

===Gruppen===
Hier werden Gruppen angelegt und erhalten einen Namen und einen Gruppenleiter.

Im Kasten "''Mitglieder''" werden Ihnen alle Personen angezeigt. Wählen Sie die Gruppenmitglieder aus
und verschieben sie nacheinander mit dem Pfeil nach rechts, es öffnet sich ein Kasten für die Gruppenmitglieder.
Mit einem Klick auf den Namen aktivieren Sie die rechts angezeigten Rollen und können nun so jeder Person ihre Rolle zuordnen.

Eine Person kann Mitglied mehrerer Gruppen sein und in jeder eine oder mehrere Rollen einnehmen: Projektverantwortlicher, Entwickler, Kunde, Tester, etc.
Die Rollen eines Benutzers können für verschiedene Projekte unterschiedlich sein.
Bei Bedarf können unter "''Organisation/Rollen/Anlegen''" eigene Rollen spezifiziert werden.

===Kunden===
Expecco ALM ermöglicht es auch Ihren Kunden eine Sicht auf Projekte oder Teilaspekte davon anzubieten.
Ebenso können Anforderungen und Fehler vom Kunden gemeldet werden. Optional kann expecco ALM auch Serviceleistungen abrechnen, wozu ein Punktesystem ("Servicepunkte") und ein Punktekonto zur Verfügung steht.

Fall Sie dies wünschen, können Sie hier jedem Kunden individuell Zugriff erteilen.

Bei "''Kunden Anlegen''" sollten Sie auch einen Verantwortlichen aus Ihrer Firma und den Ansprechpartner "''Kontakt''" beim Kunden angeben.

In dieser Maske kann ein Servicelevel angegeben und der Kontostand eingetragen werden (falls Sie Servicepunkte abrechnen wollen).
Ist der Kunde angelegt, wird die Menüleiste links aktiviert. Dort finden Sie:

* Liste: die Liste aller Kunden. Die Auswahl der angezeigten Spalten können Sie in dem karierten Fenster (neben dem Filter) auswählen.
* Details: zum Kunden
* Supportpunkte: in der Übersicht können Sie Supportpunkte für einzelen Projekte reservieren.

In der Liste werden die verbuchten Supportpunkte angezeigt.

* Anhänge: hier werden alle hochgeladenen Anhänge aufgelistet.
* Interessenten: hier bestimmen Sie, bei welchen Änderungen Sie benachrichtigt werden möchten.
* Referenzen: Übersicht über alle Artefakte des Kunden - Benutzer, Projekte, Komponenten, Arbeitspakete, Aktionen, Fehler, Anforderungen
* Historie: über alle Änderungen

===Orte===

Anlegen der Orte für Besprechungen, Standorte für Geräte und Rechner.

Wenn Sie über einen größeren Gerätepark verfügen, in dem z.B: Meßgeräte beweglich sind, können Sie damit auch diese verwalten und damit helfen Testaufbauten (sog. "Testbeds") zu beschleunigen. Natürlich lassen sich hier auch beliebige andere Ressourcen lokalisieren (z.B. Fahrzeuge). Bei Bedarf kann die Lokalisierung auch automatisiert werden (z.B. mittels NFC/RFID oder GPS Schnittstellen).

===Kategorien===

Hier werden primär Einträge für Auswahllisten und Attribute für Workflows definiert.

Am besten erklärt sich das an konkreten Beispielen:

* jede Fehlermeldung besitzt ein Feld "Systemtyp", welches das Betriebssystem beschreibt (also "Windows10", "Windows11", "Linux" etc.)
:Die möglichen Werte sind unter der Kategorie "OperatingSystem" zu finden. Alle Einträge darunter scheinen in den entsprechenden Auswahllisten.

* Arbeitsabläufe ("''Workflows''") werden durch den Zustand eines Artefakts definiert. ZB. kann eine Anforderung die Zustände "gemeldet", "angenommen", "in Arbeit", "abgelehnt" etc. annehmen. Je nach Zustand sind unterschiedliche Folgeaktionen möglich bzw. erforderlich, und auch u.U. unterschiedliche Eingabefelder sichtbar oder beschreibbar. Sowohl die Liste der möglichen Zustände (die hier definiert wird) als auch die Zuordnung zu Workflows und sichtbaren Feldern (die an anderer Stelle erfolgt) sind in expecco ALM frei definierbar und änderbar. Bei der Erstinstallation werden einige typische Workflows (for kleine, mittlere und große Unternehmen) mitgeliefert. Diese können so übernommen werden, aber auch individuellen Bedürfnissen angepasst, erweitert oder vereinfacht werden.

Sie können hier die Liste der angebotenen Einträge erweitern, kürzen oder umbenennen. Ebenso können auch eigene Kategorien definiert werden (eg. "Antrieb", "Antrieb/Diesel", "Antrieb/Hybrid", "Antrieb/Elektrisch") und dann als "Customfeld" in einem Artefakt erscheinen.

===Rechte===

===Rollen===

===Workflows===

===Benutzerdefinierte Felder===

==Projekte==

Unter dem Menüpunkt "''Projekte''" legen Sie Projekte und Arbeitspakete (''Releases'') an.

Expecco ALM Einrichten Vorgehensweise

2025-03-13T15:39:54Z

Alkurz:

{{SEITENTITEL:expecco ALM einrichten Vorgehensweise}}

==Vorab Informationen==
Nachdem Sie expecco ALM das erste Mal installiert haben, wird dies mit einer leeren Datenbank hochfahren. Jetzt können Sie expecco ALM entsprechend Ihrer Anforderungen einrichten. Hierzu sollten Sie Ihre Anforderungen genau definieren und auf ein Minimum herunterbrechen. Denn je komplexer Ihre Anforderungen sind, desto mehr müssen Sie sich mit den Konzepten und Funktionsweisen von expecco ALM auseinandersetzen, um auch in der Lage zu sein, diese komplexen Anforderungen in expecco ALM abzubilden.

Selbstverständlich können Sie sich auch gerne an uns wenden und Ihre Anforderungen durchgeben. Unsere Profis werden Ihre Anforderungen bestmöglich auf expecco ALM abbilden und Ihnen das daraus entstandene Setup als Ausgangsdatenbank zukommen lassen.

Definieren Sie Ihre Anforderungen anhand folgender Fragen:
* Was möchten Sie mit expecco ALM alles machen?
* Wie viele Aufgaben und welche soll expecco ALM übernehmen?
* Sollen mehrere Projekte abgebildet werden, oder brauchen Sie gar keine Projekte?
* Müssen den Benutzern verschiedene Rechte pro Projekt zugeteilt werden?
* Haben die Benutzer in allen Projekten die gleichen Aufgaben?
* Ist es überhaupt nötig individuelle Benutzerrechte zu vergeben?
* Dürfen auch Ihre Kunden Sicht in Ihr expecco ALM erhalten, und falls ja, auf welche Felder?
* Sollen die Benutzer von expecco ALM bei der Bearbeitung an Workflows gebunden sein?

==Schnellstart==
Wenn Sie schnell starten wollen, werden minimal benötigt:
* teilnehmende Personen
:Sie können in kleinen Entwicklerteams auf individuelle Rollenvergabe verzichten, und jeden "projektverantwortlich" machen. Damit haben erst einmal alle Teammitglieder gleiche Rechte. Oder auch in "Entwickler", "Tester" und "Kunden/Anwender" aufteilen, und letzteren lediglich Zugriff auf Fehler und Anforderungen geben, sie aber vom Testbetrieb ausschließen.
:
:Sie können alles später aber jederzeit wieder ändern, Personen anderen Gruppen zuteilen oder neue Rechte vergeben.

* mindestens ein Projekt

==Organisation==
Unter dem Menüpunkt "''Organisation''" legen Sie Personen, Gruppen, Kunden und Orte an;
Bei Bedarf werden hier eigene Rollen und Rechte eingerichtet und eigene Workflows konfiguriert.

Für einen optimalen Start, bearbeiten Sie die Reiter nacheinander von links nach rechts.

===Personen===
Hier werden die Personen mit Vor- und Nachnamen angelegt und erhalten ein Kennwort für den Zugang zum System. Das Kennwort kann jederzeit über "''Einstellungen/Kennwort''" geändert werden.

ACHTUNG: dringend die Kontaktdaten eingeben, über welche der Benutzer seine Benachrichtigungen erhalten soll.

Die Rechte der Benutzer werden unter "''Gruppe''" vergeben.

===Gruppen===
Hier werden Gruppen angelegt und erhalten einen Namen und einen Gruppenleiter.

Im Kasten "''Mitglieder''" werden Ihnen alle Personen angezeigt. Wählen Sie die Gruppenmitglieder aus
und verschieben sie nacheinander mit dem Pfeil nach rechts, es öffnet sich ein Kasten für die Gruppenmitglieder.
Mit einem Klick auf den Namen aktivieren Sie die rechts angezeigten Rollen und können nun so jeder Person ihre Rolle zuordnen.

Eine Person kann Mitglied mehrerer Gruppen sein und in jeder eine oder mehrere Rollen einnehmen: Projektverantwortlicher, Entwickler, Kunde, Tester, etc.
Die Rollen eines Benutzers können für verschiedene Projekte unterschiedlich sein.
Bei Bedarf können unter "''Organisation/Rollen/Anlegen''" eigene Rollen spezifiziert werden.

===Kunden===
Expecco ALM ermöglicht es auch Ihren Kunden eine Sicht auf Projekte oder Teilaspekte davon anzubieten.
Ebenso können Anforderungen und Fehler vom Kunden gemeldet werden. Optional kann expecco ALM auch Serviceleistungen abrechnen, wozu ein Punktesystem ("Servicepunkte") und ein Punktekonto zur Verfügung steht.

Fall Sie dies wünschen, können Sie hier jedem Kunden individuell Zugriff erteilen.

Bei "''Kunden Anlegen''" sollten Sie auch einen Verantwortlichen aus Ihrer Firma und den Ansprechpartner "''Kontakt''" beim Kunden angeben.

In dieser Maske kann ein Servicelevel angegeben und der Kontostand eingetragen werden (falls Sie Servicepunkte abrechnen wollen).
Ist der Kunde angelegt, wird die Menüleiste links aktiviert. Dort finden Sie:

* Liste: die Liste aller Kunden. Die Auswahl der angezeigten Spalten können Sie in dem karierten Fenster (neben dem Filter) auswählen.
* Details: zum Kunden
* Supportpunkte: in der Übersicht können Sie Supportpunkte für einzelen Projekte reservieren.

In der Liste werden die verbuchten Supportpunkte angezeigt.

* Anhänge: hier werden alle hochgeladenen Anhänge aufgelistet.
* Interessenten: hier bestimmen Sie, bei welchen Änderungen Sie benachrichtigt werden möchten.
* Referenzen: Übersicht über alle Artefakte des Kunden - Benutzer, Projekte, Komponenten, Arbeitspakete, Aktionen, Fehler, Anforderungen
* Historie: über alle Änderungen

===Orte===

Anlegen der Orte für Besprechungen, Standorte für Geräte und Rechner.

Wenn Sie über einen größeren Gerätepark verfügen, in dem z.B: Meßgeräte beweglich sind, können Sie damit auch diese verwalten und damit helfen Testaufbauten (sog. "Testbeds") zu beschleunigen. Natürlich lassen sich hier auch beliebige andere Ressourcen lokalisieren (z.B. Fahrzeuge). Bei Bedarf kann die Lokalisierung auch automatisiert werden (z.B. mittels NFC/RFID oder GPS Schnittstellen).

===Kategorien===

Hier werden primär Einträge für Auswahllisten und Attribute für Workflows definiert.

Am besten erklärt sich das an konkreten Beispielen:

* jede Fehlermeldung besitzt ein Feld "Systemtyp", welches das Betriebssystem beschreibt (also "Windows10", "Windows11", "Linux" etc.)
:Die möglichen Werte sind unter der Kategorie "OperatingSystem" zu finden. Alle Einträge darunter scheinen in den entsprechenden Auswahllisten.

* Arbeitsabläufe ("''Workflows''") werden durch den Zustand eines Artefakts definiert. ZB. kann eine Anforderung die Zustände "gemeldet", "angenommen", "in Arbeit", "abgelehnt" etc. annehmen. Je nach Zustand sind unterschiedliche Folgeaktionen möglich bzw. erforderlich, und auch u.U. unterschiedliche Eingabefelder sichtbar oder beschreibbar. Sowohl die Liste der möglichen Zustände (die hier definiert wird) als auch die Zuordnung zu Workflows und sichtbaren Feldern (die an anderer Stelle erfolgt) sind in expecco ALM frei definierbar und änderbar. Bei der Erstinstallation werden einige typische Workflows (for kleine, mittlere und große Unternehmen) mitgeliefert. Diese können so übernommen werden, aber auch individuellen Bedürfnissen angepasst, erweitert oder vereinfacht werden.

Sie können hier die Liste der angebotenen Einträge erweitern, kürzen oder umbenennen. Ebenso können auch eigene Kategorien definiert werden (eg. "Antrieb", "Antrieb/Diesel", "Antrieb/Hybrid", "Antrieb/Elektrisch") und dann als "Customfeld" in einem Artefakt erscheinen.

===Rechte===

===Rollen===

===Workflows===

===Benutzerdefinierte Felder===

==Projekte==

Unter dem Menüpunkt "''Projekte''" legen Sie Projekte und Arbeitspakete (''Releases'') an.

Release Notes 24.x

2024-12-09T11:04:12Z

Alkurz: /* Future Release 24.2 (4Q 2024) */

See also: [[Release Notes 23.x]]
 

== Future Release 24.2 (4Q 2024) ==
*Feature: WindowsAutomation: "Mouse Wheel Simulation" support
*Feature: Any and template typed parameters in testcase (of testplan)
*Feature: Negated [[Testplan_Editor/en#Condition_Variables|condition variable]] check
*Fix: Project Difference Viewer showed wrong tab for steps inside the test/demo diagram
*Fix: Exchange connection function of diagram editor left an invisible connection at the pin. Lead to wrong output value forwarding during the current session, but cured itself when saving and reloading.
*Improving the function and operation of variable pins ([[Scheme_Editor/en#Variable_Number_of_Pins|Scheme_Editor/Variable_Number_of_Pins]])
*Fix/Feature: Severity level limit is passed on in sub-test plans with the option of tightening the severity level per test plan level

== Release 24.1 (2Q 2024) ==
*Feature: [[Expecco_API/en#Global_and_Static_Variables|Static Variables for Python]]
*Feature: Qt-Testing: Logging with log levels <code>DEBUG</code>, <code>INFO</code> and <code>WARN</code> ([[Qt_Inject_Windows/en#Logging|Qt-Logging]])
*Feature: Qt-Testing: Qt-Connections now use the ConnectionManager like the other Gui test technologies
*Feature: WindowsAutomation: Native Touch, Tap, Drag & Drop support now in the base WindowsAutomation Library
*Feature: Show Log and [[Timeline/en|Timeline view]] for testplans
*Feature: Search and Goto Line menu functions in the activity log view
*Feature: [[Embedded Systems C Bridge API|C-Bridge]] now supports SSL connections (encryption and authentication using certificates)
*Feature: [[Testsuite_Editor-ExecutionSettings_Editor/en|Settings for execution]] (thread pool and log activities/pins/info) can now be saved in the test suite settings
*Feature: CSV test report, values for start time, end time and duration added
*Feature: Improved refactoring for compound blocks: "Extract (& Replace) New Compound Action"
*Feature: Enhanced expecco reflection library
*Feature: Logprocessors can be executed for embedded testplans
*Feature: Logging of background actions can be individually enabled and disabled for testplans and nested testplans
*Feature: Support for script actions written in the [[Installing_additional_Frameworks/en#Julia_Installation|Julia]] programming language
*Feature: Powershell actions: support functions for writing to pins, logging, opening dialogs, etc.
*Fix: Current temporary testplan settings (like selected testcases, do-not-execute of pre/post action, etc.) don't get lost anymore when reimporting a library
*Fix: WindowsAutomation: Fix blocking of applications after <Mouse Button Down>
*Fix: asynchronous write to an output pin with no wait() in bridged actions are now detected and reported as error (see Example3 in the [[Expecco_API/en#Asynchronous_and_Callback_Functions|NodeJS API Documentation]])
*Fix: Bridges: Detect (and ignore) invalid requests from forked background bridge threads
*Fix: Acitivity logs of asynchronous events in background actions are now displayed correctly in the background activity log.
*Fix: Qt: Drag and drop improved by revising the "Move mouse event" (Windows)
*Fix: Disabling logs of sub-activities (if successful, if not successful, etc.)

Release Notes 24.x

2024-11-06T16:09:57Z

Alkurz: /* Future Release 24.2 (4Q 2024) */

See also: [[Release Notes 23.x]]
 

== Future Release 24.2 (4Q 2024) ==
*Feature: WindowsAutomation: "Mouse Wheel Simulation" support
*Feature: Any and template typed parameters in testcase (of testplan)
*Fix: Project Difference Viewer showed wrong tab for steps inside the test/demo diagram
*Fix: Exchange connection function of diagram editor left an invisible connection at the pin. Lead to wrong output value forwarding during the current session, but cured itself when saving and reloading.
*Improving the function and operation of variable pins ([[Scheme_Editor/en#Variable_Number_of_Pins|Scheme_Editor/Variable_Number_of_Pins]])

== Release 24.1 (2Q 2024) ==
*Feature: [[Expecco_API/en#Global_and_Static_Variables|Static Variables for Python]]
*Feature: Qt-Testing: Logging with log levels <code>DEBUG</code>, <code>INFO</code> and <code>WARN</code> ([[Qt_Inject_Windows/en#Logging|Qt-Logging]])
*Feature: Qt-Testing: Qt-Connections now use the ConnectionManager like the other Gui test technologies
*Feature: WindowsAutomation: Native Touch, Tap, Drag & Drop support now in the base WindowsAutomation Library
*Feature: Show Log and [[Timeline/en|Timeline view]] for testplans
*Feature: Search and Goto Line menu functions in the activity log view
*Feature: [[Embedded Systems C Bridge API|C-Bridge]] now supports SSL connections (encryption and authentication using certificates)
*Feature: [[Testsuite_Editor-ExecutionSettings_Editor/en|Settings for execution]] (thread pool and log activities/pins/info) can now be saved in the test suite settings
*Feature: CSV test report, values for start time, end time and duration added
*Feature: Improved refactoring for compound blocks: "Extract (& Replace) New Compound Action"
*Feature: Enhanced expecco reflection library
*Feature: Logprocessors can be executed for embedded testplans
*Feature: Logging of background actions can be individually enabled and disabled for testplans and nested testplans
*Feature: Support for script actions written in the [[Installing_additional_Frameworks/en#Julia_Installation|Julia]] programming language
*Feature: Powershell actions: support functions for writing to pins, logging, opening dialogs, etc.
*Fix: Current temporary testplan settings (like selected testcases, do-not-execute of pre/post action, etc.) don't get lost anymore when reimporting a library
*Fix: WindowsAutomation: Fix blocking of applications after <Mouse Button Down>
*Fix: asynchronous write to an output pin with no wait() in bridged actions are now detected and reported as error (see Example3 in the [[Expecco_API/en#Asynchronous_and_Callback_Functions|NodeJS API Documentation]])
*Fix: Bridges: Detect (and ignore) invalid requests from forked background bridge threads
*Fix: Acitivity logs of asynchronous events in background actions are now displayed correctly in the background activity log.
*Fix: Qt: Drag and drop improved by revising the "Move mouse event" (Windows)
*Fix: Disabling logs of sub-activities (if successful, if not successful, etc.)

Scheme Editor/en

2024-11-06T16:06:15Z

Alkurz: /* Variable Number of Pins */

[[Bild:Schema Editor.png|thumb|300px|Schema Editor]]
The schema editor is used to define the external interface and some other attributes of an action block (both [[ ElementaryBlock_Element/en | elementary]] and [[ CompoundBlock_Element/en| compound]] actions).
It is found on the "''Schema''" tab after selecting either an elementary or a compound action in the navigation tree.

The block's interface consists of the input and output pins and its trigger behavior.
The editor shows a box representation of the action, where inputs are located on the left, outputs on the right. This is the "outside view" of the action; i.e. the action's look when placed as a step in a diagram.

To the right, you see an example for the interface of a action with a single [[DiagramElements-Pin#Input Pin|input pin]] (in) and a single [[DiagramElements-Pin#Output Pin|output pin]] (out). In a network, a step with this action will trigger when all connected input pins have received a value ("''AndConnected''" trigger condition).

Schema editors can also be invoked on actions that are write protected, e.g. actions from imported libraries, such as the standard library or your own block libraries.
Such components cannot be modified, but they can however be shown and inspected by the editor.

== Pins ==
=== Adding & Removing [[DiagramElements-Pin|Pins]] ===
New input and output pins can be added using the icon buttons in the top corners of each side of the action's representation box ([[Bild:Icon Add Inputpin.png]] / [[Bild:Icon Add Outputpin.png]]). Existing inputs and outputs can be removed using the icon buttons directly beside the buttons for adding ([[Bild:Icon Remove Pin.png]]), but a pin has to be selected for this operation first. Please note that some builtin blocks, like shell command blocks, have a fixed set of pins which can not be removed.

When new pins are added, they get default names attached with a sequential number, like ''in1'', ''in2'', ''out1'', ''out2'', etc.

=== Special Pins ===
Some actions (i.e. script and bridged execution actions) support additional special pins, with a predefined (and hardcoded) functionality. For script actions, these are used to provide the execution directory, environment variables, standard input, exitCode handling and output line buffering options.
For bridged actions, these provide the bridge connection handle and/or script interpreter handle on which the script is to be executed.

Special pins are added with the "''Special Pins''" menu, and removed by selecting the pin and deleting it (via key or menu).

These special pins are described in [[DiagramElements-Pin/en#Special_Pins_of_Script_Action_Blocks | "Special Pins of Script Action Blocks"]], [[DiagramElements-Pin/en#Special_Pins_of_Bridged_Action_Blocks | "Special Pins of Bridged Action Blocks"]] and also in [[Expecco_Scripting_API | "Expecco Scripting API"]]

[[Datei:NotBeginner.png|20px]]Note: these menu items are not shown if your experience setting is "''Beginner''". Go to the "''Settings''" - "''Look & Feel''" - dialog to change your experience setting.

=== Renaming of Pins ===
The name of a pin can be changed (*) by clicking on the name field, which then turns into an input text field. There, type in a new name for the pin. The pin will be renamed when either the <kbd>Enter</kbd> key is pressed, or the input field is left (i.e. clicking on any other element in the editor).
The <kbd>Escape</kbd> key cancels the rename operation.

For a subset of the supported programming languages, the editor will rewrite the code to use the new name.

(*): except for special pins which cannot be renamed.

===== Restrictions on Pin Naming for Elementary Blocks =====
In elementary blocks, pin names are not only used for description purpose but also to access the pin's value in the action's source code (i.e. for actions written in a textual programming language). Therefore, some naming restrictions apply to ensure that the pin name represents a valid identifier in the block's code (i.e. it must be a valid variable identifier in the programming language of the action's code, which can be JavaScript, Smalltalk, Groovy, Python, C etc.).

In practice, the identifier should be a sequence of letters, digits or the underline character (_), where the very first character should not be a digit. It may also not be a keyword of the language (i.e. "<code>function</code>" in Groovy, "<code>if</code>" in JavaScript or "<code>self</code>" in Smalltalk).

Such restrictions do not apply to compound blocks; however, if you ever plan to convert or generate elementary code, it is a good idea to restrict your naming there too.

===== Restrictions on Pin Naming for JavaScript and Groovy Elementary Blocks =====
The syntax of those two languages contains a much larger number of language keywords, which cannot be used as identifier. For example, "<code>if</code>", "<code>while</code>", "<code>for</code>" and "<code>in</code>" are all reserved words in those languages and cannot be used. Otherwise, a syntax error will be reported when code is entered.

It is a good practice to name pins as "''inPin1''" or "''textPin''" or "''xxxPin''" in general, to avoid such conflicts right from the beginning. Such naming convention also make the code more readable, as it reduces chances for confusing the name of a pin with a name of a variable used for a pin's data value (remember: in the code, the pin-name refers to the pin - not the pin's value).

===== Restrictions on Pin Naming for Other Languages =====

Similar restrictions apply to the other supported languages (Python, C, etc.).

=== Edit Functions for Existing Pins ===
For all other pin operations, the pin to be modified has to be selected first.

To select a pin, click on it with the left mouse button.

You can select multiple pins: keep the <kbd>Ctrl</kbd> key down while clicking, to toggle the pin into or out of the selection. Press the <kbd>Shift</kbd>-key while clicking to select all pins in between the previously selected pin and the clicked-on pin.
You can also select multiple pins with a rectangle-drag operation (click outside, keep holding the mouse button, and drag to the other corner, to select all pins inside the rectangle).

The selected pin(s) will appear highlighted in a red color.

To open the context menu for a pin or group of pins, first select the pin(s), then press the right mouse button. The context menu provides additional pin related functions. Since input and output pins have slightly different properties, their context menus are different and described below.

=== Setup / Change Datatype ===
Each pin has a [[Datatype|data type]] attribute that determines which kind of data is expected or generated by the pin. Every new pin initially gets the data type that was last used; initially the [[Datatype#General_Types|data type "Any"]] is assigned by default. This type is also used as default, whenever no other reasonable data type can be predicted. The pin's data type is displayed beside the pin, outside of the representation box. The data type for a pin can be changed in the context menu, through its "''datatype''" sub-menu, which brings up a list of available types.

Note that when you have already placed [[DiagramElements-Step|step]] instances of the modified action block in any activity diagram, a change in the data type of a pin may affect existing connections in which the pin is involved. If the new type is incompatible with a connection, it is drawn as dotted line in the diagram, or when a preset value becomes incompatible, the value is displayed in a red color.

=== Default Values for Pins ===
Default values for unconnected step-pins can be defined here, by "''freezing''" a pin in this schema editor. Both constant-value and environment-freeze values are possible.

=== Pin Specific Options (Context Menu) ===
[[Bild:Icon Input Desc.png|thumb|328px|Input Pin Options]]

[[Bild:Icon Output Desc.png|thumb|278px|Output Pin Options]]

;Undo
:Undo last change(s). The text shown after the word "''Undo''" (in parentheses) is the name of operation that will be undone.

;Copy Pin
:Copy all attributes from selected pin.

;Remove Pin
:This option simply removes the selected pin.

;Datatype
:This option is used to specify the [[Datatype Element/en|data type]] of the selected pin. This brings up a list of the available data types.

;Default Value Editor
:This option allows you to specify the editor type for the freeze value, e.g. strings can be entered single line, multi-line or as a password string.

;Show Datatype
:This option opens a view which shows the pins data type. Note that you can not change the datatype in this view.

;Default Value As
:This option allows, for most standard data types, presetting the input value according to the data type, by typing a valid value into a text input field. The identifier of the data type in the menu entry differs depending on the data type of the pin. A freeze value defined in this schema defines the input value of unconnected step-pins. It will only be in effect, if the action is placed as a step and the corresponding step-pin is not connected or frozen.

;Default Value from Clipboard
:Freeze pin with the data stored in the clipboard.

;Default Value from Environment Variable
:This option causes a dialog to open up, allowing specifying the environment variable's name in a text input field. For more information see: [[Environment Freeze Value]]. This freeze value is only effective for unconnected step pins (read description above).

;Delete Default Value
:This option is only available if the selected pin is frozen to a value or to an environment variable. No matter if the pin was preset with a direct value or with an environment variable, the preset information will be lost.

;Parameter (Non Consuming;Non Triggering)
:This option determines whether the select input pin is a parameter pin. For more information see: [[DiagramElements-Pin#Input Pin Trigger Attributes|Diagram Elements]].

;Telegram (Non Consuming;Non Triggering;Deliver While Executing)
:This option determines whether the selected input pin is a telegram pin. For more Information see: [[DiagramElements-Pin#Telegram Pin|Telegram Pin]].

;Buffered
:This option sets the buffering mode of the selected output pin to on or off. For more information see: [[DiagramElements-Pin#Output Pin|Diagram Elements - Output Pin]]

;Special Attributs
:A submenu offering additional functions (see below)

;Comment
:This option causes a text editor to open on the pin's comment. That comment will be displayed as a tooltip of the selected pin.

;Move Up/Down
:With those options you can change the sequence of the pins.

====Special Attributes====
=====Input Pins=====
The input pin behavior can be controlled in more detail here. Individual control of the triggering/non-triggering, consuming/non-consuming and
buffered/passed-through attributes is offered here.

;Consuming / Non-Consuming
:This option determines whether the input pin consumes its input value from the input basket or leaves it. Non-consuming pins are sometimes required, when the step is executed in a loop, and the input value should be reused for each iteration. Also, frozen parameter pins should be defined as non-consuming, as otherwise, the freeze value is only available once (in the first loop iteration).
:More info in: [[DiagramElements-Pin#Consuming_vs._Non-Consuming | Diagram Elements-Pin]].

;Triggering / Non Triggering
:This option determines whether the input pin is considered in the action triggering process or not. Triggering pins must have a value present in order for an activity to be created. Non-triggering pins are not.
:More info in: [[DiagramElements-Pin#Input_Pin_Trigger_Attributes | Diagram Elements-Pin]].

; Mailbox / Non-Mailbox (also called "''Telegram Pin''")
:This option determines whether the selected pin is a telegram pin. Normal pins "latch" their input value when the action is triggered and provide that value to internal steps (be aware, that it might be consumed). If another value arrives at the pin while it is beeing executed, another activity will be started to process the next value.
:Mailbox pins behave differently: any value arriving there will be forwarded to inside connected steps. Mailbox pins are most useful to implement a controlled cancel operation (eg. by setting a variable inside, which stops a loop).
:For more Information see: [[DiagramElements-Pin#Telegram_and_Mailbox_Pins| Diagram Elements-Pin]].

=====Output Pins=====
;Buffered / Unbuffered
:Buffered outputs will send their value(s) when the action has finished with success. Unbuffered outputs will send any value immediately (and thus may trigger other actions while this action is still executing).
:For more Information see: [[DiagramElements-Pin/en#Output_Pin_Buffer_Attribute| Diagram Elements-Pin]].

=====Variable Number of Pins=====

An input and output pin can be specified as a "variable pin". Such a pin appears in the block description (the schema) as a single pin, but it can be instantiated multiple times in one step. In other words, the number of these variable pins can be defined individually for each step. Variable pins are marked with a small plus sign.

Variable pins can only be the last pins, which are combined into a variable pin group. This pin group can be "replicated" in steps as often as required. Individual pins within a group can have different data types, and the replicated pins adopt the data type of their corresponding pin from the schema definition of the action. This is very useful for defining “multi-key-value” groups, e.g. for multi-setter actions of collections or user data objects.

'''This option is only possible for elementary actions and the elementary code must be written to access these pins with a pin index.'''

;Defining the variable pin group

:In the context menu of a pin, the start of the variable pin group can be set via the sub menu <code>Special attributes</code> - <code>Start Variable Pin Group here</code>. The selected pin and the following pins become variable pins, the pins before them become or remain fixed pins.

:This function can also be used to subsequently move the start of the pin group.

;Remove the variable pins.

:Context menu of a variable pin via the sub menu <code>Special attributes</code> - <code>Convert all Variable Pins to Fixed Pins</code>: This converts all variable pins to fixed pins.

;Equal Number of Variable Input and Output Pin Groups

:If a variable pin group is defined in the input and output pins, the number of pin groups can be synchronized. The number of replications of the input and output pins is the same. 
:<code>Special attributes</code> - <code>Equal Number of Variable Input and Output Pin Groups</code>

See also in [[DiagramElements-Pin/en#Variable_Number_of_Pins | Diagram Elements-Pin - Variable Number of Pins]].

== Action ==
To open the context menu for an action, select the box representation of the action, then press the right mouse button. The context menu supports the following functions.

=== Changing Triggering Conditions ===
The triggering condition of an action block defines which input pins must have received data on order for a new activity to be triggered and started. The so called "''triggering condition''" can be:

;ANDConnected (Default)
: All connected input pins which are "''triggering''" must have received data - unconnected pins are ignored.
;AND
: All triggering input pins must have received data.
;OR
: At least one triggering input pin must have received data.

Previous versions of expecco showed a (discussable wrong) behavior when a step had the autostart flag set AND an enable input pin with no value provided.
This behavior will be set when an old (pre 19.2) suite is loaded to remain backward compatible, but it will be displayed as:
;AND (old behavior)
: Same as AND, but will start with autoStart and enablePin present.
;OR (old behavior)
: Same as OR, but will start with autoStart and enablePin present.

The most common trigger condition is ''''AndConnected''''. The ''''Or'''' condition allows for a step to be activated whenever any input arrives on any of its pins. It is especially useful to handle events or input data coming from different sources (i.e. a demultiplexer action).

You can also change the triggering conditions by a left click on the trigger-condition field
(located at the top left of the block) and select one of the conditions.

New in the 2.8 version of expecco: The default triggering condition for new compound action blocks is "''And''", and "''AndConnected''" for all other (elementary) actions. It used to be "''AndConnected''" for all action blocks in previous versions.

=== Renaming of Actions ===
An action can be renamed either using the context menu option or rename the action in the project menu. The name of the action in project tree and the Scheme editor are identical. 
The rename of an action will also rename all already placed [[DiagramElements-Step|step]] instances of this action containing the previous (original) action name. If a step was renamed itself, the step will keep its name.

=== Action Specific Options (Context Menu) ===
;Undo
:Undo last change(s).

;Rename
:Open an inplace editor within the headline of the representing box for the action. Initially the current name of the action is selected and the editor will replace the current name with the new name. On lost focus (enter, cursor down, mouse click) the changes will be saved. Cancel editing without saving the changes can be done by pressing the "<kbd>ESC</kbd>" key.

;Copy Pin Interface
:Copy all pins (input/output) with all attributes

;Paste Pin Interface
:Paste a previous copied pin interface

;Paste Pin
:Paste a previous copied single pin (see pin context menu)

;Trigger Condition
:[[#Changing Triggering Conditions | see Changing Triggering Conditions]]

;Role in Load and Performance Tests
:These settings are also not yet used. They are only effective for load and performance tests, which are not yet officially released.

;Semantic Attributes
:[[#Declaring Semantic Attributes | see Declaring Semantic Attributes below]]

;Execution Debugging Attributes
:[[#Execution Debugging Attributes | see Execution Debugging Attributes below]]

;Attributes
:Open an editor to define the background and frame color besides the tag and name settings for this action.

== Declaring Semantic Attributes ==
The block's pop up menu also allows for a number of semantic attributes to be defined for the action.

Currently, semantic attributes are:

;Blocking (Immediately Start new Activity Process)
:Tells the executor, that this action may block for a noticeable time; for example if it reads from an external stream (typically a socket), or by opening a user-dialog, or by waiting for some other external event. By default, the executor will wait for some grace period and then start another execution thread to continue processing other action blocks. However, this grace period may be too long (a few seconds, by default) and the overall execution time may be shortened, if this is done immediately. Of course, this only makes sense if it is known in advance, that this action will block the executor, and that there might be other activities to be executed in parallel. It also only makes sense if the time it takes to start another execution thread (which does involve some overhead) is shorter than the expected wait time. Notice also, that this flag can also be set for individual steps - and it is usually a better place to set this flag.

;Operator Required
:Informational flag that the action needs operator assistance. Please set this flag if a containing action opens a UI dialog, or otherwise needs an operator assistance. This will help to identify test cases which can be run without operator assistance. You can find blocks with inconsistent "''Operator required''" setting in the "''Special''" test suite search. If the "''Operator Needed''" Flag missing option is enabled all those blocks will be listed. The operator required flag can be validated against a test case's "''Operator Required''" flag, which is actually used by QM systems to effectively schedule tests which require human personal.

Except for the previous "''Blocking''" and "''Operator Required''" attributes, the following are only relevant for the error checker and the code generator (which is not yet officially released).
When set, these flags allow for the error checker to make more specific tests and the code generator / executor to optimize the execution speed of the action.

;Functional
:Hint for the code generator, and the execution engine, that the action's code is purely functional. This means, that the output value(s) only depend(s) on the input value(s), and that neither the input values themselves nor any other global data is modified by any side effect. Purely functional blocks can be executed in parallel without a need for synchronization.

;Modifies an Input Object (Side Effect)
:Hint for the code generator and executor, that the action's code is modifying any of its input values. This means basically, that probably no other step which possibly uses this value should execute concurrently.

;Modifies an Object or External State (Side Effect)
:Hint for the code generator and executor, that the action's code is modifying any object. This means basically, that probably no other step at all should execute concurrently.

;Writes all Output(s) exactly Once
:Hint for the code generator, that the elementary code writes all of the output pins, but only once. This allows for the code generator to eliminate any data queues along the output connections, and pass these values to follow up action code as a function call; effectively allowing for faster execution.

;Writes any Output exactly Once
:Hint for the code generator, that the elementary code writes any of the output pins, but only once. This also allows for the code generator to generate shorter, more efficient code.

;May write an Output more than Once
:Hint for the code generator, that the elementary code may write any of the output pins more than once. The code generator will create data queues for the output pins. Also, the error checker makes use of this flag, when looking for input values being consumed in a loop or consumed multiple times even if only written once.

Notice: these flags should only be set if you know what you are doing and how the elementary code behaves. In a future version, a more advanced code analysis might be added, which may make these flag settings obsolete. If in doubt, leave these flags unchanged (the worst thing that happens in this case, is that any generated elementary code executes slightly slower, and that the error checker finds less errors).

== Execution Debugging Attributes ==
The debug submenu allows for additional debug checks to be defined for the action:
;Assert Executed
:Adds a check to the executor, that any step of this kind must be executed if present inside a compound action's diagram. If a compound action which has such a step in its activity diagram, finishes execution and that step was not executed, an error is reported. Use this, to ensure that verifying actions which are placed into a diagram are certain to be executed (i.e. not skipped due to missing data)

;Assert Executed within Time
:Adds a check to the executor, that any step of this kind must be executed within a given time limit. This has the same effect as the time limit pin at a concrete step; however, it allows for a global upper limit to be set eg. on UI actions, on protocol actions (transmission or connection times) without a need to add it to each of its steps separately.
:If a step has a time limit input, the value there takes precedence over any default value specified here.

;Assert Any Output Written
:Adds a check to the executor, that steps of this kind must generate a datum on at least one of its output pins. If a compound action which has such a step in its activity diagram, finishes execution and that step did not generate at least one output value, an error is reported.

;Assert All Outputs Written
:Adds a check to the executor, that steps of this kind must generate a datum on every of its output pins. If a compound action which has such a step in its activity diagram, finishes execution and that step did not generate output values for every output pin, an error is reported.

Notice that these flags can also be set on a per-step basis. The settings here will be ored with the flag settings of individual steps.
(i.e. the check will be done if either the block, OR the individual step has the flag set.

== Adding Pre- and Post Actions ==
[[CompoundBlock Element|Compound blocks]] can have pre- and post-actions. The pre-action block will be executed each time the owning block is triggered; the post execution block is executed after the owning block is finished, but not if a pre-action was present and that pre-action failed. This can be useful e.g. to allocate and/or release resources.
To add a pre- or post-action, drag and drop any action from the navigation tree into the corresponding field at the bottom. Please note that these blocks cannot not have input pins.

== Advanced and Expert Settings ==

=== Defining the Implemented Interface ===
A [[VirtualBlock Element|virtual action]] defines the interface (number of pins and their datatypes) of an action, but not its implementation. They can be placed into a network like any other action. 
At execution time, a real (concrete) action must be provided for it, either explicitly, via a performer input pin, or implicit, via an imported library which contains a concrete action which implements that virtual action.
The "''Interface''" field at the bottom of the editor assigns such an interface to a concrete action, and specifies that the edited action is able to play that virtual action's role.

[[Datei:NotBeginner.png|20px]]Note: this field is not shown if your experience setting is "''Beginner''". Go to the "''Extras''" - "''Settings''" - "''Look & Feel''" - dialog to change your experience setting.

=== Add / Remove / Test Action User Interface (Action-UI) ===
You can specify a graphical user interface (UI) for an action. If defined, that UI will be displayed as long as the action is executed during a test run. The action can communicate with the UI using environment variables. The environment variables will be created by the [[GUI Editor-GUICode Editor|UI Editor]] during creation / editing the UI.

[[Datei:NotBeginner.png|20px]]Note: this field is not shown unless your experience setting is "''Expert''". Go to the"''Extras''" - "''Settings''" - "''Look & Feel''" - dialog to change your experience setting.

== Keyboard Shortcuts ==

* '''<kbd>Ctrl-i</kbd>''' - "''New InputPin''". Adds a new input pin - same as clicking on the "''Add Input Pin''" button.

* '''<kbd>Ctrl-o</kbd>''' - "''New OutputPin''". Adds a new output pin - same as clicking on the "''Add Output Pin''" button.

==== If a Pin is Selected ====

* '''<kbd>Ctrl-n</kbd>''' - "''New Pin''". Adds a new input or output pin, depending on the currently selected pin's type.

* '''<kbd>Ctrl-e</kbd>''' - "''Environment''". Opens a dialog to adds an environment-freeze (the value is read from a variable, if the pin is unconnected)

* '''<kbd>Ctrl-p</kbd>''' - "''Parameter''". Toggles the "''is parameter pin''" attribute of the pin

* '''<kbd>Ctrl-d</kbd>''' - "''Datatype''". Opens the datatype selection menu for the pin

== See Also ==

[[Code_Editor/en | Code Editor]]

[[ElementaryBlock_Element/en|Elementary Action]], [[CompoundBlock_Element/en|Compound Action]]

For the programmer API for the builtin languages see: [[Expecco API]];
 
sections of interest are the [[Expecco_API/en#Pin Functions | Pin-API ]], [[ Expecco_API/en#Current Activity | Activity-API ]]

[[Category: Editors]]

Was ist expecco?

2024-08-01T10:02:05Z

Alkurz: /* Konzept */ Schreibfehler

== Übersicht ==

=== expecco + expecco ALM = AIDYMO ===

expecco ist die Komponente innerhalb der AIDYMO Werkzeugkette, welche der Entwicklung und Ausführung von Automatisierungen (und damit auch Tests) dient. expecco ist eine "''Native Client''"-Anwendung, welche entweder auf dem Rechner des Testentwicklers oder Testers läuft, oder als "''Test-Ausführungs-Knecht''" in einer (möglicherweise virtualisierten) Serverfarm oder einem Docker Container installiert wurde. Mit expecco werden Testpläne in einer Testsuite definiert und ausgeführt.

expecco ALM ist eine Serveranwendung mit Webbrowseroberfläche, welche für die Verteilung und ordentliche Ausführung der Automatisierungsaufgaben und Tests innerhalb der Serverfarm sorgt, Testressourcen verwaltet und Nutzungskonflikte vermeidet, Testsuiten und Resultate archiviert und versioniert, den Projektfortschritt beobachtet und berichtet, Benachrichtigungen verschickt etc.
Mit "expecco ALM" werden Testläufe automatisch auf "Ausführungs-Knechte" im lokalen Netz oder in einer Cloudumgebung zur Ausführung gebracht und die Resultate abgeholt und archiviert.

Sowohl expecco als auch expecco ALM sind eigenständige Produkte, welche gesondert bestellt, installiert und eingesetzt werden können, doch im Zusammenspiel realisieren sie eine vollautomatisierte Ausführung und Qualitätskontrolle. Beide zusammen werden unter dem Namen AIDYMO vertrieben.

=== expecco Basissystem (Plattform) ===
expecco ist ein [[expecco Architecture | modulares System]], welches aus einer Basisplattform sowie Erweiterungen ("''Plugins''") besteht. Plugins realisieren domänenspezifische Funktionen und Anbindungen (z.B. Anbindungen an spezielle Hardware, Protokolle oder UI-Technologien).

Das Basissystem umfasst:
* Laden und Speichern von Projekten (aka. Testsuiten oder Automatisierungen)
* Anlegen, Bearbeiten und Pflege von Projekten
* Ausführung
* Entwicklung mit Singlestep, Breakpoints, Ausführung von Teilsequenzen
* Inspektoren / Betrachter für verschiedene Datenformate
* Entwicklung mit "Live changes while the system runs" (i.e. Hotswap von Code, kurze Turnaround Zeiten)
* Debugging auf hoher (Diagramm-) als auch auf niedriger (Script/Code) Ebene
* Nahtlose Integration verschiedener Programmiersprachen wie Java, Node.JS, Python, C/C++ u.a.m.
* Beobachtung der Ausführung, Sammeln von Trace-, Zeit- und Logdaten
* Sammeln aller Datenflüsse, Nachrichtenpakete und Zwischenergebnisse zur späteren Inspektion
* Reportgenerierung als Mensch- und Maschinenlesbare Dokumente in verschiedenen Formaten
* expecco ALM Schnittstelle zu unserem eigenen QM Produkt (up/down load von Projekten, Logdateien, Resultaten und Reports)

Die Ausführung kann sowohl unter Aufsicht und Kontrolle eines Bedieners, als auch komplett unbeobachtet erfolgen. Ersteres wird typischerweise bei der Testentwicklung, letzteres in der Produktionsumgebung der Fall sein, wenn die Tests automatisiert zum Ablauf kommen.

Die automatisierte Ausführung kann durch die Kommandozeile oder durch entfernte Rechner via SOAP, REST oder von einem Mobilgerät bzw. einer Weboberfläche initiiert und kontrolliert werden.
Somit kann die Ausführung auch per cron-Job (Unix), scheduled tasks (Windows), Jenkins oder beliebigen anderen Programmen angestossen werden.

Das Basissystem enthält:
* expecco IDE
* Bibliotheken - (Standard, ODBC, XML, uam.)
* Webtest - Browserautomatisierung (Selenium, Webdriver, HTML5, Smart GWT, etc.) für Firefox, IE, Safari, Opera und Chrome Browser
* Manuelle Tests - (Benutzergeführter Testablauf)
* Ports - seriell/USB/parallel
* Anbindungen - (DLL, CSV, etc.)
* Webservices - (REST, SOAP, RPC)
* JavaBridge - (Java Code ausführen sowie Code Injection in Java Programme)
* .NETBridge - (DotNET Code ausführen)
* NodeJS Bridge ab v19.1 (Node/Javascript Code ausführen)
* Python Bridge ab v19.2 (Python und Jython Code ausführen)
* C Bridge ab v22.1 (C und C++ Code ausführen)
* Automatischer Report
* Remote Control ab v23.1 (Kontrolle via Browser, Android oder IOS)

expecco ist modular aufgebaut – das Basissystem kann jederzeit durch Plugins erweitert und an Ihren individuellen Bedarf oder an den Projektfortschritt angepasst werden.

=== Plugins ===
Erweiterungen ("''Plugins''") realisieren die Schnittstellen zu verschiedenen UI-Technologien, zu Hard- und Software Schnittstellen, Protokollen sowie Dokumentformaten. Diese Plugins sind z.T. im Basissystem enthalten oder können nach Bedarf bestellt werden. Es ist auch möglich, eigene Plugins zu erstellen.

Zum Beispiel:
* "Mobile Testing Plugin" für Apps unter iOS und Android
* GUI Testing für Java-Swing, SWT und andere Java UI-Frameworks
* GUI Testing für Windows Anwendungen (Windows Automation / UI-Automation)
* GUI Testing für Qt und andere C/C++ basierte UI-Frameworks
* GUI Test von VisualWorks Anwendungen
* GUI Test via VNC
* Schnittstellen zu CAN-Bus Systemen wie CANoe (Automotive)
* Schnittstellen zu SomeIP Brokern / Klienten (Automotive)
* Schnittstellen zu EDIFACT und SWIFT Systemen (B2B, Finance)
* Schnittstellen zu MQTT und OPC Systemen (Manufacturing, Internet of Things, Automotive)
* Integration und Ausführung von Functional Mockup Units (FMU)
* Import von Testspezifikationen (z.B. aus Excel- oder Word-Dokumenten)
* Schnittstellen zu spezifischen Laborgeräten (Telekom/Automotive)

Typischerweise bestehen Plugins aus zusätzlichen dll- und Blockbibliotheken, welche domänenspezifische Funktionen als "ready-to-use" Bausteine beinhalten. Diese werden dann mit drag & drop in die Testsequenzen eingefügt. Die GUI Plugins beinhalten zusätzliche Recorderfuntionen so dass Benutzerinterationen (z.B. mit einem Mobilgerät) als ablauffähiges Aktionsdiagram aufgezeichnet werden können.

Andere Plugins dienen der Integration in eine existierende QM Infrastruktur:
* Polarion Plugin, um Tests im Polarion ALM System zusammenzustellen und mit expecco zu automatisieren
* Quality Center Plugin als Schnittstelle zu HP-QC
* Jira Plugin, um nach Testläufen Jira-Issues automatisch anzulegen bzw. zu aktualisieren

=== Verfügbarkeit ===

expecco und expecco ALM sind verfügbar für Windows und Linux Systeme, sowohl als 32bit als auch als 64bit Version. Eine Version für macOS (64bit) ist in der Beta Testphase und auf Anfrage verfügbar. Versionen für Solaris und andere Unix Systeme können ebenfalls auf Anfrage bereit gestellt werden.

=== Lizenzierung ===

Lizenzen für expecco sind verfügbar als Einzelplatz (Nodelock oder Dongle), Floating (mit Hilfe eines Lizenzmanagers/Lizenzservers) oder als Firmenlizenz.
expecco kann (mittels Einzelplatz- oder vom Lizenzserver ausgelöster Lizenz) in isolierten Umgebungen, ohne Zugang zum Firmennetz oder Internet eingesetzt werden.

Zu Preisen, Rabattstaffeln und Konditionen kontaktieren Sie bitte eXept.

== Architektur ==

Im Prinzip ist expecco ein "Black Box" Testsystem, welches keine Instrumentierung des getesteten Systems ([[Glossary/en#SUT_.28System_Under_Test.29|SUT = "System Under Test"]]) erwartet oder benötigt (d.h. es ist nicht notwendig, das [[Glossary/en#SUT_.28System_Under_Test.29|SUT]] mit speziellem Code zu erweitern oder spezielle Bibliotheken dazu zubinden).
Es ermöglicht aber "code injection" bei Java-, .NET- und PythonAnwendungen, wodurch "Grey Box" und "White Box" Tests ebenfalls unterstützt werden.

Testszenarien können in expecco sowohl auf einer hohen Abstraktionsebene als (Aktivitäts-) Diagramme, als "Keyword-Driven" Testsequenzen oder als textuelle Skripte in verschiedenen Programmiersprachen formuliert werden. Skripte können sowohl in expecco selbst, als auch im [[Glossary/en#SUT_.28System_Under_Test.29|SUT]] oder anderen Maschinen ausgeführt werden (z.B. um das SUT zu stimulieren, oder um Last zu generieren).

Folgendes grobes Architekturbild gibt dazu eine Übersicht (nicht alle verfügbaren Plugins sind darin enthalten):

[[Datei:expeccoArchitecture1.png|1000px|thumb|left|expecco Architektur (nicht alle Plugins dargestellt)]]

(oder als PDF: [[Datei:expeccoArchitecture1.pdf]])

== Konzept ==
Die Grundphilosophie von Expecco ist, dass Testabläufe sowohl von Entwicklern und Programmierern, als auch von Domänenexperten und Analysten erstellt, gewartet und ausgeführt werden können,
ohne dass dazu spezielle Programmierkenntnisse notwendig wären.
Dabei darf es aber keine Einschränkungen geben, und ein erfahrener Nutzer hat alle Mittel zur Verfügung, um eigenen Code, Scripte und erweiterte Funktionen zu erstellen.

Um beiden Anforderungen gerecht zu werden, können Abläufe in Expecco sowohl als Aktivitätsdiagramm ("''Kästchen und Pfeile''") als auch als Scriptcode in verschiedenen Programmiersprachen definiert werden.
Die ermöglicht einen "''Best of both Worlds''" Ansatz: einerseits können Nichtprogrammierer auf einer hohen Abstraktionsebene bestehende Aktionsbausteine mittels "''Drag & Drop''" oder Recording von GUI Aktionen zu komplexen Szenarien verbinden,
andererseits ist es möglich, fehlende Funktionsbausteine als Scriptcode zu erstellen, und als Aktionsbaustein für andere Aktionen bereit zu stellen. Wobei "Scriptcode" hier für JavaScript, Python, Java, Shell/Batch bis hin zu C/C++ steht.

"Hardcore" Entwickler können selbstverständlich auch den gesamten Testablauf als Script/Programmcode definieren - allerdings geht dadurch u.U. die Verständlichkeit und modulare Nutzbarkeit für Nichtprogrammierer mehr oder weniger verloren. Wir raten daher im Allgemeinen dazu, Programmcode nur zu verwenden, um Anbindungen an bestehende Frameworks zu kapseln, und den eigentlichen Ablauf als Aktivitätsdiagramm zu formulieren.

In der Praxis wird es zu einer Aufgabenteilung kommen: für die Anbindung an das getestete System (SUT - System under Test) werden oft spezielle Aktionsbausteine benötigt, die ein Programmierer entwickeln wird (z.B. Anbindungen an Protokolle, Hardware oder Dokumentformate). Der Ablauf der Testszenarien wird dann gemeinsam von Entwicklern, Testern und Analysten durch Diagramme auf einer höheren Abstraktionsebene definiert, wobei hierzu kein Programmierknowhow benötigt wird.

== Erweiterbar ==
Eigene Aktionsbausteine können eine große Menge an frei verfügbarem und bereits existierenden Code nutzen. Somit können Anbindungen an Protokolle, Hardware oder Dokumentformate schnell und preisgünstig realisiert werden. Sie können interaktiv Codefragmente in ihre Szenarien einbinden, welche in JavaScript (Node.js/npm), Python, Java (jar-Dateien), DotNET (Assemblies), R (statistische Auswertungen), Gnuplot (Grafiken erstellen) u.a.m. erstellt wurden.
Für diese Programmiersprachen gibt es eine große Menge an frei verfügbaren oder auch lizensierbaren Programmpaketen, z.B. in github oder als npm (Node.js) bzw. pip (Python) Pakete.

Hauptseite

2024-08-01T09:59:27Z

Alkurz: Hack für "Was ist expecco?"

[[Hauptseite/en|English Version]]

Klicken Sie links auf ''"Letzte Änderungen"'' ("Recent changes") um die neuesten Einträge in der Dokumentation zu sehen. 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">

[[Datei:Icon_Landingpage.png|30px]]Für Einsteiger<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">

[[Datei:Icon_Landingpage5.png|30px]]Installation<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">

[[Datei:Icon_Landingpage4.png|30px]]Werkzeuge<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">

[[Datei:Icon_Landingpage6.png|30px]]Reportgenerierung<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">

[[Datei:Erweiterung_plugin.png|30px]]Erweiterungen (Plugins)<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">

[[Datei:Icon_Landingpage3.png|30px]]Elemente der Testsuite<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">

[[Datei:Icon_Landingpage3.png|30px]]API Referenz (Elementarbausteine)<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>
</ul>
</div>

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

[[Datei:Diagramm.png|30px]]Diagramm - Elemente<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">

[[Datei:Refresh.png|30px]]Sonstiges<hr>

<ul style="font-size:0.8em; padding:0.7em 1em 1em 2.4em">
<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">

[[Datei:Beispiele_icon.png|30px]]Beispiele<hr>
Sie haben Fragen, wie ein Projekt aussieht?<hr>

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

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

[[Datei:Beispiele_icon.png|30px]]Unterstützung weiterer Qualitätsmanagement Tools<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">

[[Datei:Sonstiges-Info.png|30px]]Allgemein<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">

[[Datei:Icon_Landingpage5.png|30px]]Installation/Einrichten<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">

[[Datei:Refresh.png|30px]]Plugins<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">

[[Datei:Refresh.png|30px]]Sonstiges<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>

Expecco wiki:Impressum

2024-08-01T09:42:51Z

Alkurz:

eXept Software AG 
Talstr. 4 
74321 Bietigheim-Bissingen 
Germany 

Tel.: +49 7142 91948-0 
Fax: +49 7142 91948-44

E-Mail: info@exept.de 
Internet: www.exept.de

Vorstand: 
Stefan Vogel

Aufsichtsrat: 
Claus Gittinger (Vorsitzender)

Registereinträge: 
Registergericht: Amtsgericht Stuttgart 
Registernummer: HRB 301567 

Umsatzsteuer-Identifikationsnummer: 
DE 178373827 

Haftungsausschluss: 
Die eXept AG distanziert sich in dieser Internetpräsenz ausdrücklich von allen Inhalten, die über Verweise (Links) von dieser Domain aus erreichbar sind, sofern diese Inhalte anstößig oder strafbar sind. Zum Zeitpunkt der Erstellung dieser Seiten war kein Inhalt, auf den von diesem Webangebot verwiesen wird, anstößig oder gar strafbar.

Datei:Execution Editor.png

2024-05-15T10:08:28Z

Alkurz: Alkurz lud eine neue Version von Datei:Execution Editor.png hoch

Importing file

Release Notes 24.x

2024-05-15T09:54:19Z

Alkurz: /* Release 24.1 (2Q 2024) */

See also: [[Release Notes 23.x]]
 

== Release 24.1 (2Q 2024) ==
*Feature: [[Expecco_API/en#Global_and_Static_Variables|Static Variables for Python]]
*Feature: Qt-Testing: Logging with log levels <code>DEBUG</code>, <code>INFO</code> and <code>WARN</code> ([[Qt_Inject_Windows/en#Logging|Qt-Logging]])
*Feature: Qt-Testing: Qt-Connections now use the ConnectionManager like the other Gui test technologies
*Feature: WindowsAutomation: Native Touch, Tap, Drag & Drop support now in the base WindowsAutomation Library
*Feature: Show Log and [[Timeline/en|Timeline view]] for testplans
*Feature: Search and Goto Line menu functions in the activity log view
*Feature: [[Embedded Systems C Bridge API|C-Bridge]] now supports SSL connections (encryption and authentication using certificates)
*Feature: [[Testsuite_Editor-ExecutionSettings_Editor/en|Settings for execution]] (thread pool and log activities/pins/info) can now be saved in the test suite settings
*Feature: CSV test report, values for start time, end time and duration added
*Feature: Improved refactoring for compound blocks: "Extract (& Replace) New Compound Action"
*Feature: Enhanced expecco reflection library
*Fix: Current temporary testplan settings (like selected testcases, do-not-execute of pre/post action, etc.) don't get lost anymore when reimporting a library
*Fix: WindowsAutomation: Fix blocking of applications after <Mouse Button Down>
*Fix: asynchronous write to an output pin with no wait() in bridged actions are now detected and reported as error (see Example3 in the [[Expecco_API/en#Asynchronous_and_Callback_Functions|NodeJS API Documentation]])
*Fix: Bridges: Detect (and ignore) invalid requests from forked background bridge threads
*Fix: Acitivity logs of asynchronous events in background actions are now displayed correctly in the background activity log.
*Fix: Qt: Drag and drop improved by revising the "Move mouse event" (Windows)

Testsuite Editor-ExecutionSettings Editor/en

2024-05-15T09:42:30Z

Alkurz: /* Logging */

[[Bild:Execution Editor_en.png|thumb|300px|Execution Editor]]
The execution editor is used to modify the execution settings of a [[TestSuite Element|test suite]]. It is located under the "''Execution''" tab when the test suite element (the top element) is selected in the navigation tree.

== Execution ==
;Use Values of the User Execution Settings
:The following settings are also defined in the user execution settings. If this option is activated, the values from the user execution settings are used, otherwise the values defined here in the test suite are used

;Separate Processes for Long-Running Activities
:This check toggle controls if multiple activities are allowed to execute in parallel (are executed by separate threads). By default, this is enabled, but for some programs, it makes sense to disable this feature. (Usually badly formulated activities, which do not care for synchronized access to shared data.)

;When execution longer than
:Due to the fact that starting up new processes is a slow operation and takes up some processing power, the expecco system delays the creation of new processes for some time, in order to allow for short activities to finish without the need for an expensive creation of a new process. If an activity is finished within that time duration, no new process is created. Effectively, short-term activities are sequentially executed, as long as their processing takes less than this time duration.

;Max. Number of Activity Processes
:This limits the number of parallel executing separate processes. Because a process is a somewhat expensive resource in a computer (memory, disk space etc.), allowing for an arbitrary number of separate processes might lead to a slowdown or even blocking of the computers operation.

;Separate Processes for Suspended Activities
:Due to the fact that starting up new processes (execution threads) is a relatively slow operation and takes up some processing power, the expecco system delays the creation of new processes for some time, in order to allow for short activities to finish without creating of a new process. If an activity is finished within that time duration, no new process is created. Effectively, short-term activities are sequentially executed, as long as their processing takes less than this time duration.

;Max. Recursion Level
:This parameter limits the nesting of activities during execution (i.e. the nesting of compound activities which invokes another compound activity). If this limit is reached, an error is raised, which leads to the current test case to be reported as erroneous.

:Effectively, expecco will keep a pool of worker threads for execution, which process pending activities. The max. number of worker threads is set by this parameter.

;Max. Cleanup Time
:This parameter limits the max. execution time of cleanup actions. This allows for cleanup actions which try to communicate with dead connections to be terminated and thus avoids blocking. If a cleanup action executes longer, a dialog is shown, asking if a hard termination (i.e. termination without cleanup) or a wait for the action is desired by the user. If expecco is executed in non-interactive mode (slave-mode or executed via command line), the dialog is not shown. Instead, the cleanup action is hard terminated automatically after the max. cleanup time.

== Probes ==

;Set probe mode to checking
:If there are [[Probe|Probes]] in your test suite, set them to checking mode.

== Resources ==
Specifies the set of resources (devices, operators etc.) which are available for resource allocation.

;Default Inventory
:Specifies the set of resources which are available during developing and tests of the testsuite. This resource template might differ to the ALM Template.

;ALM Template
:Optional Resources used by ALM/expeccoNET. If unspecified, the default inventory will be used.

== User Interface ==
Specifies if and how the optional user interface of actions with GUI is to be shown.
This affects only actions which have a GUI attached. In version 2.x, this is a non-supported feature which is not yet released for public use, so we recommend to not use GUI actions and to leave the setting here as defaulted "none".

== Logging ==
These settings specify, how log entries should be stored in the activity log as shown in the [[Testplan_Editor/en|testplan editor]]. The activity log is also the base of test reports, so limiting the log entries in the activity log also limits, what can be shown in a test report.

Older versions of expecco included also Report Parameter settings here. These are now kept as [[ReportTemplate_Element/en|Report Template Element]] in the project tree. Multiple of them can be stored and maintained within a single test suite, to provide specifications for multiple reports with different detail for different target audiences.

;Use Values of the User Activity-Log Settings
:The following settings are also defined in the user activity-log settings. If this option is activated, the values from the user activity-log settings are used, otherwise the values defined here in the test suite are used

;Log Activities
:If enabled, each activity is stored in an activity log.
:If disabled, only failed activities are stored.
:At least there is one activity log, which keeps the whole information about the execution.

;Max. Number of kept Subactivities per [[Executor#Activity|Activity]]
:Maximum number of subactivities per activity stored in the activity log. This setting is used to limit the amount of log data during execution. If nothing is specified, all sub activities are stored. The default setting is specified in the testsuite.

;Log Pin Data
:If enabled, all input and output pin values are stored in the activity log. Otherwise all values are discarded.

;Log Info
:If enabled, all information messages are stored in the activity log. Otherwise all information messages are discarded.

----

;Trace [[Glossary/en#Stdout | Stdout]] and [[Glossary/en#Stderr | Stderr]] on [[Tools_Transcript/en|Transcript]]
:If enabled, the Stdout and Stderr are shown on the transcript.

The default values can also be changed in the more convenient [[Settings#Logging Settings|settings dialog]].

[[Category:Editors]]

Testsuite Editor-ExecutionSettings Editor/en

2024-05-15T09:40:50Z

Alkurz: /* Logging */

[[Bild:Execution Editor_en.png|thumb|300px|Execution Editor]]
The execution editor is used to modify the execution settings of a [[TestSuite Element|test suite]]. It is located under the "''Execution''" tab when the test suite element (the top element) is selected in the navigation tree.

== Execution ==
;Use Values of the User Execution Settings
:The following settings are also defined in the user execution settings. If this option is activated, the values from the user execution settings are used, otherwise the values defined here in the test suite are used

;Separate Processes for Long-Running Activities
:This check toggle controls if multiple activities are allowed to execute in parallel (are executed by separate threads). By default, this is enabled, but for some programs, it makes sense to disable this feature. (Usually badly formulated activities, which do not care for synchronized access to shared data.)

;When execution longer than
:Due to the fact that starting up new processes is a slow operation and takes up some processing power, the expecco system delays the creation of new processes for some time, in order to allow for short activities to finish without the need for an expensive creation of a new process. If an activity is finished within that time duration, no new process is created. Effectively, short-term activities are sequentially executed, as long as their processing takes less than this time duration.

;Max. Number of Activity Processes
:This limits the number of parallel executing separate processes. Because a process is a somewhat expensive resource in a computer (memory, disk space etc.), allowing for an arbitrary number of separate processes might lead to a slowdown or even blocking of the computers operation.

;Separate Processes for Suspended Activities
:Due to the fact that starting up new processes (execution threads) is a relatively slow operation and takes up some processing power, the expecco system delays the creation of new processes for some time, in order to allow for short activities to finish without creating of a new process. If an activity is finished within that time duration, no new process is created. Effectively, short-term activities are sequentially executed, as long as their processing takes less than this time duration.

;Max. Recursion Level
:This parameter limits the nesting of activities during execution (i.e. the nesting of compound activities which invokes another compound activity). If this limit is reached, an error is raised, which leads to the current test case to be reported as erroneous.

:Effectively, expecco will keep a pool of worker threads for execution, which process pending activities. The max. number of worker threads is set by this parameter.

;Max. Cleanup Time
:This parameter limits the max. execution time of cleanup actions. This allows for cleanup actions which try to communicate with dead connections to be terminated and thus avoids blocking. If a cleanup action executes longer, a dialog is shown, asking if a hard termination (i.e. termination without cleanup) or a wait for the action is desired by the user. If expecco is executed in non-interactive mode (slave-mode or executed via command line), the dialog is not shown. Instead, the cleanup action is hard terminated automatically after the max. cleanup time.

== Probes ==

;Set probe mode to checking
:If there are [[Probe|Probes]] in your test suite, set them to checking mode.

== Resources ==
Specifies the set of resources (devices, operators etc.) which are available for resource allocation.

;Default Inventory
:Specifies the set of resources which are available during developing and tests of the testsuite. This resource template might differ to the ALM Template.

;ALM Template
:Optional Resources used by ALM/expeccoNET. If unspecified, the default inventory will be used.

== User Interface ==
Specifies if and how the optional user interface of actions with GUI is to be shown.
This affects only actions which have a GUI attached. In version 2.x, this is a non-supported feature which is not yet released for public use, so we recommend to not use GUI actions and to leave the setting here as defaulted "none".

== Logging ==
These settings specify, how log entries should be stored in the activity log as shown in the [[TestplanEditor]]. The activity log is also the base of test reports, so limiting the log entries in the activity log also limits, what can be shown in a test report.

Older versions of expecco included also Report Parameter settings here. These are now kept as [[Report Template Element]] in the project tree. Multiple of them can be stored and maintained within a single test suite, to provide specifications for multiple reports with different detail for different target audiences.

;Use Values of the User Activity-Log Settings
:The following settings are also defined in the user activity-log settings. If this option is activated, the values from the user activity-log settings are used, otherwise the values defined here in the test suite are used

;Log Activities
:If enabled, each activity is stored in an activity log.
:If disabled, only failed activities are stored.
:At least there is one activity log, which keeps the whole information about the execution.

;Max. Number of kept Subactivities per [[Executor#Activity|Activity]]
:Maximum number of subactivities per activity stored in the activity log. This setting is used to limit the amount of log data during execution. If nothing is specified, all sub activities are stored. The default setting is specified in the testsuite.

;Log Pin Data
:If enabled, all input and output pin values are stored in the activity log. Otherwise all values are discarded.

;Log Info
:If enabled, all information messages are stored in the activity log. Otherwise all information messages are discarded.

----

;Trace [[Glossary/en#Stdout | Stdout]] and [[Glossary/en#Stderr | Stderr]] on [[Tools_Transcript/en|Transcript]]
:If enabled, the Stdout and Stderr are shown on the transcript.

The default values can also be changed in the more convenient [[Settings#Logging Settings|settings dialog]].

[[Category:Editors]]

Testsuite Editor-ExecutionSettings Editor/en

2024-05-15T09:36:38Z

Alkurz: /* Execution Settings */

[[Bild:Execution Editor_en.png|thumb|300px|Execution Editor]]
The execution editor is used to modify the execution settings of a [[TestSuite Element|test suite]]. It is located under the "''Execution''" tab when the test suite element (the top element) is selected in the navigation tree.

== Execution ==
;Use Values of the User Execution Settings
:The following settings are also defined in the user execution settings. If this option is activated, the values from the user execution settings are used, otherwise the values defined here in the test suite are used

;Separate Processes for Long-Running Activities
:This check toggle controls if multiple activities are allowed to execute in parallel (are executed by separate threads). By default, this is enabled, but for some programs, it makes sense to disable this feature. (Usually badly formulated activities, which do not care for synchronized access to shared data.)

;When execution longer than
:Due to the fact that starting up new processes is a slow operation and takes up some processing power, the expecco system delays the creation of new processes for some time, in order to allow for short activities to finish without the need for an expensive creation of a new process. If an activity is finished within that time duration, no new process is created. Effectively, short-term activities are sequentially executed, as long as their processing takes less than this time duration.

;Max. Number of Activity Processes
:This limits the number of parallel executing separate processes. Because a process is a somewhat expensive resource in a computer (memory, disk space etc.), allowing for an arbitrary number of separate processes might lead to a slowdown or even blocking of the computers operation.

;Separate Processes for Suspended Activities
:Due to the fact that starting up new processes (execution threads) is a relatively slow operation and takes up some processing power, the expecco system delays the creation of new processes for some time, in order to allow for short activities to finish without creating of a new process. If an activity is finished within that time duration, no new process is created. Effectively, short-term activities are sequentially executed, as long as their processing takes less than this time duration.

;Max. Recursion Level
:This parameter limits the nesting of activities during execution (i.e. the nesting of compound activities which invokes another compound activity). If this limit is reached, an error is raised, which leads to the current test case to be reported as erroneous.

:Effectively, expecco will keep a pool of worker threads for execution, which process pending activities. The max. number of worker threads is set by this parameter.

;Max. Cleanup Time
:This parameter limits the max. execution time of cleanup actions. This allows for cleanup actions which try to communicate with dead connections to be terminated and thus avoids blocking. If a cleanup action executes longer, a dialog is shown, asking if a hard termination (i.e. termination without cleanup) or a wait for the action is desired by the user. If expecco is executed in non-interactive mode (slave-mode or executed via command line), the dialog is not shown. Instead, the cleanup action is hard terminated automatically after the max. cleanup time.

== Probes ==

;Set probe mode to checking
:If there are [[Probe|Probes]] in your test suite, set them to checking mode.

== Resources ==
Specifies the set of resources (devices, operators etc.) which are available for resource allocation.

;Default Inventory
:Specifies the set of resources which are available during developing and tests of the testsuite. This resource template might differ to the ALM Template.

;ALM Template
:Optional Resources used by ALM/expeccoNET. If unspecified, the default inventory will be used.

== User Interface ==
Specifies if and how the optional user interface of actions with GUI is to be shown.
This affects only actions which have a GUI attached. In version 2.x, this is a non-supported feature which is not yet released for public use, so we recommend to not use GUI actions and to leave the setting here as defaulted "none".

== Logging ==
These settings specify, how log entries should be stored in the activity log as shown in the [[TestplanEditor]]. The activity log is also the base of test reports, so limiting the log entries in the activity log also limits, what can be shown in a test report.

Older versions of expecco included also Report Parameter settings here. These are now kept as [[Report Template Element]] in the project tree. Multiple of them can be stored and maintained within a single test suite, to provide specifications for multiple reports with different detail for different target audiences.

;Use Values of the User Activity-Log Settings
:The following settings are also defined in the user activity-log settings. If this option is activated, the values from the user activity-log settings are used, otherwise the values defined here in the test suite are used

;Log Activities
:If enabled, each activity is stored in an activity log.
:If disabled, only failed activities are stored.
:At least there is one activity log, which keeps the whole information about the execution.

;Max. Number of kept Subactivities per [[Executor#Activity|Activity]]
:Maximum number of subactivities per activity stored in the activity log. This setting is used to limit the amount of log data during execution. If nothing is specified, all sub activities are stored. The default setting is specified in the testsuite.

;Log Pin Data
:If enabled, all input and output pin values are stored in the activity log. Otherwise all values are discarded.

;Log Info
:If enabled, all information messages are stored in the activity log. Otherwise all information messages are discarded.

----

;Trace [[Glossary/en#Stdout | Stdout]] and [[Glossary/en#Stderr | Stderr]] on [[Transcript]]
:If enabled, the Stdout and Stderr are shown on the transcript.

The default values can also be changed in the more convenient [[Settings#Logging Settings|settings dialog]].

[[Category:Editors]]

Testsuite Editor-ExecutionSettings Editor/en

2024-05-15T09:36:00Z

Alkurz: /* Logging Settings */

[[Bild:Execution Editor_en.png|thumb|300px|Execution Editor]]
The execution editor is used to modify the execution settings of a [[TestSuite Element|test suite]]. It is located under the "''Execution''" tab when the test suite element (the top element) is selected in the navigation tree.

== Execution Settings ==
;Use Values of the User Execution Settings
:The following settings are also defined in the user execution settings. If this option is activated, the values from the user execution settings are used, otherwise the values defined here in the test suite are used

;Separate Processes for Long-Running Activities
:This check toggle controls if multiple activities are allowed to execute in parallel (are executed by separate threads). By default, this is enabled, but for some programs, it makes sense to disable this feature. (Usually badly formulated activities, which do not care for synchronized access to shared data.)

;When execution longer than
:Due to the fact that starting up new processes is a slow operation and takes up some processing power, the expecco system delays the creation of new processes for some time, in order to allow for short activities to finish without the need for an expensive creation of a new process. If an activity is finished within that time duration, no new process is created. Effectively, short-term activities are sequentially executed, as long as their processing takes less than this time duration.

;Max. Number of Activity Processes
:This limits the number of parallel executing separate processes. Because a process is a somewhat expensive resource in a computer (memory, disk space etc.), allowing for an arbitrary number of separate processes might lead to a slowdown or even blocking of the computers operation.

;Separate Processes for Suspended Activities
:Due to the fact that starting up new processes (execution threads) is a relatively slow operation and takes up some processing power, the expecco system delays the creation of new processes for some time, in order to allow for short activities to finish without creating of a new process. If an activity is finished within that time duration, no new process is created. Effectively, short-term activities are sequentially executed, as long as their processing takes less than this time duration.

;Max. Recursion Level
:This parameter limits the nesting of activities during execution (i.e. the nesting of compound activities which invokes another compound activity). If this limit is reached, an error is raised, which leads to the current test case to be reported as erroneous.

:Effectively, expecco will keep a pool of worker threads for execution, which process pending activities. The max. number of worker threads is set by this parameter.

;Max. Cleanup Time
:This parameter limits the max. execution time of cleanup actions. This allows for cleanup actions which try to communicate with dead connections to be terminated and thus avoids blocking. If a cleanup action executes longer, a dialog is shown, asking if a hard termination (i.e. termination without cleanup) or a wait for the action is desired by the user. If expecco is executed in non-interactive mode (slave-mode or executed via command line), the dialog is not shown. Instead, the cleanup action is hard terminated automatically after the max. cleanup time.

----

;Set probe mode to checking
:If there are [[Probe|Probes]] in your test suite, set them to checking mode.

== Resources ==
Specifies the set of resources (devices, operators etc.) which are available for resource allocation.

;Default Inventory
:Specifies the set of resources which are available during developing and tests of the testsuite. This resource template might differ to the ALM Template.

;ALM Template
:Optional Resources used by ALM/expeccoNET. If unspecified, the default inventory will be used.

== User Interface ==
Specifies if and how the optional user interface of actions with GUI is to be shown.
This affects only actions which have a GUI attached. In version 2.x, this is a non-supported feature which is not yet released for public use, so we recommend to not use GUI actions and to leave the setting here as defaulted "none".

== Logging ==
These settings specify, how log entries should be stored in the activity log as shown in the [[TestplanEditor]]. The activity log is also the base of test reports, so limiting the log entries in the activity log also limits, what can be shown in a test report.

Older versions of expecco included also Report Parameter settings here. These are now kept as [[Report Template Element]] in the project tree. Multiple of them can be stored and maintained within a single test suite, to provide specifications for multiple reports with different detail for different target audiences.

;Use Values of the User Activity-Log Settings
:The following settings are also defined in the user activity-log settings. If this option is activated, the values from the user activity-log settings are used, otherwise the values defined here in the test suite are used

;Log Activities
:If enabled, each activity is stored in an activity log.
:If disabled, only failed activities are stored.
:At least there is one activity log, which keeps the whole information about the execution.

;Max. Number of kept Subactivities per [[Executor#Activity|Activity]]
:Maximum number of subactivities per activity stored in the activity log. This setting is used to limit the amount of log data during execution. If nothing is specified, all sub activities are stored. The default setting is specified in the testsuite.

;Log Pin Data
:If enabled, all input and output pin values are stored in the activity log. Otherwise all values are discarded.

;Log Info
:If enabled, all information messages are stored in the activity log. Otherwise all information messages are discarded.

----

;Trace [[Glossary/en#Stdout | Stdout]] and [[Glossary/en#Stderr | Stderr]] on [[Transcript]]
:If enabled, the Stdout and Stderr are shown on the transcript.

The default values can also be changed in the more convenient [[Settings#Logging Settings|settings dialog]].

[[Category:Editors]]

Testsuite Editor-ExecutionSettings Editor/en

2024-05-15T09:35:31Z

Alkurz: /* Inventory */

[[Bild:Execution Editor_en.png|thumb|300px|Execution Editor]]
The execution editor is used to modify the execution settings of a [[TestSuite Element|test suite]]. It is located under the "''Execution''" tab when the test suite element (the top element) is selected in the navigation tree.

== Execution Settings ==
;Use Values of the User Execution Settings
:The following settings are also defined in the user execution settings. If this option is activated, the values from the user execution settings are used, otherwise the values defined here in the test suite are used

;Separate Processes for Long-Running Activities
:This check toggle controls if multiple activities are allowed to execute in parallel (are executed by separate threads). By default, this is enabled, but for some programs, it makes sense to disable this feature. (Usually badly formulated activities, which do not care for synchronized access to shared data.)

;When execution longer than
:Due to the fact that starting up new processes is a slow operation and takes up some processing power, the expecco system delays the creation of new processes for some time, in order to allow for short activities to finish without the need for an expensive creation of a new process. If an activity is finished within that time duration, no new process is created. Effectively, short-term activities are sequentially executed, as long as their processing takes less than this time duration.

;Max. Number of Activity Processes
:This limits the number of parallel executing separate processes. Because a process is a somewhat expensive resource in a computer (memory, disk space etc.), allowing for an arbitrary number of separate processes might lead to a slowdown or even blocking of the computers operation.

;Separate Processes for Suspended Activities
:Due to the fact that starting up new processes (execution threads) is a relatively slow operation and takes up some processing power, the expecco system delays the creation of new processes for some time, in order to allow for short activities to finish without creating of a new process. If an activity is finished within that time duration, no new process is created. Effectively, short-term activities are sequentially executed, as long as their processing takes less than this time duration.

;Max. Recursion Level
:This parameter limits the nesting of activities during execution (i.e. the nesting of compound activities which invokes another compound activity). If this limit is reached, an error is raised, which leads to the current test case to be reported as erroneous.

:Effectively, expecco will keep a pool of worker threads for execution, which process pending activities. The max. number of worker threads is set by this parameter.

;Max. Cleanup Time
:This parameter limits the max. execution time of cleanup actions. This allows for cleanup actions which try to communicate with dead connections to be terminated and thus avoids blocking. If a cleanup action executes longer, a dialog is shown, asking if a hard termination (i.e. termination without cleanup) or a wait for the action is desired by the user. If expecco is executed in non-interactive mode (slave-mode or executed via command line), the dialog is not shown. Instead, the cleanup action is hard terminated automatically after the max. cleanup time.

----

;Set probe mode to checking
:If there are [[Probe|Probes]] in your test suite, set them to checking mode.

== Resources ==
Specifies the set of resources (devices, operators etc.) which are available for resource allocation.

;Default Inventory
:Specifies the set of resources which are available during developing and tests of the testsuite. This resource template might differ to the ALM Template.

;ALM Template
:Optional Resources used by ALM/expeccoNET. If unspecified, the default inventory will be used.

== User Interface ==
Specifies if and how the optional user interface of actions with GUI is to be shown.
This affects only actions which have a GUI attached. In version 2.x, this is a non-supported feature which is not yet released for public use, so we recommend to not use GUI actions and to leave the setting here as defaulted "none".

== Logging Settings ==
These settings specify, how log entries should be stored in the activity log as shown in the [[TestplanEditor]]. The activity log is also the base of test reports, so limiting the log entries in the activity log also limits, what can be shown in a test report.

Older versions of expecco included also Report Parameter settings here. These are now kept as [[Report Template Element]] in the project tree. Multiple of them can be stored and maintained within a single test suite, to provide specifications for multiple reports with different detail for different target audiences.

;Use Values of the User Activity-Log Settings
:The following settings are also defined in the user activity-log settings. If this option is activated, the values from the user activity-log settings are used, otherwise the values defined here in the test suite are used

;Log Activities
:If enabled, each activity is stored in an activity log.
:If disabled, only failed activities are stored.
:At least there is one activity log, which keeps the whole information about the execution.

;Max. Number of kept Subactivities per [[Executor#Activity|Activity]]
:Maximum number of subactivities per activity stored in the activity log. This setting is used to limit the amount of log data during execution. If nothing is specified, all sub activities are stored. The default setting is specified in the testsuite.

;Log Pin Data
:If enabled, all input and output pin values are stored in the activity log. Otherwise all values are discarded.

;Log Info
:If enabled, all information messages are stored in the activity log. Otherwise all information messages are discarded.

----

;Trace [[Glossary/en#Stdout | Stdout]] and [[Glossary/en#Stderr | Stderr]] on [[Transcript]]
:If enabled, the Stdout and Stderr are shown on the transcript.

The default values can also be changed in the more convenient [[Settings#Logging Settings|settings dialog]].

[[Category:Editors]]

Testsuite Editor-ExecutionSettings Editor/en

2024-05-15T09:33:14Z

Alkurz:

[[Bild:Execution Editor_en.png|thumb|300px|Execution Editor]]
The execution editor is used to modify the execution settings of a [[TestSuite Element|test suite]]. It is located under the "''Execution''" tab when the test suite element (the top element) is selected in the navigation tree.

== Execution Settings ==
;Use Values of the User Execution Settings
:The following settings are also defined in the user execution settings. If this option is activated, the values from the user execution settings are used, otherwise the values defined here in the test suite are used

;Separate Processes for Long-Running Activities
:This check toggle controls if multiple activities are allowed to execute in parallel (are executed by separate threads). By default, this is enabled, but for some programs, it makes sense to disable this feature. (Usually badly formulated activities, which do not care for synchronized access to shared data.)

;When execution longer than
:Due to the fact that starting up new processes is a slow operation and takes up some processing power, the expecco system delays the creation of new processes for some time, in order to allow for short activities to finish without the need for an expensive creation of a new process. If an activity is finished within that time duration, no new process is created. Effectively, short-term activities are sequentially executed, as long as their processing takes less than this time duration.

;Max. Number of Activity Processes
:This limits the number of parallel executing separate processes. Because a process is a somewhat expensive resource in a computer (memory, disk space etc.), allowing for an arbitrary number of separate processes might lead to a slowdown or even blocking of the computers operation.

;Separate Processes for Suspended Activities
:Due to the fact that starting up new processes (execution threads) is a relatively slow operation and takes up some processing power, the expecco system delays the creation of new processes for some time, in order to allow for short activities to finish without creating of a new process. If an activity is finished within that time duration, no new process is created. Effectively, short-term activities are sequentially executed, as long as their processing takes less than this time duration.

;Max. Recursion Level
:This parameter limits the nesting of activities during execution (i.e. the nesting of compound activities which invokes another compound activity). If this limit is reached, an error is raised, which leads to the current test case to be reported as erroneous.

:Effectively, expecco will keep a pool of worker threads for execution, which process pending activities. The max. number of worker threads is set by this parameter.

;Max. Cleanup Time
:This parameter limits the max. execution time of cleanup actions. This allows for cleanup actions which try to communicate with dead connections to be terminated and thus avoids blocking. If a cleanup action executes longer, a dialog is shown, asking if a hard termination (i.e. termination without cleanup) or a wait for the action is desired by the user. If expecco is executed in non-interactive mode (slave-mode or executed via command line), the dialog is not shown. Instead, the cleanup action is hard terminated automatically after the max. cleanup time.

----

;Set probe mode to checking
:If there are [[Probe|Probes]] in your test suite, set them to checking mode.

== Inventory ==
Specifies the set of resources (devices, operators etc.) which are available for resource allocation.

;Default Inventory
:Specifies the set of resources which are available during developing and tests of the testsuite. This resource template might differ to the expeccoNET Template.

;ExpeccoNET Template
:Optional Resources used by expeccoNET. If unspecified, the default inventory will be used.

== User Interface ==
Specifies if and how the optional user interface of actions with GUI is to be shown.
This affects only actions which have a GUI attached. In version 2.x, this is a non-supported feature which is not yet released for public use, so we recommend to not use GUI actions and to leave the setting here as defaulted "none".

== Logging Settings ==
These settings specify, how log entries should be stored in the activity log as shown in the [[TestplanEditor]]. The activity log is also the base of test reports, so limiting the log entries in the activity log also limits, what can be shown in a test report.

Older versions of expecco included also Report Parameter settings here. These are now kept as [[Report Template Element]] in the project tree. Multiple of them can be stored and maintained within a single test suite, to provide specifications for multiple reports with different detail for different target audiences.

;Use Values of the User Activity-Log Settings
:The following settings are also defined in the user activity-log settings. If this option is activated, the values from the user activity-log settings are used, otherwise the values defined here in the test suite are used

;Log Activities
:If enabled, each activity is stored in an activity log.
:If disabled, only failed activities are stored.
:At least there is one activity log, which keeps the whole information about the execution.

;Max. Number of kept Subactivities per [[Executor#Activity|Activity]]
:Maximum number of subactivities per activity stored in the activity log. This setting is used to limit the amount of log data during execution. If nothing is specified, all sub activities are stored. The default setting is specified in the testsuite.

;Log Pin Data
:If enabled, all input and output pin values are stored in the activity log. Otherwise all values are discarded.

;Log Info
:If enabled, all information messages are stored in the activity log. Otherwise all information messages are discarded.

----

;Trace [[Glossary/en#Stdout | Stdout]] and [[Glossary/en#Stderr | Stderr]] on [[Transcript]]
:If enabled, the Stdout and Stderr are shown on the transcript.

The default values can also be changed in the more convenient [[Settings#Logging Settings|settings dialog]].

[[Category:Editors]]

Datei:Execution Editor en.png

2024-05-15T09:08:07Z

Alkurz:

Release Notes 24.x

2024-05-07T14:57:17Z

Alkurz: /* Release 24.1 (2Q 2024) */

See also: [[Release Notes 23.x]]
 

== Release 24.1 (2Q 2024) ==
*Feature: [[Expecco_API/en#Global_and_Static_Variables|Static Variables for Python]]
*Feature: Qt-Testing: Logging with log levels <code>DEBUG</code>, <code>INFO</code> and <code>WARN</code> ([[Qt_Inject_Windows/en#Logging|Qt-Logging]])
*Feature: WindowsAutomation: Native Touch, Tap, Drag & Drop support now in the base WindowsAutomation Library
*Feature: Show Log and [[Timeline/en|Timeline view]] for testplans
*Feature: Search and Goto Line menu functions in the activity log view
*Feature: [[Embedded Systems C Bridge API|C-Bridge]] now supports SSL connections (encryption and authentication using certificates)
*Feature: Settings for execution (thread pool and log activities/pins/info) can now be saved in the test suite settings
*Feature: CSV test report, values for start time, end time and duration added
*Feature: Improved Refactoring "Extract (& Replace) New Compound Action"
*Fix: Current temporary testplan settings (like selected testcases, do-not-execute of pre/post action, etc.) don't get lost anymore when reimporting a library
*Fix: WindowsAutomation: Fix blocking of applications after <Mouse Button Down>
*Fix: asynchronous write to an output pin with no wait() in bridged actions are now detected and reported as error (see Example3 in the [[Expecco_API/en#Asynchronous_and_Callback_Functions|NodeJS API Documentation]])
*Fix: Bridges: Detect (and ignore) invalid requests from forked background bridge threads

Release Notes 24.x

2024-05-07T14:56:42Z

Alkurz: /* Release 24.1 (2Q 2024) */

See also: [[Release Notes 23.x]]
 

== Release 24.1 (2Q 2024) ==
*Feature: [[Expecco_API/en#Global_and_Static_Variables|Static Variables for Python]]
*Feature: Qt-Testing: Logging with log levels <code>DEBUG</code>, <code>INFO</code> and <code>WARN</code> ([[Qt_Inject_Windows/en#Logging|Qt-Logging]])
*Feature: WindowsAutomation: Native Touch, Tap, Drag & Drop support now in the base WindowsAutomation Library
*Feature: Show Log and [[Timeline/en|Timeline view]] for testplans
*Feature: Search and Goto Line menu functions in the activity log view
*Feature: [[Embedded Systems C Bridge API|C-Bridge]] now supports SSL connections (encryption and authentication using certificates)
*Feature: Settings for execution (thread pool and log activities/pins/info) can now be saved in the test suite settings
*Feature: CSV test report, values for start time, end time and duration added
*Feature: Improved Refactoring "Extract (& Replace) New Compound Action"
*Feature: More information in CSV test reports
*Fix: Current temporary testplan settings (like selected testcases, do-not-execute of pre/post action, etc.) don't get lost anymore when reimporting a library
*Fix: WindowsAutomation: Fix blocking of applications after <Mouse Button Down>
*Fix: asynchronous write to an output pin with no wait() in bridged actions are now detected and reported as error (see Example3 in the [[Expecco_API/en#Asynchronous_and_Callback_Functions|NodeJS API Documentation]])
*Fix: Bridges: Detect (and ignore) invalid requests from forked background bridge threads

Release Notes 24.x

2024-05-07T14:55:49Z

Alkurz: /* Release 24.1 (2Q 2024) */

See also: [[Release Notes 23.x]]
 

== Release 24.1 (2Q 2024) ==
*Feature: [[Expecco_API/en#Global_and_Static_Variables|Static Variables for Python]]
*Feature: Qt-Testing: Logging with log levels <code>DEBUG</code>, <code>INFO</code> and <code>WARN</code> ([[Qt_Inject_Windows/en#logging|Qt-Logging]])
*Feature: WindowsAutomation: Native Touch, Tap, Drag & Drop support now in the base WindowsAutomation Library
*Feature: Show Log and [[Timeline/en|Timeline view]] for testplans
*Feature: Search and Goto Line menu functions in the activity log view
*Feature: [[Embedded Systems C Bridge API|C-Bridge]] now supports SSL connections (encryption and authentication using certificates)
*Feature: Settings for execution (thread pool and log activities/pins/info) can now be saved in the test suite settings
*Feature: CSV test report, values for start time, end time and duration added
*Feature: Improved Refactoring "Extract (& Replace) New Compound Action"
*Feature: More information in CSV test reports
*Fix: Current temporary testplan settings (like selected testcases, do-not-execute of pre/post action, etc.) don't get lost anymore when reimporting a library
*Fix: WindowsAutomation: Fix blocking of applications after <Mouse Button Down>
*Fix: asynchronous write to an output pin with no wait() in bridged actions are now detected and reported as error (see Example3 in the [[Expecco_API/en#Asynchronous_and_Callback_Functions|NodeJS API Documentation]])
*Fix: Bridges: Detect (and ignore) invalid requests from forked background bridge threads

Release Notes 24.x

2024-05-07T09:18:20Z

Alkurz: /* Release 24.1 (2Q 2024) */

See also: [[Release Notes 23.x]]
 

== Release 24.1 (2Q 2024) ==
*Feature: [[Expecco_API/en#Global_and_Static_Variables|Static Variables for Python]]
*Feature: Qt-Testing: Logging with log levels <code>DEBUG</code>, <code>INFO</code> and <code>WARN</code>
*Feature: WindowsAutomation: Native Touch, Tap, Drag & Drop support now in the base WindowsAutomation Library
*Feature: Log and timeline view also for the root testplan
*Feature: Search and Goto Line menu functions in the activity log view
*Feature: C-Bridge supports SSL connections (encryption and authentication using certificates)
*Enhancement: Current temporary testplan settings (like selected testcases, do-not-execute of pre/post action, etc.) don't get lost anymore when reimporting a library
*Bug Fix: WindowsAutomation: Fix blocking after <Mouse Button Down>
*Bug Fix: asynchronous write to an output pin with no wait() in bridged actions are now detected and reported as error (see Example3 in the [[Expecco_API/en#Asynchronous_and_Callback_Functions|NodeJS API Documentation]])
*Bug Fix: Bridges: Detect (and ignore) invalid requests from forked background threads
*Improvement: Refactoring "Extract (& Replace) New Compound Action"
*Feature: Settings for execution (thread pool and log activities/pins/info) can now be saved in the test suite settings
*Improvement: CSV test report, values for start time, end time and duration added

Release Notes 24.x

2024-05-07T08:30:03Z

Alkurz:

Release Notes 24.x

2024-05-07T08:17:35Z

Alkurz: /* Release 24.1 (2Q 2024) */

Settings ExecutionSettings/en

2024-04-11T14:18:01Z

Alkurz: /* Execution Settings */

== Execution Settings ==

=== Thread Pool ===
===== Separate Processes for Long Running Activities =====
This check toggle controls if multiple activities are allowed to execute in parallel
(are executed by separate threads).
By default, this is enabled, but in rare situations, it makes sense to disable this feature for some test projects.
Usually these are badly formulated activities, which do not care for synchronized access to shared data or data bases, and may therefore be not prepared for parallel execution.

Instead of disabling this feature, you should instead use synchronisation mechanisms in your activity diagram (i.e. either use trigger-out/trigger-in connections to enforce sequential execution, or use explicit semaphore actions to ensure mutual exclusion while doing such critical operations).

''This parameter can be set and saved directly in the test suite.''
''When a new test suite is created, the value from the settings dialog is used as the default value.''

===== Start Process After =====
Due to the fact that starting up new processes (execution threads) is a relatively slow operation and takes up some processing
power, the expecco system delays the creation of new processes for some time,
in order to allow for short activities to finish without creating of a new process.
If an activity is finished within that time duration, no new process is created.
Effectively, short-term activities are sequentially executed,
as long as their processing takes less than this time duration.

''This parameter can be set and saved directly in the test suite.''
''When a new test suite is created, the value from the settings dialog is used as the default value.''

===== Max. Number of Processes =====
This limits the number of parallel executing separate processes.
Because a process is a somewhat expensive resource in a computer (memory, disk space etc.),
allowing for an arbitrary number of separate processes might lead to a slowdown or even blocking of the computer's operation.

Effectively, expecco will keep a pool of worker threads for execution, which process pending activities. The max. number of worker threads is set by this parameter.

''This parameter can be set and saved directly in the test suite.''
''When a new test suite is created, the value from the settings dialog is used as the default value.''

===== Max. Number of Executors per Testsuite =====
This limits the number of executors that can execute within the same test suite at the same time.
This parameter can be used to prevent tests which use global resources without locking from being executed in parallel
(eg. when the same test suite is executed against multiple systems-under-test,
or if expecco is operated as an execution slave (runtime) and multiple execution jobs for the same suite are coming from a central QM management system)

===== Max. Number of ExpeccoNET Test-Executions =====
This limits the number of test execution jobs from a QM-management system that can run in parallel to limit the overall load on the system .
This parameter is only used if expecco is used as a test slave processor
(for remote test execution, under the control of an expecco ALM or other QM management system).

=== Recursion ===
===== Max. Recursion Level =====
This parameter limits the nesting of activities during execution
(i.e. the nesting of compound activities which invokes another compound activity).
If this limit is reached, an error is raised, which leads to the current test case to be reported as erroneous.

''This parameter can be set and saved directly in the test suite.''
''When a new test suite is created, the value from the settings dialog is used as the default value.''

=== Cleanup ===
===== Max. Cleanup Time =====
This parameter limits the max. execution time of cleanup
actions. This allows for cleanup actions which try to communicate with
dead connections to be terminated and thus avoids blocking.
If a cleanup action executes longer, a dialog is shown,
asking if a hard termination (i.e. termination without cleanup) or a wait for the action is desired by the user.
If expecco is executed in non-interactive mode (slave-mode or executed via command line),
the dialog is not shown. Instead, the cleanup action is hard terminated automatically after the max. cleanup time.

''This parameter can be set and saved directly in the test suite.''
''When a new test suite is created, the value from the settings dialog is used as the default value.''

=== User Interface ===
===== Slow Motion Delay =====
This parameter introduces a delay between the execution of individual activities.
This is useful in demonstration or replay situations, where the user wants to
visually follow and monitor the execution of the individual steps.
It is also sometimes useful when debugging a test,
to slow down the process artificially.

===== Show "Do Not Disturb" Banner =====
If checked, a banner window is shown during the execution of a test plan.
This is useful to prevent other users from touching the machine, especially preventing
them from stopping or disturbing an ongoing, long running test. It is especially useful on the
test floor, where test machines are shared among different users.

===== Minimize Expecco while Executing=====
If checked, the expecco window is iconified during a test's execution.

Useful to see what is going on (and as a still-processing feedback monitor)
when running UI-Tests (eg. in a Browser) on a single screen.
This feature is introduced with rel 19.1.

===== Auto-Confirm Dialog Boxes =====
If checked, dialog boxes will automatically close themself after a given time period.
Set this, to let the suite run unattended and confirm all dialogs with their default (usually "OK"), but still get a chance to interact if required (within that time period).

=== Scripts ===
===== Execute in the Attachments Folder =====
If checked, scripts are executed within the Attachments folder;
if unchecked (the default), they are executed one folder above.
This flag is only present for backward compatibility with previous
expecco versions.

===== Keep Temporary Script Folders =====
For debugging only; by default, scripts are generated into temporary files for execution by a shell or language interpreter, and removed afterwards.
Set this to prevent removal for debugging (especially to debug the variable expansion mechanism).

----

[[Settings/en|Back to the main page "Settings"]]
[[Category:Settings]]

Settings LoggingSettings/en

2024-04-11T14:16:16Z

Alkurz:

=== Overview ===
Activity log entries remember the result of a step's execution. They usually include information
about the input pin values, the execution time, the outcome (verdict) and the generated output value(s).
The activity log is (currently) stored in memory, to avoid excessive slow-down of the tests execution.

The activity log as generated by long running extensive tests may become very large and consume
lots of memory - sometimes more than can be kept and prunning (cutting off parts of the trace) is
required. For such tests, it might be useful to disable the logging of certain actions and/or steps and/or pins. This can be controlled via popup menus of steps and pins in the diagram editor.

In contrast to activity logs, traces as sent to the Transcript (Console) are not persistent and will be lost when the Transcript window is closed (unless the contents is captured and saved explicitly, via one of the Transcript action blocks)

== Logging Settings ==
These are found in "''Settings''" - "''Execution''" - "''Logging''".

=== Log Activities ===
If enabled, every activity is stored in the activity log.
If disabled, only failed activities are stored.
There will be always one master (top-level) entry stored, which keeps the overall
outcome of an execution, even for passed runs with disabled logging.

''This parameter can be set and saved directly in the test suite.''
''When a new test suite is created, the value from the settings dialog is used as the default value.''

=== Log Pin Data ===
If enabled, all input and output pin values are stored in the activity log.
Otherwise all values are discarded and pin values cannot be inspected after the test run.

''This parameter can be set and saved directly in the test suite.''
''When a new test suite is created, the value from the settings dialog is used as the default value.''

=== Log Info ===
If enabled, all information messages
(i.e. messages as generated by explicit logInfo calls and logInfo blocks)
are stored in the activity log.
Otherwise information messages are discarded.

''This parameter can be set and saved directly in the test suite.''
''When a new test suite is created, the value from the settings dialog is used as the default value.''

=== Log GUI Screenshots Automatically on Error ===
If enabled, GUI action blocks which encounter an error (typically: element/xpath not found) will automatically generate a screenshot and add this to the activity log. Be aware that this may generate a huge number of images and lead to excessive memory use and even a failure when running out of memory (especially on 32bit machines). SO this feature should only be used during development.

=== Log External OS Commands ===
If enabled, all executed OS commands (shell/script interpreter calls, etc.)
will be logged in the activity log.

=== Log System Activity Notifications ===
If enabled, activity information notifications
(i.e. implicit notifications of the underlying language framework)
are stored in the activity log as info log entries.
Otherwise information messages are discarded.

The default is false (used to be true in pre 2.1 releases).

=== Timestamps have Microsecond Resolution ===
If enabled, timestamps are kept with microsecond resolution (if the underlying operating system supports them);
otherwise, they are generated with millisecond resolution.

The default is false for backward compatibility with older expecco versions.

=== Ignore any "Skip in Trace" Attribute ===
Enforces an activity log/trace to be generated for all steps/pin values,
even if individual steps/pins have the "''Skip in Trace''"
attribute set.

=== Prefix for log output ===

An environment variable called__Transcript_Prefix__ can be defined in a test suite.
When text from this test suite is written to Transcript, the value of the variable is also output as a prefix.

== Tracing Settings ==
These are found in "''Settings''" - "''Execution''" - "''Tracing''".

=== Show Internal Warning and Info Messages ===
Probably only useful for diagnostics of expecco itself

=== Show Actions being Executed===
If enabled, the currently executed action's name is shown in the lower info area (not in the Transcript).
It can be further filtered by tag.

=== Logger Treshold ===
Defines a treshold which controls the set of Logger messages to be shown. Logger messages are typically produced internally eg. to display progress, errors etc. Many logger messages are meant for expecco developers, however some might be also of interest during test development.
Logger messages are associated a severity, which can be TRACE, DEBUG, INFO, WARNING, ERROR or FATAL.
Only logger messages with a greater-or-equal severity will be shown by the logger.
 By default, this treshold is set to "WARNING".

=== Show External Commands on Transcript ===
If on, executed shell, batch, script and other OS commands will be
traced on the Transcript.

=== Show Stdout and Stderr on Transcript ===
If on, the stdout/stderr of executed external programs is
traced on the Transcript (stderr in red).

=== Show Outgoing HTTP Requests on Transcript ===
Outgoing HTTP requests (from the HTTP-get/put actions) will be traced on the Transcript.

=== Show Outgoing SOAP Requests on Transcript ===
Outgoing SOAP requests will be traced on the Transcript.

=== Show IMAP and POP3 Protocol on Transcript ===
Interactions with the mailbox are traced on the Transcript.

=== MessageTally on Execution ===
If checked, execution times of elementary activities are measured and
an execution profile is generated after the execution (on the Transcript window).
This is useful to find out where time is spent for performance optimizations.

=== Coverage Recording onExecution ===
If checked, executed actions are instrumented to record which parts are executed and which are not.
(this is an unfinished feature, which may or may not work in your particular version of expecco)

----

[[Settings/en|Back to the main page "Settings"]]

Settings ExecutionSettings/en

2024-04-11T14:14:28Z

Alkurz: /* Keep Temporary Script Folders */

== Execution Settings ==

=== Thread Pool ===
===== Separate Processes for Long Running Activities =====
This check toggle controls if multiple activities are allowed to execute in parallel
(are executed by separate threads).
By default, this is enabled, but in rare situations, it makes sense to disable this feature for some test projects.
Usually these are badly formulated activities, which do not care for synchronized access to shared data or data bases, and may therefore be not prepared for parallel execution.

Instead of disabling this feature, you should instead use synchronisation mechanisms in your activity diagram (i.e. either use trigger-out/trigger-in connections to enforce sequential execution, or use explicit semaphore actions to ensure mutual exclusion while doing such critical operations).

This parameter is stored in the test suite, not in the private per-user settings.

===== Start Process After =====
Due to the fact that starting up new processes (execution threads) is a relatively slow operation and takes up some processing
power, the expecco system delays the creation of new processes for some time,
in order to allow for short activities to finish without creating of a new process.
If an activity is finished within that time duration, no new process is created.
Effectively, short-term activities are sequentially executed,
as long as their processing takes less than this time duration.

This parameter is stored in the test suite, not in the private per-user settings.

===== Max. Number of Processes =====
This limits the number of parallel executing separate processes.
Because a process is a somewhat expensive resource in a computer (memory, disk space etc.),
allowing for an arbitrary number of separate processes might lead to a slowdown or even blocking of the computer's operation.

Effectively, expecco will keep a pool of worker threads for execution, which process pending activities. The max. number of worker threads is set by this parameter.

This parameter is stored in the test suite, not in the private per-user settings.

===== Max. Number of Executors per Testsuite =====
This limits the number of executors that can execute within the same test suite at the same time.
This parameter can be used to prevent tests which use global resources without locking from being executed in parallel
(eg. when the same test suite is executed against multiple systems-under-test,
or if expecco is operated as an execution slave (runtime) and multiple execution jobs for the same suite are coming from a central QM management system)

===== Max. Number of ExpeccoNET Test-Executions =====
This limits the number of test execution jobs from a QM-management system that can run in parallel to limit the overall load on the system .
This parameter is only used if expecco is used as a test slave processor
(for remote test execution, under the control of an expecco ALM or other QM management system).

=== Recursion ===
===== Max. Recursion Level =====
This parameter limits the nesting of activities during execution
(i.e. the nesting of compound activities which invokes another compound activity).
If this limit is reached, an error is raised, which leads to the current test case to be reported as erroneous.

This parameter is stored in the test suite, not in the private per-user settings.

=== Cleanup ===
===== Max. Cleanup Time =====
This parameter limits the max. execution time of cleanup
actions. This allows for cleanup actions which try to communicate with
dead connections to be terminated and thus avoids blocking.
If a cleanup action executes longer, a dialog is shown,
asking if a hard termination (i.e. termination without cleanup) or a wait for the action is desired by the user.
If expecco is executed in non-interactive mode (slave-mode or executed via command line),
the dialog is not shown. Instead, the cleanup action is hard terminated automatically after the max. cleanup time.

This parameter is stored in the test suite, not in the private per-user settings.

=== User Interface ===
===== Slow Motion Delay =====
This parameter introduces a delay between the execution of individual activities.
This is useful in demonstration or replay situations, where the user wants to
visually follow and monitor the execution of the individual steps.
It is also sometimes useful when debugging a test,
to slow down the process artificially.

===== Show "Do Not Disturb" Banner =====
If checked, a banner window is shown during the execution of a test plan.
This is useful to prevent other users from touching the machine, especially preventing
them from stopping or disturbing an ongoing, long running test. It is especially useful on the
test floor, where test machines are shared among different users.

===== Minimize Expecco while Executing=====
If checked, the expecco window is iconified during a test's execution.

Useful to see what is going on (and as a still-processing feedback monitor)
when running UI-Tests (eg. in a Browser) on a single screen.
This feature is introduced with rel 19.1.

===== Auto-Confirm Dialog Boxes =====
If checked, dialog boxes will automatically close themself after a given time period.
Set this, to let the suite run unattended and confirm all dialogs with their default (usually "OK"), but still get a chance to interact if required (within that time period).

=== Scripts ===
===== Execute in the Attachments Folder =====
If checked, scripts are executed within the Attachments folder;
if unchecked (the default), they are executed one folder above.
This flag is only present for backward compatibility with previous
expecco versions.

===== Keep Temporary Script Folders =====
For debugging only; by default, scripts are generated into temporary files for execution by a shell or language interpreter, and removed afterwards.
Set this to prevent removal for debugging (especially to debug the variable expansion mechanism).

----

[[Settings/en|Back to the main page "Settings"]]
[[Category:Settings]]

Settings LoggingSettings/en

2024-04-11T14:13:13Z

Alkurz: /* Log Info */

Settings LoggingSettings/en

2024-04-11T14:12:56Z

Alkurz: /* Log Pin Data */

=== Overview ===
Activity log entries remember the result of a step's execution. They usually include information
about the input pin values, the execution time, the outcome (verdict) and the generated output value(s).
The activity log is (currently) stored in memory, to avoid excessive slow-down of the tests execution.

The activity log as generated by long running extensive tests may become very large and consume
lots of memory - sometimes more than can be kept and prunning (cutting off parts of the trace) is
required. For such tests, it might be useful to disable the logging of certain actions and/or steps and/or pins. This can be controlled via popup menus of steps and pins in the diagram editor.

In contrast to activity logs, traces as sent to the Transcript (Console) are not persistent and will be lost when the Transcript window is closed (unless the contents is captured and saved explicitly, via one of the Transcript action blocks)

== Logging Settings ==
These are found in "''Settings''" - "''Execution''" - "''Logging''".

=== Log Activities ===
If enabled, every activity is stored in the activity log.
If disabled, only failed activities are stored.
There will be always one master (top-level) entry stored, which keeps the overall
outcome of an execution, even for passed runs with disabled logging.

''This parameter can be set and saved directly in the test suite.''
''When a new test suite is created, the value from the settings dialog is used as the default value.''

=== Log Pin Data ===
If enabled, all input and output pin values are stored in the activity log.
Otherwise all values are discarded and pin values cannot be inspected after the test run.

''This parameter can be set and saved directly in the test suite.''
''When a new test suite is created, the value from the settings dialog is used as the default value.''

=== Log Info ===
If enabled, all information messages
(i.e. messages as generated by explicit logInfo calls and logInfo blocks)
are stored in the activity log.
Otherwise information messages are discarded.

''This parameter can be set and saved directly in the test suite.
When a new test suite is created, the value from the settings dialog is used as the default value.''

=== Log GUI Screenshots Automatically on Error ===
If enabled, GUI action blocks which encounter an error (typically: element/xpath not found) will automatically generate a screenshot and add this to the activity log. Be aware that this may generate a huge number of images and lead to excessive memory use and even a failure when running out of memory (especially on 32bit machines). SO this feature should only be used during development.

=== Log External OS Commands ===
If enabled, all executed OS commands (shell/script interpreter calls, etc.)
will be logged in the activity log.

=== Log System Activity Notifications ===
If enabled, activity information notifications
(i.e. implicit notifications of the underlying language framework)
are stored in the activity log as info log entries.
Otherwise information messages are discarded.

The default is false (used to be true in pre 2.1 releases).

=== Timestamps have Microsecond Resolution ===
If enabled, timestamps are kept with microsecond resolution (if the underlying operating system supports them);
otherwise, they are generated with millisecond resolution.

The default is false for backward compatibility with older expecco versions.

=== Ignore any "Skip in Trace" Attribute ===
Enforces an activity log/trace to be generated for all steps/pin values,
even if individual steps/pins have the "''Skip in Trace''"
attribute set.

=== Prefix for log output ===

An environment variable called__Transcript_Prefix__ can be defined in a test suite.
When text from this test suite is written to Transcript, the value of the variable is also output as a prefix.

== Tracing Settings ==
These are found in "''Settings''" - "''Execution''" - "''Tracing''".

=== Show Internal Warning and Info Messages ===
Probably only useful for diagnostics of expecco itself

=== Show Actions being Executed===
If enabled, the currently executed action's name is shown in the lower info area (not in the Transcript).
It can be further filtered by tag.

=== Logger Treshold ===
Defines a treshold which controls the set of Logger messages to be shown. Logger messages are typically produced internally eg. to display progress, errors etc. Many logger messages are meant for expecco developers, however some might be also of interest during test development.
Logger messages are associated a severity, which can be TRACE, DEBUG, INFO, WARNING, ERROR or FATAL.
Only logger messages with a greater-or-equal severity will be shown by the logger.
 By default, this treshold is set to "WARNING".

=== Show External Commands on Transcript ===
If on, executed shell, batch, script and other OS commands will be
traced on the Transcript.

=== Show Stdout and Stderr on Transcript ===
If on, the stdout/stderr of executed external programs is
traced on the Transcript (stderr in red).

=== Show Outgoing HTTP Requests on Transcript ===
Outgoing HTTP requests (from the HTTP-get/put actions) will be traced on the Transcript.

=== Show Outgoing SOAP Requests on Transcript ===
Outgoing SOAP requests will be traced on the Transcript.

=== Show IMAP and POP3 Protocol on Transcript ===
Interactions with the mailbox are traced on the Transcript.

=== MessageTally on Execution ===
If checked, execution times of elementary activities are measured and
an execution profile is generated after the execution (on the Transcript window).
This is useful to find out where time is spent for performance optimizations.

=== Coverage Recording onExecution ===
If checked, executed actions are instrumented to record which parts are executed and which are not.
(this is an unfinished feature, which may or may not work in your particular version of expecco)

Settings LoggingSettings/en

2024-04-11T14:12:43Z

Alkurz: /* Log Activities */

=== Overview ===
Activity log entries remember the result of a step's execution. They usually include information
about the input pin values, the execution time, the outcome (verdict) and the generated output value(s).
The activity log is (currently) stored in memory, to avoid excessive slow-down of the tests execution.

The activity log as generated by long running extensive tests may become very large and consume
lots of memory - sometimes more than can be kept and prunning (cutting off parts of the trace) is
required. For such tests, it might be useful to disable the logging of certain actions and/or steps and/or pins. This can be controlled via popup menus of steps and pins in the diagram editor.

In contrast to activity logs, traces as sent to the Transcript (Console) are not persistent and will be lost when the Transcript window is closed (unless the contents is captured and saved explicitly, via one of the Transcript action blocks)

== Logging Settings ==
These are found in "''Settings''" - "''Execution''" - "''Logging''".

=== Log Activities ===
If enabled, every activity is stored in the activity log.
If disabled, only failed activities are stored.
There will be always one master (top-level) entry stored, which keeps the overall
outcome of an execution, even for passed runs with disabled logging.

''This parameter can be set and saved directly in the test suite.''
''When a new test suite is created, the value from the settings dialog is used as the default value.''

=== Log Pin Data ===
If enabled, all input and output pin values are stored in the activity log.
Otherwise all values are discarded and pin values cannot be inspected after the test run.

''This parameter can be set and saved directly in the test suite.
When a new test suite is created, the value from the settings dialog is used as the default value.''

=== Log Info ===
If enabled, all information messages
(i.e. messages as generated by explicit logInfo calls and logInfo blocks)
are stored in the activity log.
Otherwise information messages are discarded.

''This parameter can be set and saved directly in the test suite.
When a new test suite is created, the value from the settings dialog is used as the default value.''

=== Log GUI Screenshots Automatically on Error ===
If enabled, GUI action blocks which encounter an error (typically: element/xpath not found) will automatically generate a screenshot and add this to the activity log. Be aware that this may generate a huge number of images and lead to excessive memory use and even a failure when running out of memory (especially on 32bit machines). SO this feature should only be used during development.

=== Log External OS Commands ===
If enabled, all executed OS commands (shell/script interpreter calls, etc.)
will be logged in the activity log.

=== Log System Activity Notifications ===
If enabled, activity information notifications
(i.e. implicit notifications of the underlying language framework)
are stored in the activity log as info log entries.
Otherwise information messages are discarded.

The default is false (used to be true in pre 2.1 releases).

=== Timestamps have Microsecond Resolution ===
If enabled, timestamps are kept with microsecond resolution (if the underlying operating system supports them);
otherwise, they are generated with millisecond resolution.

The default is false for backward compatibility with older expecco versions.

=== Ignore any "Skip in Trace" Attribute ===
Enforces an activity log/trace to be generated for all steps/pin values,
even if individual steps/pins have the "''Skip in Trace''"
attribute set.

=== Prefix for log output ===

An environment variable called__Transcript_Prefix__ can be defined in a test suite.
When text from this test suite is written to Transcript, the value of the variable is also output as a prefix.

== Tracing Settings ==
These are found in "''Settings''" - "''Execution''" - "''Tracing''".

=== Show Internal Warning and Info Messages ===
Probably only useful for diagnostics of expecco itself

=== Show Actions being Executed===
If enabled, the currently executed action's name is shown in the lower info area (not in the Transcript).
It can be further filtered by tag.

=== Logger Treshold ===
Defines a treshold which controls the set of Logger messages to be shown. Logger messages are typically produced internally eg. to display progress, errors etc. Many logger messages are meant for expecco developers, however some might be also of interest during test development.
Logger messages are associated a severity, which can be TRACE, DEBUG, INFO, WARNING, ERROR or FATAL.
Only logger messages with a greater-or-equal severity will be shown by the logger.
 By default, this treshold is set to "WARNING".

=== Show External Commands on Transcript ===
If on, executed shell, batch, script and other OS commands will be
traced on the Transcript.

=== Show Stdout and Stderr on Transcript ===
If on, the stdout/stderr of executed external programs is
traced on the Transcript (stderr in red).

=== Show Outgoing HTTP Requests on Transcript ===
Outgoing HTTP requests (from the HTTP-get/put actions) will be traced on the Transcript.

=== Show Outgoing SOAP Requests on Transcript ===
Outgoing SOAP requests will be traced on the Transcript.

=== Show IMAP and POP3 Protocol on Transcript ===
Interactions with the mailbox are traced on the Transcript.

=== MessageTally on Execution ===
If checked, execution times of elementary activities are measured and
an execution profile is generated after the execution (on the Transcript window).
This is useful to find out where time is spent for performance optimizations.

=== Coverage Recording onExecution ===
If checked, executed actions are instrumented to record which parts are executed and which are not.
(this is an unfinished feature, which may or may not work in your particular version of expecco)

Settings ExecutionSettings/en

2024-04-11T14:11:19Z

Alkurz:

== Execution Settings ==

=== Thread Pool ===
===== Separate Processes for Long Running Activities =====
This check toggle controls if multiple activities are allowed to execute in parallel
(are executed by separate threads).
By default, this is enabled, but in rare situations, it makes sense to disable this feature for some test projects.
Usually these are badly formulated activities, which do not care for synchronized access to shared data or data bases, and may therefore be not prepared for parallel execution.

Instead of disabling this feature, you should instead use synchronisation mechanisms in your activity diagram (i.e. either use trigger-out/trigger-in connections to enforce sequential execution, or use explicit semaphore actions to ensure mutual exclusion while doing such critical operations).

This parameter is stored in the test suite, not in the private per-user settings.

===== Start Process After =====
Due to the fact that starting up new processes (execution threads) is a relatively slow operation and takes up some processing
power, the expecco system delays the creation of new processes for some time,
in order to allow for short activities to finish without creating of a new process.
If an activity is finished within that time duration, no new process is created.
Effectively, short-term activities are sequentially executed,
as long as their processing takes less than this time duration.

This parameter is stored in the test suite, not in the private per-user settings.

===== Max. Number of Processes =====
This limits the number of parallel executing separate processes.
Because a process is a somewhat expensive resource in a computer (memory, disk space etc.),
allowing for an arbitrary number of separate processes might lead to a slowdown or even blocking of the computer's operation.

Effectively, expecco will keep a pool of worker threads for execution, which process pending activities. The max. number of worker threads is set by this parameter.

This parameter is stored in the test suite, not in the private per-user settings.

===== Max. Number of Executors per Testsuite =====
This limits the number of executors that can execute within the same test suite at the same time.
This parameter can be used to prevent tests which use global resources without locking from being executed in parallel
(eg. when the same test suite is executed against multiple systems-under-test,
or if expecco is operated as an execution slave (runtime) and multiple execution jobs for the same suite are coming from a central QM management system)

===== Max. Number of ExpeccoNET Test-Executions =====
This limits the number of test execution jobs from a QM-management system that can run in parallel to limit the overall load on the system .
This parameter is only used if expecco is used as a test slave processor
(for remote test execution, under the control of an expecco ALM or other QM management system).

=== Recursion ===
===== Max. Recursion Level =====
This parameter limits the nesting of activities during execution
(i.e. the nesting of compound activities which invokes another compound activity).
If this limit is reached, an error is raised, which leads to the current test case to be reported as erroneous.

This parameter is stored in the test suite, not in the private per-user settings.

=== Cleanup ===
===== Max. Cleanup Time =====
This parameter limits the max. execution time of cleanup
actions. This allows for cleanup actions which try to communicate with
dead connections to be terminated and thus avoids blocking.
If a cleanup action executes longer, a dialog is shown,
asking if a hard termination (i.e. termination without cleanup) or a wait for the action is desired by the user.
If expecco is executed in non-interactive mode (slave-mode or executed via command line),
the dialog is not shown. Instead, the cleanup action is hard terminated automatically after the max. cleanup time.

This parameter is stored in the test suite, not in the private per-user settings.

=== User Interface ===
===== Slow Motion Delay =====
This parameter introduces a delay between the execution of individual activities.
This is useful in demonstration or replay situations, where the user wants to
visually follow and monitor the execution of the individual steps.
It is also sometimes useful when debugging a test,
to slow down the process artificially.

===== Show "Do Not Disturb" Banner =====
If checked, a banner window is shown during the execution of a test plan.
This is useful to prevent other users from touching the machine, especially preventing
them from stopping or disturbing an ongoing, long running test. It is especially useful on the
test floor, where test machines are shared among different users.

===== Minimize Expecco while Executing=====
If checked, the expecco window is iconified during a test's execution.

Useful to see what is going on (and as a still-processing feedback monitor)
when running UI-Tests (eg. in a Browser) on a single screen.
This feature is introduced with rel 19.1.

===== Auto-Confirm Dialog Boxes =====
If checked, dialog boxes will automatically close themself after a given time period.
Set this, to let the suite run unattended and confirm all dialogs with their default (usually "OK"), but still get a chance to interact if required (within that time period).

=== Scripts ===
===== Execute in the Attachments Folder =====
If checked, scripts are executed within the Attachments folder;
if unchecked (the default), they are executed one folder above.
This flag is only present for backward compatibility with previous
expecco versions.

===== Keep Temporary Script Folders =====
For debugging only; by default, scripts are generated into temporary files for execution by a shell or language interpreter, and removed afterwards.
Set this to prevent removal for debugging (especially to debug the variable expansion mechanism).

<hr>

[[Settings/en|Back to the main page "Settings"]]
[[Category:Settings]]

Settings ExecutionSettings/en

2024-04-11T13:58:34Z

Alkurz:

== Execution Settings ==

=== Thread Pool ===
===== Separate Processes for Long Running Activities =====
This check toggle controls if multiple activities are allowed to execute in parallel
(are executed by separate threads).
By default, this is enabled, but in rare situations, it makes sense to disable this feature for some test projects.
Usually these are badly formulated activities, which do not care for synchronized access to shared data or data bases, and may therefore be not prepared for parallel execution.

Instead of disabling this feature, you should instead use synchronisation mechanisms in your activity diagram (i.e. either use trigger-out/trigger-in connections to enforce sequential execution, or use explicit semaphore actions to ensure mutual exclusion while doing such critical operations).

This parameter is stored in the test suite, not in the private per-user settings.

===== Start Process After =====
Due to the fact that starting up new processes (execution threads) is a relatively slow operation and takes up some processing
power, the expecco system delays the creation of new processes for some time,
in order to allow for short activities to finish without creating of a new process.
If an activity is finished within that time duration, no new process is created.
Effectively, short-term activities are sequentially executed,
as long as their processing takes less than this time duration.

This parameter is stored in the test suite, not in the private per-user settings.

===== Max. Number of Processes =====
This limits the number of parallel executing separate processes.
Because a process is a somewhat expensive resource in a computer (memory, disk space etc.),
allowing for an arbitrary number of separate processes might lead to a slowdown or even blocking of the computer's operation.

Effectively, expecco will keep a pool of worker threads for execution, which process pending activities. The max. number of worker threads is set by this parameter.

This parameter is stored in the test suite, not in the private per-user settings.

===== Max. Number of Executors per Testsuite =====
This limits the number of executors that can execute within the same test suite at the same time.
This parameter can be used to prevent tests which use global resources without locking from being executed in parallel
(eg. when the same test suite is executed against multiple systems-under-test,
or if expecco is operated as an execution slave (runtime) and multiple execution jobs for the same suite are coming from a central QM management system)

===== Max. Number of ExpeccoNET Test-Executions =====
This limits the number of test execution jobs from a QM-management system that can run in parallel to limit the overall load on the system .
This parameter is only used if expecco is used as a test slave processor
(for remote test execution, under the control of an expecco ALM or other QM management system).

=== Recursion ===
===== Max. Recursion Level =====
This parameter limits the nesting of activities during execution
(i.e. the nesting of compound activities which invokes another compound activity).
If this limit is reached, an error is raised, which leads to the current test case to be reported as erroneous.

This parameter is stored in the test suite, not in the private per-user settings.

=== Cleanup ===
===== Max. Cleanup Time =====
This parameter limits the max. execution time of cleanup
actions. This allows for cleanup actions which try to communicate with
dead connections to be terminated and thus avoids blocking.
If a cleanup action executes longer, a dialog is shown,
asking if a hard termination (i.e. termination without cleanup) or a wait for the action is desired by the user.
If expecco is executed in non-interactive mode (slave-mode or executed via command line),
the dialog is not shown. Instead, the cleanup action is hard terminated automatically after the max. cleanup time.

This parameter is stored in the test suite, not in the private per-user settings.

=== User Interface ===
===== Slow Motion Delay =====
This parameter introduces a delay between the execution of individual activities.
This is useful in demonstration or replay situations, where the user wants to
visually follow and monitor the execution of the individual steps.
It is also sometimes useful when debugging a test,
to slow down the process artificially.

===== Show "Do Not Disturb" Banner =====
If checked, a banner window is shown during the execution of a test plan.
This is useful to prevent other users from touching the machine, especially preventing
them from stopping or disturbing an ongoing, long running test. It is especially useful on the
test floor, where test machines are shared among different users.

===== Minimize Expecco while Executing=====
If checked, the expecco window is iconified during a test's execution.

Useful to see what is going on (and as a still-processing feedback monitor)
when running UI-Tests (eg. in a Browser) on a single screen.
This feature is introduced with rel 19.1.

===== Auto-Confirm Dialog Boxes =====
If checked, dialog boxes will automatically close themself after a given time period.
Set this, to let the suite run unattended and confirm all dialogs with their default (usually "OK"), but still get a chance to interact if required (within that time period).

=== Scripts ===
===== Execute in the Attachments Folder =====
If checked, scripts are executed within the Attachments folder;
if unchecked (the default), they are executed one folder above.
This flag is only present for backward compatibility with previous
expecco versions.

===== Keep Temporary Script Folders =====
For debugging only; by default, scripts are generated into temporary files for execution by a shell or language interpreter, and removed afterwards.
Set this to prevent removal for debugging (especially to debug the variable expansion mechanism).

----

[[Settings/en|Back to the main page "Settings"]]
[[Category:Settings]]

Settings LoggingSettings/en

2024-04-11T13:54:57Z

Alkurz: /* Logging Settings */

=== Overview ===
Activity log entries remember the result of a step's execution. They usually include information
about the input pin values, the execution time, the outcome (verdict) and the generated output value(s).
The activity log is (currently) stored in memory, to avoid excessive slow-down of the tests execution.

The activity log as generated by long running extensive tests may become very large and consume
lots of memory - sometimes more than can be kept and prunning (cutting off parts of the trace) is
required. For such tests, it might be useful to disable the logging of certain actions and/or steps and/or pins. This can be controlled via popup menus of steps and pins in the diagram editor.

In contrast to activity logs, traces as sent to the Transcript (Console) are not persistent and will be lost when the Transcript window is closed (unless the contents is captured and saved explicitly, via one of the Transcript action blocks)

== Logging Settings ==
These are found in "''Settings''" - "''Execution''" - "''Logging''".

=== Log Activities ===
If enabled, every activity is stored in the activity log.
If disabled, only failed activities are stored.
There will be always one master (top-level) entry stored, which keeps the overall
outcome of an execution, even for passed runs with disabled logging.

''This parameter can be set and saved directly in the test suite.
When a new test suite is created, the value from the settings dialog is used as the default value.''

=== Log Pin Data ===
If enabled, all input and output pin values are stored in the activity log.
Otherwise all values are discarded and pin values cannot be inspected after the test run.

''This parameter can be set and saved directly in the test suite.
When a new test suite is created, the value from the settings dialog is used as the default value.''

=== Log Info ===
If enabled, all information messages
(i.e. messages as generated by explicit logInfo calls and logInfo blocks)
are stored in the activity log.
Otherwise information messages are discarded.

''This parameter can be set and saved directly in the test suite.
When a new test suite is created, the value from the settings dialog is used as the default value.''

=== Log GUI Screenshots Automatically on Error ===
If enabled, GUI action blocks which encounter an error (typically: element/xpath not found) will automatically generate a screenshot and add this to the activity log. Be aware that this may generate a huge number of images and lead to excessive memory use and even a failure when running out of memory (especially on 32bit machines). SO this feature should only be used during development.

=== Log External OS Commands ===
If enabled, all executed OS commands (shell/script interpreter calls, etc.)
will be logged in the activity log.

=== Log System Activity Notifications ===
If enabled, activity information notifications
(i.e. implicit notifications of the underlying language framework)
are stored in the activity log as info log entries.
Otherwise information messages are discarded.

The default is false (used to be true in pre 2.1 releases).

=== Timestamps have Microsecond Resolution ===
If enabled, timestamps are kept with microsecond resolution (if the underlying operating system supports them);
otherwise, they are generated with millisecond resolution.

The default is false for backward compatibility with older expecco versions.

=== Ignore any "Skip in Trace" Attribute ===
Enforces an activity log/trace to be generated for all steps/pin values,
even if individual steps/pins have the "''Skip in Trace''"
attribute set.

=== Prefix for log output ===

An environment variable called__Transcript_Prefix__ can be defined in a test suite.
When text from this test suite is written to Transcript, the value of the variable is also output as a prefix.

== Tracing Settings ==
These are found in "''Settings''" - "''Execution''" - "''Tracing''".

=== Show Internal Warning and Info Messages ===
Probably only useful for diagnostics of expecco itself

=== Show Actions being Executed===
If enabled, the currently executed action's name is shown in the lower info area (not in the Transcript).
It can be further filtered by tag.

=== Logger Treshold ===
Defines a treshold which controls the set of Logger messages to be shown. Logger messages are typically produced internally eg. to display progress, errors etc. Many logger messages are meant for expecco developers, however some might be also of interest during test development.
Logger messages are associated a severity, which can be TRACE, DEBUG, INFO, WARNING, ERROR or FATAL.
Only logger messages with a greater-or-equal severity will be shown by the logger.
 By default, this treshold is set to "WARNING".

=== Show External Commands on Transcript ===
If on, executed shell, batch, script and other OS commands will be
traced on the Transcript.

=== Show Stdout and Stderr on Transcript ===
If on, the stdout/stderr of executed external programs is
traced on the Transcript (stderr in red).

=== Show Outgoing HTTP Requests on Transcript ===
Outgoing HTTP requests (from the HTTP-get/put actions) will be traced on the Transcript.

=== Show Outgoing SOAP Requests on Transcript ===
Outgoing SOAP requests will be traced on the Transcript.

=== Show IMAP and POP3 Protocol on Transcript ===
Interactions with the mailbox are traced on the Transcript.

=== MessageTally on Execution ===
If checked, execution times of elementary activities are measured and
an execution profile is generated after the execution (on the Transcript window).
This is useful to find out where time is spent for performance optimizations.

=== Coverage Recording onExecution ===
If checked, executed actions are instrumented to record which parts are executed and which are not.
(this is an unfinished feature, which may or may not work in your particular version of expecco)

Settings LoggingSettings/en

2024-03-27T17:26:29Z

Alkurz: /* Logging Settings */

=== Overview ===
Activity log entries remember the result of a step's execution. They usually include information
about the input pin values, the execution time, the outcome (verdict) and the generated output value(s).
The activity log is (currently) stored in memory, to avoid excessive slow-down of the tests execution.

The activity log as generated by long running extensive tests may become very large and consume
lots of memory - sometimes more than can be kept and prunning (cutting off parts of the trace) is
required. For such tests, it might be useful to disable the logging of certain actions and/or steps and/or pins. This can be controlled via popup menus of steps and pins in the diagram editor.

In contrast to activity logs, traces as sent to the Transcript (Console) are not persistent and will be lost when the Transcript window is closed (unless the contents is captured and saved explicitly, via one of the Transcript action blocks)

== Logging Settings ==
These are found in "''Settings''" - "''Execution''" - "''Logging''".

=== Log Activities ===
If enabled, every activity is stored in the activity log.
If disabled, only failed activities are stored.
There will be always one master (top-level) entry stored, which keeps the overall
outcome of an execution, even for passed runs with disabled logging.

This setting value is stored in and loaded from the project, not the user's private settings file.

=== Log Pin Data ===
If enabled, all input and output pin values are stored in the activity log.
Otherwise all values are discarded and pin values cannot be inspected after the test run.

The default value is stored in the testsuite, not in the user's private settings file.

=== Log Info ===
If enabled, all information messages
(i.e. messages as generated by explicit logInfo calls and logInfo blocks)
are stored in the activity log.
Otherwise information messages are discarded.

The default setting is stored in the testsuite, not in the user's private settings file.

=== Log GUI Screenshots Automatically on Error ===
If enabled, GUI action blocks which encounter an error (typically: element/xpath not found) will automatically generate a screenshot and add this to the activity log. Be aware that this may generate a huge number of images and lead to excessive memory use and even a failure when running out of memory (especially on 32bit machines). SO this feature should only be used during development.

=== Log External OS Commands ===
If enabled, all executed OS commands (shell/script interpreter calls, etc.)
will be logged in the activity log.

=== Log System Activity Notifications ===
If enabled, activity information notifications
(i.e. implicit notifications of the underlying language framework)
are stored in the activity log as info log entries.
Otherwise information messages are discarded.

The default is false (used to be true in pre 2.1 releases).

=== Timestamps have Microsecond Resolution ===
If enabled, timestamps are kept with microsecond resolution (if the underlying operating system supports them);
otherwise, they are generated with millisecond resolution.

The default is false for backward compatibility with older expecco versions.

=== Ignore any "Skip in Trace" Attribute ===
Enforces an activity log/trace to be generated for all steps/pin values,
even if individual steps/pins have the "''Skip in Trace''"
attribute set.

=== Prefix for log output ===

An environment variable called__Transcript_Prefix__ can be defined in a test suite.
When text from this test suite is written to Transcript, the value of the variable is also output as a prefix.

== Tracing Settings ==
These are found in "''Settings''" - "''Execution''" - "''Tracing''".

=== Show Internal Warning and Info Messages ===
Probably only useful for diagnostics of expecco itself

=== Show Actions being Executed===
If enabled, the currently executed action's name is shown in the lower info area (not in the Transcript).
It can be further filtered by tag.

=== Logger Treshold ===
Defines a treshold which controls the set of Logger messages to be shown. Logger messages are typically produced internally eg. to display progress, errors etc. Many logger messages are meant for expecco developers, however some might be also of interest during test development.
Logger messages are associated a severity, which can be TRACE, DEBUG, INFO, WARNING, ERROR or FATAL.
Only logger messages with a greater-or-equal severity will be shown by the logger.
 By default, this treshold is set to "WARNING".

=== Show External Commands on Transcript ===
If on, executed shell, batch, script and other OS commands will be
traced on the Transcript.

=== Show Stdout and Stderr on Transcript ===
If on, the stdout/stderr of executed external programs is
traced on the Transcript (stderr in red).

=== Show Outgoing HTTP Requests on Transcript ===
Outgoing HTTP requests (from the HTTP-get/put actions) will be traced on the Transcript.

=== Show Outgoing SOAP Requests on Transcript ===
Outgoing SOAP requests will be traced on the Transcript.

=== Show IMAP and POP3 Protocol on Transcript ===
Interactions with the mailbox are traced on the Transcript.

=== MessageTally on Execution ===
If checked, execution times of elementary activities are measured and
an execution profile is generated after the execution (on the Transcript window).
This is useful to find out where time is spent for performance optimizations.

=== Coverage Recording onExecution ===
If checked, executed actions are instrumented to record which parts are executed and which are not.
(this is an unfinished feature, which may or may not work in your particular version of expecco)