Expecco Reflection Library: Unterschied zwischen den Versionen
Cg (Diskussion | Beiträge) |
K |
||
| Zeile 1: | Zeile 1: | ||
== Introduction == |
== Introduction == |
||
The Reflection Library contains building blocks to automate expecco itself. |
The Reflection Library contains building blocks to automate expecco itself. |
||
Its main use is to automatically generate test suites or libraries. |
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 |
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. |
||
generate test skeletons or concrete action blocks and/or test suites. |
|||
For more information, please refer to the documentation and examples |
For more information, please refer to the documentation and examples |
||
| Zeile 12: | Zeile 11: | ||
The reflection library can be used to: |
The reflection library can be used to: |
||
* automatically generate testsuites from textual descriptions |
* automatically generate testsuites from textual descriptions |
||
* automatically generate datatypes ( |
* automatically generate datatypes (e.g. from textual descriptions) |
||
* merge, filter testsuites |
* merge, filter testsuites |
||
* bulk renaming, bulk annotating of elements in a number of suites |
* bulk renaming, bulk annotating of elements in a number of suites |
||
| Zeile 24: | Zeile 23: | ||
== Project Manipulation == |
== Project Manipulation == |
||
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). |
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). |
||
Version vom 15. Juli 2017, 19:25 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.
For more information, please refer to the documentation and examples inside the library.
Typical Uses[Bearbeiten]
The reflection library can be used to:
- automatically generate testsuites from textual descriptions
- automatically generate datatypes (e.g. from textual descriptions)
- merge, filter testsuites
- bulk renaming, bulk annotating of elements in a number of suites
- extraction of annotations from a number of suites
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.
