|Test execution duration now shown for each node in Test Result View||
The amount of time taken to execute each Test Step, Test Case and Test Suite is now shown in milliseconds in the Test Result View. You can use this information to see whether parts of your test are taking longer than you expect them to. The HTML and XML reports generated or exported for the test results also show the durations. You can turn off the decoration in the preferences.
|Parameter values now shown for each node in Test Result View||
The parameter values entered or used at a specific level in your test (Test Step, Test Case) are now shown in the Test Result View. You can use this information to which data were used for your Test Cases, without having to expand the test result tree to the lowest levels. This is especially useful if you have a Test Case that runs multiple times with different data sets. You can turn off the decoration in the preferences.
|Missing data decoration shown in Test Case and Test Suite Editors||
When working on a Test Case or a Test Suite in an editor, you can now see a small red cross directly in the editor when test data that can be entered in this editor are missing for a node.
|Functions can be entered as parameter values||
Alongside concrete values ("abc"), referenced data (=VAL1) and
variables ($VAR), you can now also enter functions as test data.
Functions are introduced using the question mark (?) followed
by the function name and its arguments.
|Categories are now supported in the Test Suite Browser and Central Test Data Editor||
To make project organization easier, you can now use categories in the Test Suite Browser and Central Test Data Editor.
|Teststyle framework and some guidelines now available in Jubula||
The project properties contain a new page for Teststyle rules. Teststyle gives guidelines on project structure and design. This framework was previously a part of GUIdancer and has been migrated to Jubula. Jubula contains a subset of the Teststyle rules that are available in GUIdancer.
|Analysis framework and sample metrics added||
Jubula now contains a framework for test analysis. A small set of sample metrics are available that can be performed on projects.
|"Save as new Test Case"||
There is a new option in the Test Case Editor and
Test Suite Editor to save selected items as a new Test Case.
The selected nodes are added to a new Test Case whose name you
define. The nodes are not copied, but their references are: the
effect is the same as if you had manually created a new Test Case
and added the Test Cases to it.
|New action: Store Property Value||
The abstract toolkit contains a new action on the
Graphics Component component to store the value of a
property. The action works in a similar way to Check Property,
except that the expected value is not provided. Instead, the value is written
to the variable name you define. You can then use this value later on in the test.
|New extensible adapter mechanism for Swing components||
You can now add support for renderers for Swing components that do not use the getText() method. An example of the adapter mechanism can be found here.
|Completeness check shown as progress window||
After saving in the ITE, the completeness check for a project is now shown as a progress window. This results from performance improvements made to the completeness check.
Eclipse Marketplace Client now accessible
You can now open the Eclipse Marketplace Client from the help menu in the Jubula Standalone.
|Changes to layout for properties view for Test Results||
The properties view for Test Results now shows test data in two columns to improve the readability of the information.
|Selenium update (Jubula standalone)||
The version of Selenium used for HTML testing in the Jubula standalone has been updated to 2.12.0. IE9 and FF 10 are now a part of our regression tests.
|GD_AUT_STARTUP_DELAY renamed to TEST_AUT_STARTUP_DELAY||
The variable for waiting between starting an AUT and checking that it is there has been renamed.