New Window Manager: Views Open Separate Windows
The views no longer open within the client window, but as separate windows of the operating system.
Switching between the windows can be done via ALT-TAB. From all windows, all windows are accessible via the respective status bar.
Assigning elements via drag & drop is done across windows, even across multiple screens.
The windows have a progress display and are restored exactly (size, position, screen) when the client is started.
Compare Versions
Versions of test case sets and test elements can be compared. The result is opened in the browser as a web page.
The comparison and the content to be compared can be set individually.
Quick Access to Plugins
A plugin can be defined for the specification and the execution respectively, which appears as an additional button in the management information of the specification and under the buttons for starting the manual test execution.
The plugin can be executed directly without indirection via these buttons.
Assign from Browser and Show Textual Steps
To display the structure of elements, they can be dragged into the browser.
All displayed elements can now be assigned from the browser anywhere.
In the browser, the first characters from the description of the textual test steps are displayed as the name.
(Same functionality as in iTORX)
Default Values for Parameters
Default values can be set for parameters in the parameter lists of test case sets and interactions.
If new test cases are created for test case sets, the default values from the parameter list are used instead of the “red ?”.
When interactions are called in test sequences, the default values are also used instead of the “red ?”.
In test sequences, the default values from the parameter list of a called interaction can be set directly via keyboard shortcut CTRL-M.
If another default value is set, all values preset with the default value also change.
Use References Directly as Parameter Values
A new test element, the reference data type, allows references (attachments, file references, hyperlinks) to be used directly as representatives.
Reference data types are atomic data types whose representatives can be used in the same way as the representatives of the standard data types.
The representatives of the reference data types can be distinguished from normal representatives by a preceding icon.
Advanced Content for Interactions
In addition to the description, interactions can manage other information. The content is given a type so that it can be better displayed and processed externally.
In these advanced contents, e.g. control data or code snippets can be used in test execution.
Versions and Usages of Test Elements Merged
For a better overview, the versions and usages for test elements are now on the same tab card.
Furthermore the following was added:
- Information about the version
- Accessible visualization of the loaded version
- Change marker
Versions and usages are on a same tab card for test elements and contain additional information.
Show Detailed Use of Test Elements
In the test element view, all its uses can be displayed for a test element. The uses are displayed for all versions of the test element.
For each usage, it is also shown whether the usage lies within or outside the associated subtree. For data types, the usage of its representatives is also taken into account.
The detailed uses can also be displayed for all elements of a subdivision. In this way it can be determined, for example, whether a subdivision can be deleted or whether there are still uses outside the subdivision.
Convert Atomic to Detailed Instance Lossless
If the parameter of a test case set is subsequently converted from an atomic instance to a detailed instance, the values of the underlying subdata types are entered in the test case table.
The same applies accordingly to the conversion of a detailed instance into an atomic instance.
Atomic instances are converted lossless to detailed and vice versa.
Test Object Version-wide Representatives
For values with certain semantics it makes sense not to define these values again in each data type, but to have a possibility to define these values at a central place.
Such a value can be e.g. the “explicit empty value”, so that everywhere uniformly a value can be set to explicit empty.
Another new test element, the global data type, is used for this purpose. Its representatives can be selected in the selection lists of other data types of the same test object version. For this purpose, the use of the global data types must be allowed for these other data types.
Test Element Libraries
Test elements (interactions, data types and conditions) can be centrally grouped in libraries within a test object version. These libraries can be used in other test object versions.
The basic functions are:
- Consistent stands of the elements of a library are created and versioned as baselines.
- Updating to new versions (= new baselines) of a library is possible.
- The test elements of a library are read-only in the test object version being used, so they can only be changed centrally.
- Libraries can have dependencies on other libraries.
Requirement Coverage and Test Status Distribution
Requirements management displays metrics for baselines on the coverage of requirements by tests and the distribution of the test status of requirements.
If multiple baselines are present, the metrics are also output over all baselines in total.
In the context menu of a metric the graph can be saved or printed.
Metrics for the coverage of requirements by tests and for the distribution of the test status of the requirements.
Show Requirement-ID in the Requirement Tree
The ID of a requirement can be shown in the tree of requirements.
The ID of a requirement, compared to the title, is more often used to identify a requirement and now can be seen directly.
