Test Execution Monitor Window/en: Unterschied zwischen den Versionen
Cg (Diskussion | Beiträge) (Die Seite wurde neu angelegt: „== Introduction == Expecco can be configured to present a custom dynamic GUI while executing. This user interface is defined and controlled by the action being…“) |
Cg (Diskussion | Beiträge) |
||
| Zeile 2: | Zeile 2: | ||
Expecco can be configured to present a custom dynamic GUI while executing. This user interface is defined and controlled by the action being executed, and can vary (i.e. changed) dynamically. Useful scenarios for this are test stands, where you want to hide the internals of the execution from the test operator, or to present additional data (monitoring) or to ask interactively for parameters or other input values. |
Expecco can be configured to present a custom dynamic GUI while executing. This user interface is defined and controlled by the action being executed, and can vary (i.e. changed) dynamically. Useful scenarios for this are test stands, where you want to hide the internals of the execution from the test operator, or to present additional data (monitoring) or to ask interactively for parameters or other input values. |
||
Of course, the simple dialog requests can also be used for parameter questions, but a custom UI |
Of course, the simple dialog requests can also be used for parameter questions, but a custom UI can both provide a better look and allow for more complex user interaction to be defined. |
||
| ⚫ | |||
| ⚫ | |||
== Getting Started == |
== Getting Started == |
||
* First, create a new compound action, |
* First, create a new compound action, |
||
Version vom 18. Februar 2021, 09:35 Uhr
Introduction[Bearbeiten]
Expecco can be configured to present a custom dynamic GUI while executing. This user interface is defined and controlled by the action being executed, and can vary (i.e. changed) dynamically. Useful scenarios for this are test stands, where you want to hide the internals of the execution from the test operator, or to present additional data (monitoring) or to ask interactively for parameters or other input values.
Of course, the simple dialog requests can also be used for parameter questions, but a custom UI can both provide a better look and allow for more complex user interaction to be defined.
The general mechanism is based on attaching a UI individual (compound) actions, which is shown whenever the action is active.
Getting Started[Bearbeiten]
- First, create a new compound action,
and go to its schema tab.
- at the bottom, find the button named "GUI"and click on it. A UI-editor will open, showing 3 views:
- the main view, containing the widget hierarchy and attributes,
- a drawing canvas, which shows how the UI will look
- and a widget gallery, from which UI elements can be dragged into the widget hierarchy to into the drawing canvas.
- now - for a simple example, drag a simple "OK" button and a ListView from the gallery into the canvas
- press "Save"and close the editor.
- place a simple "Delay for a few seconds" action into the action's activity diagram, so the UI will show itself for a while, while the action is active.
- press "Run"
You will now probably get an error outcome, stating the the UI was disabled in the project. This is the default, and you should enable this first in the project's "Execution" tab.
Run it again.
Your UI should now show up, while the compound action is active, and disappear later. Of course, we did not yet connect any data or callback actions with the UI's elements.
