Testsuite Editor-Metadata Editor/en: Unterschied zwischen den Versionen

Aus expecco Wiki (Version 2.x)
Zur Navigation springen Zur Suche springen
 
(13 dazwischenliegende Versionen desselben Benutzers werden nicht angezeigt)
Zeile 40: Zeile 40:


=== GUI Extensions ===
=== GUI Extensions ===
==== Operation Menu ====
Allows for a folder full of actions to be attached to expecco's main-menu. If a folder is dropped into that field, all of that folder's actions are presented as menu items in the "Extra" menu.
Allows for a folder full of actions to be attached to expecco's main-menu. If a folder is dropped into that field, all of that folder's actions are presented as menu items in the [[ExtrasMenu | "''Extras''" menu]] (or optionally in the main menu).
This is very useful to make common functions (calibration, test-setup, tear-down etc.) easily accessible to the test-operator.
This is very useful to make common functions (calibration, test-setup, tear-down etc.) easily accessible to the test-operator.


The action will be executed whenever the corresponding menu item is selected, independent of any ongoing test executions.
The action will be executed whenever the corresponding menu item is selected, independent of any ongoing test executions.

<!-- ==== Background Actions ====
==== In Main Menu ====
By default, the menu operation is synchronous, which means that expecco waits for the action to finish. While executing, the expecco UI is blocked. If that is not desired, or if an action needs to remain active during the whole test execution (for example, if a shell script is to be executed in parallel), append an ampersand character ("&") to the action's name. In that case, the menu item will execute the block in a separate thread in the background. This is especially useful to start external programs, Java bridges or the System Under Test itself. -->
If this flag is checked, the operations menu is shown as a separate entry in the main menu. Otherwise the items are sliced into the [[ExtrasMenu | "''Extras''" menu]].

==== Include Imported Menus ====
If this flag is checked, operation menu entries from imported libraries are also included.

==== Background Menu Actions ====
By default, the menu operations are synchronous, which means that expecco waits for the action to finish. While executing, the expecco UI is blocked. If that is not desired, or if an action needs to remain active during the whole test execution (for example, if a shell script is to be executed in parallel), append an ampersand character ("&") to the action's name. In that case, the menu item will execute the block in a separate thread in the background. This is especially useful to start external programs, Java bridges or the System Under Test itself.
<br>See more in [[User_Defined_Menu_Items | User Defined Menu Items]]


=== Testplan Execution ===
=== Testplan Execution ===
Allows for additional pre- and post-execution actions to be automatically executed with any test plan execution. Different actions can be specified depending on the test plan's outcome, for example to trigger further reporting or alarm processing. It may also be used to add actions which send email notifications or which contact a QM-system for automatic issue generation (e.g. into Bugzilla, jira or other bug tracking systems).
Allows for additional pre- and post-execution actions to be automatically executed with any test plan execution. Different actions can be specified depending on the test plan's outcome, for example to trigger further reporting or alarm processing. They may also be used to add actions which send email notifications or which contact a QM-system for automatic issue generation (e.g. into Bugzilla, Jira or other bug tracking systems).


Notice:<br>These actions are not logged in the activity-log. Because they are not logged, they should not have any influence on the actual test execution. Especially, they should not be used to setup equipment, protocols etc.
[[Datei:point_right.png|20px]] Notice: These actions are not logged in the activity-log. Because they are not logged, they should not have any influence on the actual test execution. Especially, they should not be used to setup equipment, protocols etc.
Only use them for "meta" operations, such as statistics, reporting, etc.
Only use them for "meta" operations, such as statistics, reporting, etc.


Pre- and post actions which do affect the test execution should be defined in the testplan, which also provides pre- and post execution hooks.
Pre- and post actions which do affect the test execution should be defined in the testplan, which also provides pre- and post execution hooks. Testplan hooks will be logged in the report.


Also notice: errors in these actions may open a debugger, ignoring your "''Open Debugger on Error''" settings.
Also notice: errors in these actions may open a debugger, ignoring your "''Open Debugger on Error''" settings.

Aktuelle Version vom 18. Februar 2020, 17:47 Uhr

Misc Editor (outdated screenshot - the current version shows more fields)

The misc editor is used to view and edit some miscellaneous settings and additional information for the test suite or (in a readonly version) for imported suites or libraries. It can be found on the "Misc" tab after selecting the test suite in the navigation tree.

To the right, you see an example for an opened misc editor.

