|Embedded AUT Agent||
If you are starting your AUT and running your tests on your local machine, you can now connect to an embedded AUT Agent directly from the ITE. This saves you having to start an Agent on localhost. This is also useful for testers working with Jubula as a feature in an Eclipse installation. The embedded AUT Agent is started on port 60000 by default; this number can be changed in the preferences.
|AUT Agent now part of the Jubula feature||
There is now no need to use the AUT Agent from the standalone version of Jubula to be able to work with Jubula as a feature: The AUT Agent is now included in the distribution.
|Launch configurations for Swing and RCP AUT's||
When working with the Jubula feature, you can now start your AUT from within the IDE as a launch configuration. This is available for Swing and RCP AUT's.
|Object Mapping Editor: Cleanup unused component names||
In the Object Mapping Editor, there is a new option in the context-sensitive menu. Via Cleanup -> unused component names you can start a search for any component names that are no longer used in Test Suites for this AUT. Once the search is finished, you can delete all of these unused names from the Object Mapping Editor. If they are then no longer used in the entire Project, they can be deleted from the Component Names Browser.
|HTML Test Result Reports can be expanded again||
Following changes made for the initial contribution, the HTML Test Result Reports could not be viewed properly in the previous version. In this release, the nodes in the HTML reports can be expanded and collapsed to view the whole test progress.
|State of component recognition displayed when collecting technical names||
When a component (technical name) is collected from an AUT, it receives a colored dot corresponding to the accuracy of the object recognition for this component at the time of collecting. A green dot signifies that the component could be found with an exact match, and was the only component above the threshold. A yellow dot means that the component is an exact match, but that multiple other components were also above the threshold. A red dot means that this component cannot be relocated in the current state of the application.
|Migration wizard re-enabled||
When migrating between the Indigo release and SR1, the migration assistant will automatically notify you that your database scheme is out-of-date. You can then select which Projects to import (these must have been exported from the database prior to migrating!).The assistant will drop the tables in the database, recreate the necessary tables and import the Projects you specified.
|Refactor: Replace with Test Case||
In the Test Case Editor and Test Suite Editor, there is a new option to replace one or more selected Test Cases with another Test Case from the library. A new wizard takes you step-by-step through the replacement process, letting you transfer component names and add further information for the new Test Case. This feature should help testers who want to restructure their tests after creating a reusable module to replace one or more Test Cases.
|Copy ID to clipboard also for Test Suites||
The ability to copy a unique ID to the clipboard to reference a Jubula element in external systems has also been implemented for Test Suites. You can now copy the ID of a Test Case or a Test Suite to the clipboard, and also open an element based on its ID in the clipboard using Shift+F9.
|The DBTool is more verbose||
The command line tool to import, export and delete Projects in the database, the DBTool, has been updated so that it is more verbose.
The ITE now uses the progress view to show longer-running activities such as test execution, connecting to AUTs etc.
|Edit Parameters Dialog in Central Test Data Editor can be opened via double-click||
In the Central Test Data Editor, it is no longer necessary to open the Edit Parameters Dialog via context-menu, as it can now also be opened via double-click on the data set you wish to edit.
|Mac keyboards now supported, new mechanism for adding keyboard layout files||
In the AUT configuration dialog for SWT and RCP AUTs, the Keyboard Layout combo box now only offers layouts that have been defined for Jubula. German (DE) and English (US) are defined as standard. As well as being able to add keyboard layouts for other keyboards, you can also define platform-specific keyboard layouts (e.g. for Mac) The documentation has been updated to describe the new mechanism for adding keyboard layouts.
Read the release notes (available from the documentation page) for more details, including known issues and other important information.
Back to the top