Distribution of Test Specification Status
In each test theme, the distribution of the status in the subtree is displayed.
Inside the context menue of the metric the graphic can be saved or printed.
For the root of the test theme tree, the Current View, the status distribution is displayed for the whole tree.
Accessibility
The colors of the graphics can be adjusted for each client.
In the clients "bin" directory the file "nimbus.properties" exists in which the colors are defined.
Suggestions for the different color deficiencies are stored, which every user can adapt individually to his needs.
Find the Location of a Filter
Deeply nested trees often contain many different filters at various positions on the trees. The position of a filter can now easily be found in the tree.
Double click on the filter name jumps to the definition of the filter in the filter administration.
Direct Checkout of New Versions
Loaded or (locked) versions checked in by the system can be checked out immediately, switching to the version list is no longer necessary.
In these cases the check-in button changes to a check-out button.
Details of Assigned Requirements
The details of a requirement are displayed directly in the test specification. The switching to the requirement management can be omitted.
This is valid for requirements for test themes and test case sets.
Parameter Titles of the Test Sequences
The table titles of the parameters in the test sequence adapt to the parameters of the selected line.
The parameter names of the called interaction are displayed, which are also shown in the tooltip of the parameter.
"Goto" from the Browser (Static View)
The browser is used to visualise structures in the Keyword Driven Test and in the Data Driven Test. Jumping to the displayed elements is now possible.
The existing functionalities are now also accessible via the context menu.
Identify Used Test Elements
Interactions used in test sequences of test case sets can be identified in the auxiliary objects view.
Double click on the name has the same function as the context menu.
Double click in the number column jumps to the element in the test design view.
Distribution of Test Execution Status
In each test theme, the distribution of the status in the subtree is displayed. In the test execution the test cases are counted.
Inside the context menue of the metric the graphic can be saved or printed.
For the root of the test theme tree, the Current View, the status distribution is displayed for the whole tree.
Offline Development of MS Word Reports
Microsoft Word reports can be created using the command line tool generate-word-report.bat or generate-word-report.sh.
Locally stored XML reports are processed directly. An export via the client is only necessary once.
The package can be requested via support(at)imbus.de.
Extending released data types
The modules (test elements) of the Keyword-Driven Test are locked for all changes from the moment they receive the status "released". However, if data types are used in additional modules or tests, it is often necessary to insert new values in the equivalence classes and data tables, as the existing ones are not sufficient. Up to now, in such cases, the data type was reset to the status "in progress", which then led to the reset of the status "released" of all elements using it.
From now on, additional, new values can also be entered in released data types, i.e. they no longer have to be reset to the status "in progress".
Data and values existing at the time of release can of course still not be changed.
Drag interactions and data types directly into static view
With the modules (test elements) of the Keyword-Driven Test, very complex structures can be modeled in a very compressed way. To see the complexity of a test element at a glance, you can use the static view of the Test Element Browser.
Test elements can now be dragged directly from their position of use within test sequences or parameter lists into the static view. This makes the analysis of existing test definitions a bit easier and faster again.
Jump exactly in place of use
For each element in the TestBench, it is stored which other elements use or call this element. This makes it easy to determine which elements are affected by changes, for example, or which tests need to be repeated after a change. From this so-called usage list, you can jump directly to the user.
From now on, you can jump directly to the position of use within the using element. For example, for interactions (keywords of the keyword-driven test), the system jumps directly to the test definition and marks the position of the interaction within the test sequence.
This makes jumping between elements noticeably easier and faster. Impact analyses of changes are simplified.
Optimized assignment of errors
It is now easier to assign errors to test cases:
- Test cases no longer have to be preselected, but errors can be assigned directly to a test case in the list of test cases.
- Errors can be assigned to all test cases simultaneously or removed from all test cases simultaneously.
Updating a variant
Within the variant management, changes within a basic test object version (basic TOV) can now be transferred to already derived variants. The transfer is carried out manually from the variant, so that variants can be checked and only updated if there is a real need to update them.
Complete variants, individual sub-trees of the test theme tree or individual tests can be updated.
It is also possible to copy new elements from the basic TOV to a variant. In this cases the derivation for the variant is performed automatically.
New plugins to integrate the Robot Framework
The integration of the Robot Framework with the test automation interface of the TestBench was newly implemented.
There are now three plugins available:
- Robot Framework Export-Plugin
Serves to prepare the test specification for execution of the automated tests with the Robot Framework.
The tests can be called directly from the plugin if required. - Robot Framework Import-Plugin
Used to transfer test results from the Robot Framework to the TestBench. - Robot Framework Library Import-Plugin
A large number of libraries exist around the Robot Framework to facilitate the test specification of specific systems or environments. For example there are several libraries around Selenium available. With the help of the plugin, the libraries can be imported into the TestBench, where they are available as test elements in the keyword-driven test. In this way, tests can be specified that can be executed quasi out-of-the-box automatically.
Testing Intelligence: Save presentation of the diagrams
The settings for displaying the diagrams in the Testing Intelligence metric add-on are now saved permanently:
- Grouped or stacked display of bar charts
- Hidden statuses
Hidden statuses can be shown again by simply clicking on the legend.
If these statuses are to become invisible, they can be completely removed from the display.
Testing Intelligence: Filtering by keywords
In the TestBench, the most frequently used mechanism is to mark tests or combine them into sets, that is, the assignment of keywords to tests.
For example, a keyword can mark all tests to be executed automatically every night, which can then be filtered to generate reports or evaluations of the nightly test runs.
This mechanism for filtering by keywords is now also available directly in Testing Intelligence, i.e. the data displayed in the metrics can be subsequently filtered at any time using the keywords set in TestBench.
Testing Intelligence: New metric on quality progress
Testing Intelligence has a new metric that represents the progression of the quality of a system. This is done by relating the test results of the requirements to the number of open errors.
Over time, it is easy to see how the coverage of requirements with tests and the number of errors evolves over time and whether a test end can be reached soon.
Your contact person at imbus
Mr. Dierk Engelhardt
mail: testbench@imbus.de
phone: +49 9131 / 7518-0
fax: +49 9131 / 7518-50