Tree Elements
Aus ExpeccoWiki
Tree elements are all elements in a testsuite. They are displayed and managed in the so-called project tree.
Inhaltsverzeichnis |
IDs
Each element in the project has two unique IDs. One is the so called "Functional-ID" which is assigned once, when the element is created initially and never changed thereafter. The other is the "Version-ID". This is reassigned with every modification.
The "Version-ID" is used to quickly detect identical elements (for example, when merging projects from different files).
The "Functional-ID" is used when reimporting libraries; i.e. to identify which blocks should be automatically replaced by newer versions.
The name of a tree element is not used by the system to identity elements; this is only used for presentation to the user.
Tests
Testplan
A testplan contains a collection if test cases. A testcase-item can be either an activity, or another testplan. Testcases within a testplan are executed sequentially.
Performancetest
A performance test is used to collect load and performance test specific items.
Libraries
Libraries are collections of blocks. They are nested in the "Imports" node. Libraries like the standard library or the Qt-Interface library are provided by eXept. However, you can also create your own project-specific libraries. Or provide them as a supplier to third party. Libraries can contain any type of element, including dataTypes, attachments, elementary and compound blocks.
Already included in all releases of expecco are the following libraries:
Upon request, other libraries are available. For example:
- Interfaces to specific rich-client GUIs (Qt, JavaSwing, ST/X, Ranorex)
- Interfaces to specific applications like SAP, Siebel, ...
- Databases
- Webservices
- CAN/MOST
- GPIB, VISA
Reimport a library
A reimport is needed to upgrade a project's imported libraries to a new version.
Virtual Library
Virtual libraries allow for the behavior of a group of actions to be determined and changed at runtime.
Blocks
Elementary Block
An elementary block is a block which is not defined by an activity diagram. For example built-in functions, DLL-calls and JavaScript functions.
Compound Block
A compound block is a block which is defined by an internal activity diagram.
Virtual Block
A virtual block is used to place a step whose execution is defined dynamically at runtime. Similar to a virtual function in programming languages, only the block's interface is defined in a network. At execution time, one of multiple concrete actions is choosen to be actually executed.
Test Data Generator Block
A test data generator block is used to generate simple tabular data for a test.
Compound GUI Block
An compound GUI block is used to model non-modal user interfaces.
Elementary GUI Block
An elementary GUI block is used to model modal (blocking) user interfaces.
Management
Datatype
A datatype element allows the creation of user-defined data types.
Skill
A skill is a part of the description of a resource or the requirement of a block.
Resource
A resource element represents a physical, logical or human resource. Examples for physical resources are measurement devices, equipment or human operators. Non-physical resources are database-locks or synchronization semaphores.
Inventory
An inventory is a collection of resources.
Miscellaneous
Attachment
An attachment is used to manage any file together with a test suite.
Documentation
A documentation element is used to document the test suite.
Report Template
A report template is used to customize a report.
The full online documentation can be found under: Online Documentation