Version[Bearbeiten]

Release Name
An optional field for a descriptive name of the test suite's version.
Author
An optional field for the name of the test suite's author (filled in automatically).
Version
This shows an internally generated version number useful to quickly identify the current version. It is constructed from a sequential number and the suite's last edit author. The sequence number will be incremented whenever the suite is saved.

Project File Path[Bearbeiten]

The path to the file from which the current testsuite was loaded. Only used for documentation.


Library Interface[Bearbeiten]

For a concrete library, this field specifies which virtual library interface is implemented by this library. For more information please read the section on virtual blocks and virtual libraries.

Prerequisites[Bearbeiten]

Expecco Version[Bearbeiten]

Allows for the minimum required expecco version for this test suite to be specified. If this suite is loaded into an older expecco, a warn box will appear (this is useful for libraries which call into the expecco API and use functions which are not present in older versions).

Extension Packages[Bearbeiten]

Lists required extension packages from the underlying execution framework. This is especially used by plugin-libraries which require additional low-level DLL functionality. Packages are named using the standard Smalltalk/X package naming scheme (foo:bar/baz/...). For an extension package to be found, it must be located below the expecco installation directory in a directory named "foo/bar/baz/..." under the "packages" subfolder.

Plugin UUIDs[Bearbeiten]

Lists the required plugin id(s). Used by libraries which require a specific plugin to be present. Especially used by plugin-libraries which implement a block interface to the plugin's operations. To verify at package loading time, that any API entries used by extension blocks will be present at execution time.

Load / Unload[Bearbeiten]

Allows for an action to be automatically executed whenever the suite (or import library) is loaded / unloaded. This can be used to check for the availability of hardware, software or to give additional information automatically to a test operator. To use this, simply drag and drop an existing activity block into one of these fields.

Point right.png Notice: these actions are only executed if the suite is loaded interactively via the user interface. They are (by purpose) not executed when tests are executed automatically (via command line or inside a test-host). There are multiple reasons for this, one being that suites might be composed from multiple files and executed as a single suite, and that the preLoad/postLoad actions are usually meant to either add project specific menu items to the expecco UI, or to perform other test-developer related actions. Executing those on any load of a suite would make the behavior very nondeterministic, especially in view that loaded suites are cached inside expecco when running as a test host for expecco ALM or other QM systems.

GUI Extensions[Bearbeiten]

Operation Menu[Bearbeiten]

Allows for a folder full of actions to be attached to expecco's main-menu. If a folder is dropped into that field, all of that folder's actions are presented as menu items in the "Extras" menu (or optionally in the main menu). This is very useful to make common functions (calibration, test-setup, tear-down etc.) easily accessible to the test-operator.

The action will be executed whenever the corresponding menu item is selected, independent of any ongoing test executions.

In Main Menu[Bearbeiten]

If this flag is checked, the operations menu is shown as a separate entry in the main menu. Otherwise the items are sliced into the "Extras" menu.

Include Imported Menus[Bearbeiten]

If this flag is checked, operation menu entries from imported libraries are also included.

Background Menu Actions[Bearbeiten]

By default, the menu operations are synchronous, which means that expecco waits for the action to finish. While executing, the expecco UI is blocked. If that is not desired, or if an action needs to remain active during the whole test execution (for example, if a shell script is to be executed in parallel), append an ampersand character ("&") to the action's name. In that case, the menu item will execute the block in a separate thread in the background. This is especially useful to start external programs, Java bridges or the System Under Test itself.
See more in User Defined Menu Items

Testplan Execution[Bearbeiten]

Allows for additional pre- and post-execution actions to be automatically executed with any test plan execution. Different actions can be specified depending on the test plan's outcome, for example to trigger further reporting or alarm processing. They may also be used to add actions which send email notifications or which contact a QM-system for automatic issue generation (e.g. into Bugzilla, Jira or other bug tracking systems).

Point right.png Notice: These actions are not logged in the activity-log. Because they are not logged, they should not have any influence on the actual test execution. Especially, they should not be used to setup equipment, protocols etc. Only use them for "meta" operations, such as statistics, reporting, etc.

Pre- and post actions which do affect the test execution should be defined in the testplan, which also provides pre- and post execution hooks. Testplan hooks will be logged in the report.

Also notice: errors in these actions may open a debugger, ignoring your "Open Debugger on Error" settings.



Copyright © 2014-2024 eXept Software AG