Expecco Reflection Library: Unterschied zwischen den Versionen
Cg (Diskussion | Beiträge) |
Cg (Diskussion | Beiträge) |
||
Zeile 16: | Zeile 16: | ||
Includes blocks to create test suites, to manipulate environments (create/modify variables), |
Includes blocks to create test suites, to manipulate environments (create/modify variables), |
||
and to load and save test suite files (".ets"-files). |
and to load and save test suite files (".ets"-files). |
||
There are both blocks which operate on a browser window, and blocks which operate on a project object itself (i.e. without a need for a browser window). |
|||
== Tree Manipulation == |
== Tree Manipulation == |
Version vom 18. Dezember 2015, 19:28 Uhr
Inhaltsverzeichnis
Introduction[Bearbeiten]
The Reflection Library contains building blocks to automate expecco itself. Its main use is to automatically generate test suites or libraries. For example, to import specifications in a textual format, a database or a QM-system and generate test skeletons or concrete action blocks and/or test suites.
Please refer to the documentation in the libraries action items.
Browser Manipulation[Bearbeiten]
These include blocks to simulate various user actions, either towards the currently running expecco application, or to a secondary expecco window. For example, to open, close expecco windows, to switch to particular tabs, or to change the selection in the item tree.
Project Manipulation[Bearbeiten]
Includes blocks to create test suites, to manipulate environments (create/modify variables), and to load and save test suite files (".ets"-files). There are both blocks which operate on a browser window, and blocks which operate on a project object itself (i.e. without a need for a browser window).
Tree Manipulation[Bearbeiten]
Includes blocks to create actions, datatypes, attachments and folders in a project's item tree.
Diagram Editing[Bearbeiten]
Includes blocks to create activity diagrams, to add steps and to connect pins.
Text Editing[Bearbeiten]
These operate on the currently running expecco, and are mostly useful for code-generation utilities, which can be bound to user-defined menu items.
Execution[Bearbeiten]
This allows for a testplan to be executed automatically, under control of another activity.
Reporting[Bearbeiten]
Actions to generate test reports.