# Release Notes

# Introduction

This document presents the relevant differences between versions and updates, and provides an account of any developments or known issues with the current release.

For up-to-date information on a release, it is worth looking in the FAQ's on the website.

The release notes are presented in chronological order, with the most recent at the beginning of the document.

# Important advice for migrating to new versions

Existing users who wish to update to a new version should follow the steps described online to ensure a problem-free migration:
http://testing.bredex.de/migration-information.html

# Release Notes for version 8.7.0

## New Features and Developments

Changes in Check Text with Cell spec

- The table action check text with cell spec is now searching further. This means if the first value found is not matching but there is another row,column combination with the specified value, this will also be checked. This is only for the rows. We still do not support duplicated Table Header names.

Embedded AUTAgent for API

- It is now possible to start an AUTAgent within the API. Therefore you do not need any Jubula installation to run a test. For more information see the developer manual.

Getting ComponentIdentifier from AUTAgent

- The component name and the encoded ComponentIdentifier can be easily get from and external or the embedded API AUTAgent. It is possible to start an simple Component collecting mode via the context menu on the AUTAgent. This is only possible if no ITE/testexec/API is connected to the agent. For more information see the developer manual.

## Known issues and other information

Java 9 and later

- Java 9 and later applications must be started with the jvm arguments '--add-opens=javafx.controls/javafx.scene.control.skin=ALL-UNNAMED-illegal-access=permit'. This is necessary because we are using internal information to get e.g. some position information of components.

Object Mapping(OM) via AUTAgent

- There is a problem that extensions are not loaded if using the OM via the AUTAgent context menu. If you are using the embedded agent for API you can register new Testerclasses to the ToolkitInformation and than start the Embedded agent.

# Release Notes for version 8.6.0

## New Features and Developments

Value sets for parameter

- The data for new data set rows can now restricted to specific values. Also it is possible to set a default value, so that new data sets begin with this value. This is possible in the Edit Parameters dialog.

Possibility to reduce the amount of component name proposals

- You can now reduce the amount of proposed component names. This can be done by setting Object Mapping Categories in Specification Test Cases. The association can be done with a dialog which opens when you open the context menu on a specification of a test case and use Edit OM association.

New Teststyle to gather TODO's in the problems view

- The Teststyle searches for a specific text (default `#TODO`) in names of nodes e.g. Test Cases. It can be adjusted to search for other text, in specific context, cases sensitive or also in inactive Nodes. See the documentation for more information.

UI improvements

- After refreshing the project the Test Case Browser and the Test Suite Browser have the same expanded state as before.

- The horizontal divider in the Object Mapping Editor is now remembered after closing the editor or the application. This setting is saved in the workspace.

Removed support to import xml files

Jubula API

- The class MakeR has now the method `createCIWithName` which is creating a Component Identifier with just a given name(ID).

Search where Central Test Data is referenced

- We added the possibility to search for places where a given cell in a Central Test Data is referenced through the ?getCentralTestDataValue function. The results are classified as being exact (when the exact cell is referenced) and approximate (when the column of the cell is referenced). Please note that only the literal references are found (e.g. those which do not use parameters, variables or other function calls).

Try AUT from the AUT Config Dialog

- It is now possible to check if an AUT is startable directly from the AUT Config Dialog. You can use the `Try AUT` button for this. When clicked, the ITE tries to start the AUT (if the ITE is already connected to an AUT Agent, that is used, otherwise the embedded Agent is started). In case of a successful AUT start, the AUT is kept running, otherwise the user is notified of the reasons why starting the AUT failed.

Go To Previous / Next (Edited) Editor

- We added a new navigation feature. Jubula now maintains a history of visited Editors, and it is possible to navigate between these, or only those which have been edited.

SWT Tree Table actions

- SWT Tree Tables support the following table-like actions from now on:

  - Check Editability (Specify Cell)

  - Check Existence of a Column

  - Check Existence of Value in Column

  - Check Existence of Value in Row

  - Check Text (Specify Cell)

  - Check Text (Mouse Position)

  - Select Cell

  - Select Value from Column

  - Select Value from Row

  - Store Value (Specify Cell)

  - Store Value at Mouse Position

- We also corrected the `Check Property at Mouse Position` and `Check Text (Mouse Position)` actions.

New CAP which can save data into the testresult summary

- We added the possibility to add Information the the testresult summary. A new Action (`Store value in Testresult Summary (ub_app_storeValueInSummary)`) is introduced which saves Strings into the Additional Information section of the testresult summary.

Improving the Save As New / Extract Test Case operations

- We added the possibility to choose the Category where the new Test Case should be added for these operations.

JavaFX - java 9 support

- JavaFX should now be working with java 9

## Known issues and other information

There are no known issues or additional information for this version.

# Release Notes for version 8.5.0

## New Features and Developments

Moving tree table actions to the concrete toolkit

- We have moved the JavaFX and SWT tree table actions to the concrete toolkit. As a consequence, the relevant modules in the unbound_modules_javafx and unbound_modules_swt projects have been deprecated. Please replace these modules by their counterparts from the project unbound_modules_concrete. Also note that some of the tree table actions are still only implemented for the JavaFX toolkit (e.g. Check Existence of Value in Column). These actions now result in an Action not supported by selected toolkit error if executed on SWT Tree Tables.

Upgrading Selenium to 3.3.1

- We have upgraded the used Selenium Webdriver version to 3.3.1. As a consequence, the browser webdrivers may also need upgrading. The new Selenium version has been tested using ChromeDriver version 2.28, GeckoDriver (Firefox) version 0.15 and IEDriver version 3.3.0.

Export JUnit reports

- When generating TestResult XML/HTML files from Test Results, the generated files will now include an additional lightweight JUnit report. You can now define referenced Test Cases as TestSuites for the generation of the JUnit report with a newly added parameter called "JUnitTestSuite".

Deletion with Orphans

- We introduced a new feature in the Test Case Browser called Delete with Orphans.

- When tidying up a project, there are Test Cases that are no longer required or used. The Delete with Orphans feature allows you to show all Test Cases that would remain unused if a certain Test Case were deleted. It then offers you to delete the Test Case with all its remaining "Orphans".

Import project files by drag and drop

- It is now possible to import .jub project files by dragging them to the Test Suite Browser View of the ITE. If only one project is imported this way, it is automatically opened. Please note that this feature is not supported on some Linux distributions.

Highlight components at which an error occures

- It is now possible to highlight the component at which an error occured in the screenshot, that is being taken when an error occurs. This will only happen if the corresponding checkbox in the expert section of the AUT configuration window is selected.

Improved Replace Test Case References operation

- It is now possible to choose default values for unmatched parameters in the Replace Test Case Reference operation (the non-Editor version). These default values can not contain references, but all other types are usable (e.g. variables and functions).

Added the possibility to use a static IP Address and port for the AUT - Client connection.

- This is possible by setting the JVM properties jubClientAddr and jubClientPort in either the jubula.ini or the testexec.vmoptions configuration files. You can also use command-line arguments to achieve the same (e.g. by something like `testexec.exe -jubClientPort 11111`).

Double clicking on Test Case Editor root nodes

- To help navigating between Editors, we added a new feature: when double-clicking a Test Case Editor's root node, if there is a single Editor open which references the given Test Case, that Editor is activated. If there are more than one such Editors open, you can choose one to activate in a dialog. And if there is no such Editor open, you can choose a Test Case or Test Suite which references the Test Case, and open its Editor.

Added the possibility to jump to a referenced data set from the Properties View.

- It is now possible to try to jump to a data set which is referenced by a parameter through the getCentralTestDataSetValue function. In case the row and cell are identifiable from the arguments of the function then they are also selected in the Data Sets View.

- We improved the Check / Store Property actions for HTML AUTs using a Webdriver. It is now possible to access any (specifically, CSS) attributes and properties of HTML elements. To access a CSS property, simply use its name (e.g. `background-color`). Please note that the actual value returned is strongly browser-dependent.

- The background of browsers now change their color when filtering is active. We introduced this to remind you about the active filtering so you don't get confused about not finding elements that are currently hidden by the filter.

Update site for the RCP Accessor

- We added a P2 update site for the RCP Accessor to the file <installation-directory>/development/rcp-accessor-repo.zip. You can use this site in the Help--> Install new software... menu of an RCP AUT to add the RCP Accessor. Of course this option is only available if your AUT provides this feature.

New navigation feature in HTML reports

- Similarly to the ITE, it is now possible to navigate between errors in an HTML report. The navigation always starts from the active (currently selected) node of the result tree. This active node is distinguished by a lightgray background.

Update in the Jubula API

- ActionHandlers are now returning Result objects so the return value can be extracted. This is useful for actions like readValue which e.g. has the text of a component as return value.

- Two new actions have been added to the Jubula API. getProperty can now be used to get a property of a component and isSelected can be used to check whether a checkbox or a toggle button is selected.

## Known issues and other information

Known Issues with Java 9

- Starting AUTs will not work without --permit-illegal-acces set for the java virtual machine. Sometimes also --add-modules=ALL-SYSTEM is necessary.

- JavaFx testing ComboBox, Slider, TableView and TreeTableViews will not work.

# Release Notes for version 8.4.1

| Databases created with Version 8.4.0 can be used, there are no migration steps necessary

## Known issues and other information

Following Bugs are resolved

- Bug 508977 A New Function is available which allows the user to convert a numerical number with a decimal point to an integer and the other way around.

- Bug 494756 Return value of function ignored for click actions, resolved by Bug 508977.

- Bug 509847 The order of the loops and conditions in a Test Case is now shown correct in the Test Suite Browser and the Test Case Browser.

- Bug 509910 A Bug fix for the use of technical and logical Component Names.

- Bug 509909 All unused Component Names will be now deleted in the Object Mapping Editor.

- Bug 509911 A correct error message is now shown in case of user want to do operations like: replace all, save as new, etc when an object was locked or deleted.

- Bug 509851 It is now possible to add a description to a repeat module.

- Bug 509959 User has now the possibility to drag and drop conditions in the Test Suite Editor.

- Bug 509852 Visual Representation for negated conditions in the ITE.

- Bug 509969 Condition nodes in a Test Suite can now be exported.

- Bug 510020 HTML TestResult Reports does now contain all conditions and loops.

- Bug 509849 Visualization of Negations of Conditions in the Testresult and -execution view and XML and HTML Reports.

# Release Notes for version 8.4.0

## New Features and Developments

Conditional Statements and Loops

- We introduced new nodes altering the test execution flow: Conditional Statements and Loops.

- The If-Then-Else-node allows you to specify one or more test cases or test steps as a condition. Based upon the result of the condition nodes, either the "then" or the "else" branch will be entered and the containing nodes will be executed. The condition can also be negated.

- The While-Do-node and the Do-While-Node will both repeat the test nodes inside the "do"-branch until the condition is no longer being met. In contrary to the While-Do-node, the Do-While-node checks the condition after each run through the "do"-branch. Therefore the Do-While-node will always run at least once.

- The Repeat-node repeats the nodes inside the "do"-branch for a specified amount of times.

Invoke External Methods

- It is now possible to invoke external (AUT - independent) methods through the Reflection component. The external JAR files must be placed in the directory <installation-directory>/ite/externaljars.

Component Names

- Component name types are calculated and treated differently from this release onwards. The type becomes only decorative, so actions resulting in invalid component name types are allowed from now on, however, the user is warned before any action resulting in an invalid type. Component names with invalid type are decorated by error markers, just like component names which are mapped into a component which does not realize one of the actions which might be executed on the component name.

- A new feature is added to the Component Name Browser: it is now possible to display the usage counter for component names. This shows the number of places in the current project where the component name is used. Users can turn this feature on and off in the Test - Editors preference window.

Check actions with timeout parameter

- Most of the check actions do now have a timeout parameter. If there is a timeout value greater than 0 the check action is checking multiple times if the wanted status has occurred. If this did not happen until the timeout is reached the check is marked as check failed.

Skipping test steps

- Test steps can now be skipped by changing the value of at least one parameter of a test step to '##jbskip##'.

## Known issues and other information

JaCoCo version updated

- JaCoCo has been updated from version 0.7.3 to 0.7.7. More information about changes in JaCoCo are available at http://www.eclemma.org/jacoco/trunk/doc/changes.html.

- Some databases which limit the row size (like MySQL) have problems with Jubula if they are set to use multi-byte encodings like UTF8. Try to use single-byte encodings like latin1 if you encounter any problems.

# Release Notes for version 8.3.0

## New Features and Developments

Since M3

Support for javafx.stage.Popup

- The JavaFX toolkit now allows mapping in Popups.

Support for javafx.scene.shape.Shape

- Jubula now supports Shapes (e.g. Circles or Rectangles) in the JavaFX toolkit on a graphics component level.

An automatic screenshot is taken after timeouts.

- When connection to the AUT is lost during test execution, and the Automatic Screenshots preference is ON, the AUT Agent attempts to take a final screenshot, which is then saved to the Database.

Possibility to get text values from a componentin the API

- From now on it is possible to get a text value of a Component (like Label, TextInputComponent, etc) in the API.

Wizard for creating an extension

- We have created a wizard for eclipse which makes it easier to write a extension for not supported components. See the developer manual for more information.

A list of changes which happened in the API since version 8.2.0 is located here.

Since M2

Simple Extensions

- Jubula now provides a simple way to add support for an unsupported component via the new 'Simple Extension' option.

- You don't have to use the complex way of creating and installing an extension anymore if you want to support a component on a graphics component level, e.g. if you only want to execute a click on that component.

- Now, you only need to add "SimpleExtensions" as a key to the property map of an AUT and a comma-separated list of fully qualified classnames as the value.

- For more information take a look at the "Extensibility" chapter in the user manual.

Selenium version updated

- The version of Selenium used by Jubula to execute HTML tests has been updated to version 2.53.0.

Added support for Slider components to all Java toolkits

- It is now possible to create tests for Sliders in JavaFX, Swing and RCP/SWT.

Added move action for Tree Tables in JavaFX

- It is now possible to move in a Tree Table similar to moving in Tables.

Added move action for Tree Tables in JavaFX

- It is now possible to move in a Tree Table similar to moving in Tables.

New Action - check existence of column for Tables and Tree Tables

- A new action was added. It is now possible to check if a specific column exists, respectively does not exist, in a Table/Tree Table.

Since M1

New way to export and import projects

- We changed our xml-based project export mechanism to a custom way which uses the json format.

- The new files consume much less disc space and the export and import process runs faster now.

- Due to that we're about to discontinue the support for the old XML interchange format. Which is why exporting projects is now only possible with the new *.jub interchange format.

  We will however support the importing of the old XML format for a couple of versions.

You can use Selenium Webdriver for HTML tests

- We added the possibility to use Selenium Webdriver for test execution in the HTML toolkit in an experimental mode.

- You can try it out for Firefox and Chrome. If you choose Chrome you will have to download the driver explicitly. Testing with the Internet Explorer does not yet work at this point in time.

Removal of Dashboard

- In the course of some cleanup efforts the dashboard was removed from Jubula.

- If you connected your tests to an ALM system, the link to the results opens them in a Jubula instance now, instead of the dashboard.

New features in Jacoco monitoring agent

- Now you are able to add multiple source directories in Jacoco code coverage. The added source directories can be edited and removed.

- Optional configuration to allow class file id collision in code coverage.

- You can enter multiple regexes to for inclusion. For more information see user manual.

- Optional configuration to allow class file id collision in code coverage.

- You can add multiple directories and jar files in installation path.

New features in report generation

- It is now possible to automatically generate a monitoring report.

Timeout to connect to AUT now configurable

- You can now configure the timeout for connecting to an AUT as a property for the AUT, so that performance problems in your environment won't prevent connecting to your AUT.

Empty parameters allowed

- Now you can leave parameter fields in test steps empty. This might be helpful, if you use for example the invoke method action and don't need a certain parameter.

New way to check component appearance and disappearance.

- We approved the check component existence with a timeout property. With this value you can set a time limit, while the test execution will wait for the component appearing or disappearing. For more information check the Reference Manual.

Check the text/properties of customized cells in JavaFX

- It is now possible to check the text of customized cells in JavaFX. In this case customized means that there are child components within the cell that are used to display the text of the cell. In this case the old mechanism to get the text of a cell would not be able to retrieve the displayed text. With the new approach we are checking for every child component of the cell if there exists an adapter which can retrieve the text. This also applies for check property at mouse position. First of all it is checked if the cell contains the wanted property, if this is not the case we are checking all child components which are under the mouse. Because both mechanisms try to find a fitting adapter for the child components, you can easily add support for a custom component that you created. You just have to create an extension containing the adapter for your component.

Two new actions to execute external commands

- We introduced a new CAP for executing external commands:

  - Execute External Command

- Among other things it is now possible to specify a parameter split character, the encoding type and to specify the directory and the executable file separately.

## Known issues and other information

Since M3

jb_null can be used to invoke a method with a null "value"

- There is now the possibility to use the string jb_null as a method argument for the invoke method action. This string will then be converted to a null when calling the method.

Since M2

Removal of iOS toolkit support

- We removed the support for iOS toolkit. It is no longer possible to create projects and start AUTs using these two toolkits.

Since M1

'jubula' and 'server' directories merged in installation

- Instead of having two separate directories in the installation folder for the ITE tools (Jubula, testexec, dbtool) and the AUT Agent tools (AUT Agent, autrun), there is now only one folder, 'ite'.

- You will need to adapt your continuous integration scripts to reflect this change.

Removal of Atlassian connectors

- We removed the Atlassian connector since it is deprecated. If you want to connect Jubula to another ALM besides to Bugzilla and Trac you will have to use the commercially available Tasktop Dev connectors.

- There is currently a known issue that reporting Jira as ALM fails for task IDs which include a '-'. https://bugzilla.bredex.de/1769

# Release Notes for version 8.2.2

## New Features and Developments

XLSX support in using excel spreadsheets.

- Now you can import test data from xlsx excel files. Localization is removed, only the first sheet will be used.

Set heuristic profiles for individual components

- You can set specific profiles for the object recognition for individual components. This might be useful for components which can't be found with the standard profile.

## Known issues and other information

Removal of multi language support

- We removed the support for multi-lingual testing, i.e. it is not possible anymore to specify test data in different languages in one project. The according GUI items and command line tools parameters have been removed. When importing a project which contains multi-lingual test data the default language is the one that will be kept. The command line tools will also use the default language. AUTs can still be started in different languages using the according AUT arguments.

Removal of .NET and Winapps toolkit support

- We removed the support for .NET and Winapps toolkits. It is no longer possible to create projects and start AUTs using these two toolkits.

Removal of external Chronon support

- We removed the external support for the Chronon monitoring agent.

Removal of mobile toolkit

- We removed the mobile toolkit support. Projects using this toolkit will be automatically converted to iOS toolkit.

# Release Notes for version 8.2.1

## New Features and Developments

Jubula runs now on Java 8

- We updated the bundled JRE which is included in every Jubula installation to Java 1.8.0_66.

ITE performance improvements

- Completeness check operations within the ITE, that are supposed to ensure the projects executable consistency, are now performed in the background and do no longer cause the UI from being blocked.

New view for logs from execute external command

- A new view is introduced which can show the logs from the execute external command action. When selecting such an action in a testresult the log will be shown. Use Window-->Show View-->Other to open the Log View.

New way to add comments

- In the test case, test suite and test job editors it is now possible to add a new kind of comment as a node to your test via alt+c. These comments are only visible in the editors and can help you structuring your tests.

New way to delete test result summaries/details with dbtool

- The dbtool can now delete test result summaries/details. It can be used to delete test results for a specific project/version or all projects. You can define an amount of days to remove test result summaries/details that are older than a specific date. For more information see user manual.

- It is now possible to copy and paste Test Cases and Test Suites in Test Case Editors, Test Suite Editors and Test Job Editors. To do so you have to select the according items and select "Copy" from the context menu or press CTRL+C, switch to the editor in which you want to paste these items and select "Paste" from the context menu or press CTRL+V. The copied items will be pasted in the exact same order as the originals. Test Data and component names will be adopted accordingly.

## Known issues and other information

Metrics support within the ITE removed

- The functionality for project metrics has been removed from the ITE and will no longer be supported.

# Release Notes for version 8.2.0

## New Features and Developments

New actions for the RCP toolkit(GEF)

- You can now check the status of a connection point (anchor) on a block.

- You can now check properties of ConnectionEditParts.

- Now the GEF Inspector additionally gives information about the properties of an inspected figure or connection.

A list of changes which happened in the API since version 8.1 is located here.

## Known issues and other information

There are no known issues or additional information for this version.

# Release Notes for version 8.1.9

## New Features and Developments

New actions for the RCP toolkit(GEF)

- You can now check the existence of connections in GEF Figure canvas using the unbound module ub_fcv_checkExistenceOfConnection_byTextpaths from unbound_modules_rcp

- You can now check the Anchor count of an edit part in GEF Figure canvas using the unbound module ub_fcv_checkAnchorCountOfEditPart_byTextpath from unbound_modules_rcp. This action can only be used if you are using a custom extension implementing the identifier for edit parts. See the developer manual for more information.

New actions for Tree Tables in the JavaFX toolkit

- You can now check the editability of a cell at the current mouse position using the unbound module ub_trt_checkEditabilityAtMousePosition from unbound_modules_javafx.

- You can now check the editability of a cell which is currently selected using the unbound module ub_trt_checkEditabilityOfSelectedCell from unbound_modules_javafx.

- You can now check the text of a cell at the current mouse position using the unbound module ub_trt_checkTextAtMousePosition from unbound_modules_javafx.

- You can now store the text of a cell at the current mouse position using the unbound module ub_trt_storeValueAtMousePosition from unbound_modules_javafx.

- You can now store any property value of a cell at the current mouse position using the unbound module ub_trt_storePropertyAtMousePosition from unbound_modules_javafx.

## Known issues and other information

There are no known issues or additional information for this version.

# Release Notes for version 8.1.8

## New Features and Developments

Additional option for Object Mapping in the JavaFX toolkit

- There is a new key combination in object mapping mode. With that it is now possible to map the current component at mouse position and all its supported parents from the AUT's hierarchy.

New actions for the SWT toolkit

- You can now check the property of tree table items using the unbound module ub_trt_checkPropertyAtMousePosition from unbound_modules_swt.

- The unbound modules ub_tbl_checkPropertyAtMousePosition and ub_tre_checkPropertyAtMousePosition from unbound_modules_concrete are now also implemented for the SWT toolkit.

## Known issues and other information

There are no known issues or additional information for this version.

# Release Notes for version 8.1.7

## New Features and Developments

Lots of new actions for the JavaFX toolkit

- You can now check the property of list items using the unbound module ub_lst_checkPropertyAtMousePosition from unbound_modules_concrete.

- You can now check the property of table items using the unbound module ub_tbl_checkPropertyAtMousePosition from unbound_modules_concrete.

- You can now check the property of tree items using the unbound module ub_tre_checkPropertyAtMousePosition from unbound_modules_concrete.

- You can now check the property of tree table items using the unbound module ub_trt_checkPropertyAtMousePosition from unbound_modules_javafx.

- Furthermore, there are several new check and select actions for tree tables in the JavaFX toolkit which emphasize the table aspect of that component. It is now possible to select/check tree table items by providing the name of the column or the path of nested columns. Please refer to the reference manual for a detailed description. The unbound modules that used integers to address columns are now deprecated.

Selenium version updated

- The version of Selenium used by Jubula to execute HTML tests has been updated to version 2.46.0.

New example

- We added an example for our Client API using JavaFX. It is located in org.eclipse.jubula.examples.api.adder.javafx.jar.

## Known issues and other information

There are no known issues or additional information for this version.

# Release Notes for version 8.1.6

## New Features and Developments

It is now possible to change the order of data sets in the Data Sets View.

It is now possible to change the order of single data sets in the Data Sets View. You can now move single data sets up and down in the Data Sets View

GEF figure canvas are addressable via API CAPs

GEF figure canvas can now be addressed by using the Jubula client API.

Performance for opening Test Result Details in the Reporting Perspective has been improved

The performance for opening Test Result Details in the Reporting Perspective has been drastically improved. Currently it is not possible to use the functions Open Specification and Show Specification due to these changes.

## Known issues and other information

Currently it is not possible to use the functions Open Specification and Show Specification when working with Test Result Details in the Reporting Perspective and in the Execution Perspective.

# Release Notes for version 8.1.5

## New Features and Developments

New action for checking the text of tooltips

- You can now check the text of tooltips using the unbound module ub_ttc_checkTooltipText.

Support for DatePickers in JavaFX

- DatePickers in the JavaFX toolkit can now be addressed as components with text input. You can also execute tests which address graphics components (ub_grc) on DatePickers.

Take screenshot on error now supported in the Java API

- Take screenshot on error is now supported when using the Java API.

- Reporting to ALM is now performed by having n transactions for n test results / field updates.

## Known issues and other information

- http://eclip.se/467071 : The fix for this issue might require a re-mapping of (many) UI components for your JavaFX AUT within the Object Mapping Editor. This is necessary as the quality of the (already existing) object mapping information might not be sufficient enough to either find the UI component again (leading to a component not found error during test execution) or to find another one as being more likely (likely leading to odd action errors). Please keep this in mind if you experience problems after switching to this version.

# Release Notes for version 8.1.4

## New Features and Developments

Sister release to Eclipse Mars

- This version is the "sister" release to the Eclipse Mars release. It was produced in the same sprint as the branch for the Mars release.

# Release Notes for version 8.1.3

## New Features and Developments

New options for exporting object maps for the API

- You can now export single names, or categories of names from the Object Mapping Editor for use in the API.

Documentation for the converter

- The developer manual now contains some information on using the converter to convert an ITE project to an API project.

RCP tests now executed on Eclipse 4.4

- We now execute our tests for RCP 4.x branches on version 4.4 of Eclipse.

# Release Notes for version 8.1.2

## New Features and Developments

New actions for HTML to handle alerts, prompts and confirmations

- You can now handle alert, prompt and confirmation dialogs in HTML AUTs.

- You can use the actions: interact (to accept or dismiss the item), input text, check existence and check text.

- Alerts, prompts and confirmations are not shown during test execution, but they must still be handled in the test. You must use the actions to deal with the prompt, alert or confirmation just before the item appears. The actions are designed to deal with the next prompt, alert or confirmation that appears and not while it is already open.

Progress in JavaFX toolkit

- JavaFX AUTs can now be started via autrun.

- Code coverage reports are now supported for JavaFX AUTs as well.

- Support for drag and drop actions on lists.

- Support for actions on check boxes in tables which are not located in the first column. It is not assumed anymore, that a check box can only occur in a first column of a table - contrary to the other toolkits.

## Known issues and other information

The name GUIdancer has been retired

- We no longer build the product with the name GUIdancer. Since Jubula and GUIdancer have been functionally identical in the standalone versions since 2013, this simply avoids confusion by only having one name.

- Any scripts in your test execution that use the string GUIdancer should be changed once you update to a new Jubula release.

Reduction in test focus

- In order to focus our development efforts, we are no longer executing tests on .NET applications or on Mac systems (with the exception of iOS tests).

# Release Notes for version 8.1.1

## New Features and Developments

Background and border properties set by CSS are checkable in JavaFX AUTs

- In JavaFX AUTs, you can use the action "check property" to check properties set via CSS.

- We have implemented the ability to check complex properties for background and border.

- You can add support for other complex properties using an adapter.

New actions for the HTML toolkit

- There are new actions in the HTML toolkit to interact with an AUT based on a locator.

- There are five new actions that use locators instead of a component name for object mapping:

  - Click: this action clicks once with the left mouse button on the item specified in the locator.

  - Wait: this action waits for the item specified in the locator.

  - Check text: this action checks the text of the item specified in the locator.

  - Check CSS Path Count: this action checks whether the amount of items matching a CSS locator is a value you specify.

  - Check XPath Count: this action checks whether the amount of items matching an XPath locator is a value you specify.

Version information more clearly presented

- You can now see version information in the splash screen, in the AUT Agent tray icon and using the -h parameter for the command line tools.

# Release Notes for version 8.1.00294

## New Features and Developments

API for Java-based UI test automation

- We've created a whole new layer in the ITE that allows you to write functional UI tests via an official Java client API. Detailed information of the architecture and how to start can be found in the Developer Manual.

New option for reporting to ALM systems: update fields

- You can now specify in the Project properties that you want to update fields on tasks in ALM repositories after a test has run.

- This allows you to automatically change e.g. the status of tasks based on test results.

- There is a property inspector to let you see what properties a specific task has.

-datadir and -resultdir parameters are now optional for testexec

- The parameters to enter a result directory (where HTML and XML reports are created) and to enter the place where any external data files reside are now optional in the testexec.

- This reduces the amount of parameters you have to enter for a simple configuration.

New optional parameter for testexec -resultname

- You can now specify a name for the HTML and XML files that testexec can produce using the parameter -resultname.

- If you do not use this parameter, then a default name consisting of the Test Suite name will be used.

Improved no-run option in testexec

- The no-run option in the testexec now has a number of parameters so that you can define how far the test should be checked.

- You can use this option to perform all steps up to the actual test execution to ensure that e.g. AUTs can be started, object mapping is complete etc.

Composite components in JavaFX can now be mapped

- It is now easier / possible to map composite components such as accordeons and choice boxes in JavaFX AUTs.

Transformed components in JavaFX can now be tested

- You can now test components in JavaFX that have been transformed, e.g. via scaling, clipping, translation, rotation and shearing.

Support for menu buttons in JavaFX

- You can now map menu buttons in JavaFX AUTs as Graphics Components. You can select from the menu on such buttons using the actions to select from context menus, using the mouse button "1" (left button).

Support for derived components in JavaFX

- You can now test components in JavaFX AUTs that are derived from currently supported JavaFX components.

Support for nested columns in tables in JavaFX

- You can now test tables in JavaFX that have nested columns (i.e. where one column contains multiple child columns).

- Enter the path to the column you require using a forward slash as a path separator, e.g. Address/Street.

- You can address the columns using indexpath and textpath.

Description View in the ITE

- You can now enter descriptions for nodes (Test Cases, Test Suites, Test Jobs) in your tests. The descriptions are entered using a markup language, that you can select in the Project Properties.

- Once you have entered descriptions, you can see them via the Description View when you select a node with a description.

Default columns changed in the Test Result Summary View

- The columns that are shown by default in a new workspace for the Test Result Summary View have been reduced.

- You can still add other columns to the view using the context menu in the view.

- There is also a new button in the top right hand corner of the view to reset the standard column width.

- There is a new column for the version number of the Project.

New actions in the iOS toolkit

- The action input text is now available for iOS. You can use this action to enter text to a component that currently has focus.

- The action click in component is now available for iOS.

- The action take screenshot is now available for iOS. It takes a screenshot of the App screen.

- There is a new action just for iOS check badge value. Use this action to check the text on a badge based on the index of that badge within a tab bar.

Dashboard as a deployable web application

- You can now use the testresults.war found in the dashboard/webapp folder to deploy the dashboard into your own server.

- The URL for the standalone and deployable dashboard has changed to unify it. You must update any links to the dashboard to use this new URL.

      		http://HOSTNAME:SERVERPORT/testresults/dashboard

New searching options

- In the Search Dialog, you can now search for nodes in the Project based on their name, their comment and/or their Task ID.

Mouse position now shown on screenshots on error

- Automatic screenshots that are taken when an error occurs now show the mouse position.

- The mouse position is shown as a square inverted-color area, with the middle pixel being the position of the mouse pointer.

Version numbers now allow major, minor, micro numbers and qualifiers

- You can now create versions of Projects that use major, minor and micro numbers as well as qualifiers as their version number.

- Version numbers can consist of just a number, just a qualifier, or a number and a qualififier, e.g. 1.0_release, 1.0, 1.0.0, 1.0.0_release, version3

Support for Eclipse Mars AUTs

- You can now test AUTs that are based on the Eclipse Mars platform.

Testexec now includes completeness check for Test Jobs

- The testexec tool now checks whether a Test Job is complete before attempting to start test execution. If the Test Job contains one or more incomplete Test Suites, it will not start and an error message will be shown.

Testexec will start the first AUT in a Test Job

- When using Test Jobs, testexec will start the first AUT in the Test Job if this AUT is startable via an AUT configuration. You can continue to use autrun for all of your Test Suites in a Test Job if you prefer.

## Known issues and other information

We are "retiring" the name GUIdancer

- To reduce confusion when working with the standalone versions, we will be retiring the name GUIdancer in the coming releases.

  This reflects the situation that the Jubula and GUIdancer standalones have been functionally identical for over a year and only differ in their branding.

Support for Java 8 as a runtime environment

- We now run our regression tests for RCP and Swing AUTs on all platforms with Java 8 as a runtime environment.

Support for iOS 6 dropped

- We no longer support iOS 6 for testing. The iOS support is now for 7 applications.

Relevance now a property of Test Suites

- Whether or not a test run is relevant is now determined by a property on each Test Suite. This better reflects the situation that specific Test Suites will always be relevant and others never.

- The meaning of relevance has not changed. However, the entry from the preferences has been removed and the parameter for the testexec is no longer accepted.

- All Test Suites in newly imported Projects are automatically set to true for relevance.

- Newly created Test Suites are created as being relevant.

Dashboard URL has been changed

- The dashboard URL has been changed to:

            http://HOSTNAME:SERVERPORT/testresults/dashboard

Updated JRE in the Windows and Linux installers

- The Windows and Linux installers now use JRE 1.7.0_72. The ITE is executed with this version on Windows and Linux.

Tree view removed from object mapping editor

- We have removed the tree view from the object mapping editor and improved the layout of the split view and added a filter for assigned names to replace the functionality in the tree view.

Incompatible and recommended changes regarding custom toolkit extensions

- There has been a minor but incompatible change in the

      org.eclipse.jubula.toolkit.common.IToolkitProvider

  interface regarding the name of the interface itself (lower k instead of upper K) as well as a method renaming:

      public ResourceBundle getI18nResourceBundle();

  is now

      public ResourceBundle getResourceBundle();

  .

- With addressing http://eclip.se/454545 we've adjusted our recommended namespace for custom toolkit remote control extensions. Though this change is backwards compatible and using the old namespace for AdapterFactories, adapter and tester classes will still work we do strongly recommend to re-locate those custom written remote control classes. Use e.g. the org.eclipse.jubula.ext.* namespace to avoid collisions with signed classes of the ITE in the future.

- With the provisioning of an API for all toolkits we've altered the

      Bundle-SymbolicName

  of all of our toolkit provider. As this should not affect any custom written ITE toolkit extension (as no explicit bundle dependency to our bundles is necessary) you can easily adjust your bundle dependencies by replacing the old ID

      org.eclipse.jubula.toolkit.provider.<toolkitName>

  with the new one

      org.eclipse.jubula.toolkit.<toolkitName>.provider

  .

# Release Notes for Version 8.0.00170

## New Features and Developments

Support for JavaFX AUTs

- We have added support for testing JavaFX AUTs.

- There is an example Simple Adder AUT in the <installation-directory>/examples/AUTs folder. You can use this to perform example tests as described in the cheat sheets.

- You can see the overview of the support via http://eclip.se/421595.

- The toolkit is extensible, and we welcome feedback and contributions.

ALM integration: Support for commenting on HP ALM tasks after a test run

- You can now connect your ITE to a HP ALM repository (version 11+) to view tasks from the repository in the ITE.

- You can also add comments to tasks in a HP ALM repository when a test has run.

- To use the HP ALM integration, you must use a separate connector for HP ALM which may incur license costs. Visit the Tasktop website for more details http://www.tasktop.com.

ALM integration: Reporting to ALM systems after headless execution now supported

- When a test has run via testexec, you can now trigger the reporting to ALM tools manually from the Test Result Summary View.

- This allows you to add the test results from your continuous integration tests to your issues, bugs and features in your ALM system.

ALM integration: Amount of reported items shown

- When reporting to ALM systems takes place, you can now see how many tasks were reported to, how many results were written to each task, and a total amount of tasks written to in the console.

Support for embedded AUT Agent in testexec

- When executing tests via the command line using the testexec tool, you can now choose to use an embedded AUT Agent for the test.

- This means that you do not have to start a separate AUT Agent on the machine you are testing on.

- To use an embedded AUT Agent, don’t enter the -server parameter. You can either enter a port number for the embedded AUT Agent to be started on, or you can also leave out the -port parameter to start the AUT Agent on a dynamically chosen port.

Create New Version is now available in the dbtool

- You can now create new versions of a Project using the dbtool.

- Use -createVersion <project-name> <old-version> <new-version> to create a new version of an existing Project.

Change tracking in Projects

- You can now configure in the Project properties that changes to Test Cases, Test Suites and Test Jobs in the Project are tracked. You can configure a system / environment property that is shown alongside the timestamp of the change to track e.g. who made the changes.

- When change tracking is activated, when you save an editor for a Test Case, Test Suite or Test Job, the timestamp of the save as well as the property will be saved and displayed in the properties view.

- You can specify the amount of changes to track per node, or the length of time that change tracking information should be kept. Once the time has passed or the amount of changes has been reached, the next saving of the node will result in invalid change information being discarded.

- You can remove all change tracking information from the Project via the Project properties.

Support for iOS 7

- You can now also test AUTs written with iOS 7.

New information in Object Mapping Mode : property information

- When you collect a component in the Object Mapping Mode in a Swing or SWT/RCP AUT, you can now see information on the properties of that component in the Properties View.

- The information is shown as a list of properties with their values. If a value cannot be accessed, this is communicated.

- The information is not saved - to see the properties again, you must re-collect the component in the Object Mapping Mode.

- This can be used to help you write tests that use the actions check property or store property.

Component match heuristic shown for each component in test results

- In the HTML and XML test result reports, and in the result reports in the ITE, you can now see the value with which the component was found when the test was executed.

- This lets you see whether a component is ”easily” found, or whether a small change may lead to it no longer being found, so that a preventative remapping may be worthwhile.

Graphics component support for Canvas

- You can now map org.eclipse.ui.forms.widgets that inherit directly or indirectly from canvas.

- This includes, e.f. org.eclipse.ui.forms.widgets.Hyperlink.

- You can use actions such as click and check existence (and other actions on the graphics component level) on these components.

Show where used also available for Test Suites

- You can now use ”show where used” on Test Suites to find out which Test Jobs they have been reused in.

»F3« always opens selected item

- You can now press »F3« on any Test Case, Test Suite, or Test Job to open the specification of that item.

- This now includes the actual original specification of the item itself, to avoid confusion in larger Projects.

Luna AUTs supported

- AUTs that use the Eclipse Luna platform can also be tested with the ITE. This was also possible in version 7.2.

Export improved

- The export mechanism has been improved to use less memory, allowing larger Projects to be exported.

Toggling relevance of test runs

- You can now toggle the relevance of multiple test runs at once.

New option for content assist in the Component Names View

- You can now configure a delay for the content assist in the Component Names View.

- In the Preferences (in the Test section, you can enter a delay in milliseconds. This amount of time will be waited after each character entry before opening the content assist.

- If you have many component names, and / or don’t require the content assist as often, then you can increase this value to be able to type more of your name before seeing content assist.

- We have also adapted the behaviour of the content assist to not appear if you remove all of the content of the new name field in the Component Names View.

- You can press »ctrl+space« at any time to open the content assist.

Log files now split after 10MB

- Log files that get larger than 10MB are now automatically split and zipped.

Closing HTML AUTs via the close button

- If you close a HTML AUT by closing the browser, the ITE will correctly notice the closure after 5 seconds (configurable) and will remove the AUT from the running AUTs view.

- The mechanism works by polling the AUT, and if it is no longer there after the configured time, the AUT is considered to be stopped.

- If your AUT may sometimes be unreachable for longer than the default 5 seconds, you can change this time by using a process or system property:
  TEST_MAX_AUT_RESPONSE_TIME=<timeInMs>.

- Further information on this is available in this issue:
  http://bugzilla.bredex.de/1391.

p2 update site for IDE integration available in installer

- In the development folder of the installation, you can now find a p2 update site containing the Jubula Feature and Launch Integration.

## Known issues and other information

Problem displaying component names from browsers

- In some siutations, when viewing the Component Names View from a browser, you may see GUIDs (a long number/character string) instead of the component name.

- This is a problem displaying the component name at the moment and can be considered a display error, albeit a serious one.

- The component names themselves are correct, and can be seen either by opening the editor, or by refreshing the Project.

Issue with incorrect handling of null in renderers fixed

- Renderers in Swing that return null can now be correctly handled.

- See http://eclip.se/426978 for more details.

Selenium update

- We have updated the version of Selenium used for HTML tests to 2.39.

Port number for embedded AUT Agent changed

- The default port number for the embedded AUT Agent is now 60001.

- You can change the default port number in the preferences.

Table view has been removed from the Object Mapping Editor

- The table view has been removed from the Object Mapping Editor.

Problems opening BIRT reports when using IE11

- There is a known issue with BIRT reporting that occurs when using Internet Explorer 11.

- There is a ticket open in the GUIdancer Bugzilla (https://bugzilla.bredex.de/show_bug.cgi?id=1281) and in the Eclipse Bugzilla (http://eclip.se/422056) for this. The ticket in the Eclipse Bugzilla documents workarounds.

Java 1.4 AUTs no longer testable

- As of this version, Java 1.4 AUTs are no longer testable with the ITE.

Changes to the launcher for the AUT Agent

- The AUT Agent is no longer available under the name autagent-lin or autagent-sol.

- Use the launcher autagent instead.

Java 7 tests on Mac

- There are still some issues running tests on Mac machines with Java 7. We suggest using Java 6 on Mac machines for the moment.

Working directory for ITE and AUT Agent on Linux

- The AUT Agent and the ITE now use the current directory as their working directory on Linux systems.

The ITE now uses Java 7

- We have updated the version of Java installed with the ITE to version 7.

The installer requires Java 7

- You will need Java 7 installed to be able to run the installer.

iOS 5.0 no longer supported

- We no longer support testing on iOS 5.0 AUTs.

Working with RDP connections on Windows 8

- Windows 8 users working with RDP connections for test execution should ensure that they have installed all updates for Windows.

Updated the version of EclipseLink used

- In this version, we have switched to EclipseLink 2.5.1 and JPA 2.1.0.

Vista support removed

- We no longer execute tests on Vista: the support for Vista has been removed for this version.

Multi-window mode for HTML testing on Mac OSX

- There are known issues with starting AUTs that are using the multi-window mode on Mac OSX, both in Firefox and Safari.

- We have removed these combinations from our tests.

Pure SWT AUTs no longer tested

- We no longer execute regression tests on pure SWT AUTs. We do, however, perform various tests on RCP, which uses SWT components.

AUT Agent started without console per default

- The standalone AUT Agent is now started without a console per default.

- If you would like to see the console when starting the AUT Agent, you must adapt the autagent.ini file.

- In the -vm parameter, use java instead of javaw.

# Release Notes for Version 7.2.00092

## New Features and Developments

Support for linking tests to application lifecycle management (ALM) repositories

- You can now integrate your automated tests with external repositories which you have configured in your workspace and your Project.

- The integration lets you specify a task ID on items in your Project – most usually the task from an external system for which this test is relevant.

- You can open the task for a node from the browsers.

- When a test runs via the ITE, the test results from the test are attached to the relevant tasks in the external repository as a comment with a link which can be opened in the Dashboard.

- It is not currently possible to decide on a per-test basis whether or not to report. If you do not want to report for a test, then you should remove the checkboxes for reporting from the Project properties.

- Test Jobs currently do not report to external systems.

- The integration can be used with Bugzilla 3.6+, JIRA 5.0+ and Trac 0.12+. An integration with HP ALM is not possible in version 7.2, but was made available in 8.0.

New option in the testexec

- The testexec has a new option in the command line (not in the configuration file).

- Use the parameter -sx to not write any screenshots to the HTML or XML files.

Comments can be added to the Project and to categories

- You can now add comments to the Project and to categories in the Test Suite Browser and Test Case Browser.

New actions for testing checkboxes in SWT tables

- Tables in SWT/RCP AUTs that have a checkbox in the first column can now be tested.

- There are actions to toggle the state of the checkbox, and to check the state of the checkbox.

- The row to be checked is defined either by its selection or by the mouse position.

Save As... option in image view

- You can now save images from errors in the test directly to your file system using a new button and the context menu in the image view.

JProgress bar now supported as graphics component

- You can now map JProgressBar components in Swing and SWT AUTs.

- The component is supported as a graphics component – you can check its existence, wait for it etc.

HTML: the <div> tag is supported as a component with text

- You can now perform check text actions on components in HTML AUTs that use the <div> tag.

Changes to dashboard

- The URL for the Dashboard has been shortened.

- The dashboard URL is now:

      http://HOSTNAME:PORTNUMBER/dashboard

- The properties for the dashboard have also been renamed from com.bredexsw.guidancer to org.eclipse.jubula. Please ensure you update any properties files you use for the dashboard server.

Next and previous error buttons in Test Result View that appears during test execution

- You can now also use the next and previous error buttons for the Test Result View that appears during test execution.

New test data functions There are new functions available in the ITE:

- randomInt(exclusive maximum value) – to generate a random integer.

- replaceAll(string,regular expression,replacement) – to replace parts of a string with something else.

- uuid() – to generate a universal unique ID.

- base64Encode(string) – to encode a string to base64.

- base64Decode(string) – to decode a string from base64.

## Known issues and other information

dotnet toolkit renamed to win toolkit

- The dotnet toolkit has been renamed to the win toolkit in e.g. the Project wizard and properties.

Meters AUT and tests removed

- The meters application has been removed from the samples project and from the examples directory.

Change to the order of writing test results

- In previous versions, once a test run was finished, the test results were first written to a file (XML and HTML), then to the database.

- As of this version, this order has been changed. The test results are first written to the database.

H2 database version updated

- The drivers used for the embedded H2 database have been updated from version 1.1.117 to 1.3.168. These two versions are not compatible, because the file format has been changed. More information about changes in H2 are available at http://www.h2database.com/html/changelog.html.

- Old embedded H2 databases are not readable with the new version of the ITE. You should therefore follow the migration steps mentioned in the installation manual.

Database driver version updated

- All database drivers used by ITE to generate reports with Birt have been updated:

  - MySQL data base driver version updated from 5.1.10 to 5.1.25, see http://dev.mysql.com/doc/relnotes/connector-j/en/news-5-1.html.

  - Oracle data base driver version updated from 10.2.0.2.0 to 11.2.0.3.0, see http://www.oracle.com/technetwork/database/enterprise-edition/jdbc-faq-090281.html

  - PostgreSQL data base driver version updated from 8.4-701 to 9.2-1002, see http://jdbc.postgresql.org/download.html

Libraries for HTML tests version updated

- The version of Selenium used by ITE to interact with HTML AUTs has been updated from version 2.30.0 to 2.33.0. More information about changes in Selenium are available at http://selenium.googlecode.com/git/java/CHANGELOG

- Version 2.33.0 of Selenium supports Firefox 10esr, 17esr, 19 and 20 and IE10.

- The version of jQuery used by ITE for object mapping and test execution has been updated from version 1.7.2 to 1.10.1. More information about supported browers are available at http://jquery.com/download/.

JaCoCo version updated

- JaCoCo has been updated from version 0.5.9 to 0.6.3, which fully supports code coverage for Java 7. More information about changes in JaCoCo are available at http://www.eclemma.org/jacoco/trunk/doc/changes.html.

SLF4J version updated

- Version 1.7.2 of SLF4J in combination with version 1.0.7 of LOGBack are now used for logging. More information about changes in SLF4J and LOGBack are available at http://www.slf4j.org/news.html and http://logback.qos.ch/news.html.

# Release Notes for Version 7.1

## New Features and Developments

Jubula and GUIdancer standalones functionally identical

- The standalone versions for Jubula and GUIdancer have been unified so that they are functionally identical.

- This means that features such as Code Coverage and iOS testing that were previously only available in GUIdancer are now available in both tools.

- Both standalone tools continue to exist. The only difference between them is their branding.

- Jubula is downloadable by anyone from the BREDEX Testing Resources Portal at: http://testing.bredex.de. GUIdancer can be downloaded after purchasing a support package.

Search scopes supported

- The search dialog now lets you choose whether you want to search the whole Project, or just the node(s) you have selected.

- If you choose to just search within the nodes you have selected, then you can specify whether you want to use the selected node in the Test Suite Browser, the Test Case Browser, or both.

New mass replace operation for Test Cases

- From the Search Result View, you can now perform a mass replace of Test Cases.

- If you have searched, e.g. for all places where a Test Case is reused, and want to replace some or all of those places with a new Test Case, then you can select the option to replace the current Test Case references with a new Test Case reference.

- Any comments, Test Case reference names and the commented-out state of each replaced Test Case are transferred onto the new Test Case reference.

- You can also match any propagated component names and referenced parameters from the old Test Case to propagated component names and parameters from the new Test Case.

New function for accessing node attribute

- A new function has been added to the set of pre-defined functions in the ITE.

- The function is: ?getNodeAttribute() and it can have either name or comment as arguments.

- When name is chosen, the function reads the name of the node (e.g. Test Case, Test Step) on which it is resolved and uses this for the test.

- When comment is chosen, the function reads the comment of the node (e.g. Test Case, Test Step) on which it is resolved and uses this for the test.

New function for accessing values in central data sets

- There is a new function available in the pre-defined functions in the ITE.

- The name of the new function is: ?getCentralTestDataSetValue(), and it requires four arguments:

  dataSetName:

    The name of the central data set to search in.

  keyColumnName:

    The column that is used to find the correct line of the data set.

  entryKey:

    The value to locate in the key column that will provide the correct line.

  columnName:

    The name of the column in which the value to be chosen can be found.

- Within the specified data set, the required value is located based on the line found using the key column and entry key, as well as the column name for the actual value.

New option to change the column in a central test data set used by Test Cases

- If you have used a central test data set in multiple Test Cases and later realize that you have two columns in the central test data set that contain the same information, then you can change all Test Cases that use this central test data set to just use one column. Once you have done this, you can remove the unnecessary column from the central test data set.

- If you have searched, e.g. for all places where a central test data set is reused, and want to alter Test Cases that use this central test data set to use a different column in the central test data set, then you can select the option to change the central test data set column usage.

- You can change an existing parameter present in the selected Test Cases to target a different column in the central data set using the dialog that appears.

Multi-window support for HTML AUTs

- If your HTML AUT uses multi windows (e.g. pop-ups), then you can now specify this in the AUT configuration.

- AUTs that are running in multi-window mode show the Selenium console as well as the AUT when the AUT is started.

- The Object Mapping Editor has a new button to allow switching between multiple open windows for mapping components, and there are new actions in the HTML unbound modules to allow you to switch between windows during the test.

On-click expansion for pictures in HTML reports

- In HTML reports, you can now click on any screenshots taken on errors and they will be expanded to make the details more visible.

- Clicking the image again will reduce it to its original size in the test result report.

Kepler AUTs can now be tested

- It is now possible to test AUTs that are based on Kepler.

- Due to improvements in the object recognition, some components for RCP AUTs may need to be remapped.

New actions to correctly shutdown and restart an AUT

- Users testing Swing and RCP AUTs now have two new actions to Prepare an AUT for Termination and to Synchronize the termination and re-start.

- These actions can be used instead of the restart action for cases where the AUT cannot be restarted using this action, or when an AUT needs to be correctly shutdown and restarted as part of a test (e.g. to save a workspace, settings etc.).

- The actions must be placed on either side of any action that will cause the AUT to terminate (not to restart). The prepare for termination action must come first, followed (not necessarily directly) by an action to close the AUT (e.g. selecting ”Exit”). Directly after this action, the synchronize termination and re-start action must be used.

- The action to close the AUT must be an action that causes the AUT to run through the JVM shutdown hooks to properly terminate. Do not use the restart action to shut your AUT down.

- The combination of these three actions allows the AUT to be shutdown correctly and restarted.

## Known issues and other information

Mapping key combination for e4 AUTs

- In some e4 AUTs, a key-binding clash may result in the shortcut for the Object Mapping Mode not working on certain components.

- If you notice that you cannot map any / certain components, please alter the Object Mapping shortcut to an unused shortcut.

Multi-window mode much slower on IE

- The multi-window mode for HTML AUTs is considerably slower on IE than on Firefox.

- This is a known issue that is registered at Selenium.

Embedded Chronon support removed

- The embedded Chronon support for the standalone versions has been removed.

- You can still configure your AUT to run with Chronon.

# Release Notes for Version 7.0

## New Features and Developments

Support for testing AUTs written with e4

- AUTs that are written with e4 can now also be tested.

- As a result of this, the starting of RCP AUTs has changed slightly – please read the documentation in the section on Toolkits in the User Manual for more details.

- Currently, GEF figures can only be tested in AUTs written with Eclipse 3.x versions.

Testing of iOS AUTs now supported

- There is a new toolkit in Jubula for testing iOS AUTs.

- You can write tests for iOS apps and run them on the device or simulator.

- For more information on the prerequisites for iOS testing, as well as the information on working with the actions, please refer to the section on iOS in the Toolkit section of the documentation.

Addition of Turkish as supported language for the unbound modules

- Turkish is now supported in the unbound modules.

Jubula is now 64-bit compliant

- The installation of Jubula is now architecture-dependent.

- The Jubula.ini now contains different JVM-arguments defining the allocated heapsize:

  1024 mb

    for 32 bit installations

  2048 mb

    for 64 bit installations

HTML Test Result Reports now include screenshots on error

- Any screenshots taken automatically during a test (i.e. when an error occurs) are now also displayed in the HTML Test Result Reports that can be exported from the Reporting Perspective or that are generated automatically after the test.

Properties View and HTML reports parameter visualization updated

- The layout of the properties view and the HTML reports has been updated so that each parameter (test data) now only takes up one line.

- The name and type of the parameter are in the first column, and the value (which can usually be edited in the Properties View is in the second column.

- This makes the Properties View easier to read and to use.

Properties View easier to recognize as uneditable

- When selecting an item from a Browser, the Properties View is now more recognizable as non-editable.

- The background for the whole table is gray, and the color of the text has been changed from black to gray.

Double-clicking on any item in a browser opens the relevant editor

- If you double-click on an item in a browser that is, at the place where you double-click it, actually reused in another element, then the editor for the item’s direct parent will be opened, and the item you double-clicked will be selected.

- For example, if you double-click a Test Case in the Test Suite Browser that is reused in a Test Suite, then the Test Suite Editor for the Test Suite will open, and the Test Case you clicked will be selected.

- The same behavior applies to Test Cases reused in other Test Cases, Test Suites reused in Test Jobs, and Event Handlers reused in Test Cases.

- If the parent comes from a reused Project, then the editor will not open.

- This behaviour makes it easier to navigate around your Project.

Double-clicking on any item in an editor opens the item in its own editor

- If you double-click on an item in an editor, then the editor for the item you clicked will be opened (i.e. as if you had pressed »F3« - open specification).

- For example, if you double-click a Test Case in the Test Suite Browser then the Test Case Editor for the Test Case you clicked will be opened.

- The same behavior applies to Test Cases reused in other Test Cases, Test Suites reused in Test Jobs, and Event Handlers reused in Test Cases.

- If the item comes from a reused Project, then the editor will not open.

- Using »ENTER« to open the Add new Test Case reference dialog has not changed.

- This behaviour makes it easier to navigate around your Project.

Selenium version updated

- The version of Selenium used by Jubula to execute HTML tests has been updated to version 2.30.0.

Chronon version in Jubula updated

- Jubula now uses version 3.2.129 of Chronon for the embedded support.

Support for testing on Windows 8

- Windows 8 is now supported for testing AUTs.

Support for own text renderers in SWT

- If you have components with text that cannot be read due to it being rendered differently, you can now allow the text to be read.

- Use setData(TEST_TESTABLE_TEXT), text on the instance of the item or component whose text you want to read in your test.

## Known issues and other information

Migration of existing toolkit extensions

Due to major refactoring in the remote control code of Jubula you must migrate any toolkit extensions you have written. Theses changes only affect the remote control extension. The ITE extensions must not be changed. As a first step, we recommend reading the Extension Manual. Most information about the new implementation and a simple example can be found there.

To migrate any existing extensions, the following steps must be performed:

- Define a target platform for the remote control enviroment as mentioned in the Extension Manual 2.3.1

- Alter your remote control extension project to be an OSGi-fragment and set the appropiate host bundle. See Extension Manual 2.3.1

- Adapt your current implementation as described below.

- Deploy your fragment as described in Extension Manual 2.3.2

All ’old’ implementation classes (*ImplClass) have been removed and rewritten. If you previously used the Jubula implementation classes you will have to change the class you are extending:

- org.eclipse.jubula.rc.common.tester
  in this package the base classes for most of the TesterClasses are located. Some toolkit-specific implementations are in the toolkit bundles named below.

- org.eclipse.jubula.rc.swt.tester
  SWT-specific implementation for List, Table, Tree, Application and Menus

- org.eclipse.jubula.rc.swing.tester Swing-specific implementation for JList, JTable, JTree, Application and Menus

You must also write your own adapter factory (Extension Manual 2.3.1 Create an Adapter), which must be in the package org.eclipse.jubula.rc.common.adapter.

This adapter factory manages adapters that are needed for the tester classes. The adapters are necessary for the tester classes because the tester classes are toolkit-independent.

In the adapter factory you write, you must define which component (widget) is adapted by which class. For example, a JTable is adapted by the JTableAdapter. For this you can reuse existing SWT or Swing adapters or you can write your own. If you want to write your own adapter it is important that you use the Jubula interfaces of the adapter, because the tester classes require this information.

The following packages are important for adapters:

- org.eclipse.jubula.rc.swt.tester.adapter
  SWT adapter.

- org.eclipse.jubula.rc.swing.tester.adapter
  Swing adapter.

- org.eclipse.jubular.rc.common.tester.adapter.interfaces
  Interfaces for all adapters.

Migration of GEF accessibility identifer

Due to changes in the structure of our RCP accessor we have changed the location of the GEF implementation. The bundle has changed to org.eclipse.jubula.rc.rcp.e3 and also the packages now begin with org.eclipse.jubula.rc.rcp.e3. To migrate your existing plugin you have to do take the following steps:

- Change the target definition as described in the Extension Manual 3.1.1

- Change the bundle in the MANIFEST.MF from org.eclipse.jubula.rc.rcp to org.eclipse.jubula.rc.rcp.e3

- Change the adapter type in the plugin.xml to role="input">org.eclipse.jubula.rc.rcp.e3.gef. identifier.IEditPartIdentifier

- Change all packages in your classes to the new appropriate packages

Changes to resolving of referenced parameters

- In previous versions, there was an error in the way referenced parameters were resolved, which lead to the data for the parameter being read each time the parameter was referenced. This could lead to problems with e.g. time-sensitive functions. If a Test Case was structured to enter the date using the ?now() function and then check the entered text (where the data for the text entry and the check were referenced and ?now() entered at the parent Test Case), then the entered value and checked value would not be the same.

- This has been changed for this version, so that references are resolved at the place where the parameter is defined.

- Any users who have Test Cases whose parameters define variables which are declared within the Test Case itself will have to restructure such Test Cases so that the variable is not set before it is called, e.g.

  > -TC1 [VARIABLE_SET=VAR1;VARIABLE_CHECK=$VAR1]
  > – Set variable =VARIABLE_SET
  > – Check variable =VARIABLE_CHECK

- The correct way to structure such Test Cases is as follows:

  > -TC1
  > – Set variable: VAR1
  > – Check variable:$VAR1

Removal of option ”Create support information package”

- The menu option:
  Help-->Create support information package
  has been removed.

Chronon support for AUTs now with separate installation

- You can now only use a separate installation of Chronon as a monitoring agent for your AUT.

- The support for the embedded Chronon recording in AUTs has been removed.

Some categories, component names and unbound modules renamed The following items have been renamed in the unbound modules:

Combo boxes

  have been renamed to Combo Components. This is also evident in the abbreviation used for the unbound modules and the component names. It has changed from cbx to cbc.

Tabbed panes

  have been renamed to Tabbed Components. This is also evident in the abbreviation used for the unbound modules and the component names. It has changed from tpn to tbc.

Text field / text area / text pane

  has been renamed to Text Component. This is also evident in the abbreviation used for the unbound modules and the component names. It has changed from txf to txc.

Known issue with using observation mode on Gnome

- When using the observation mode on Gnome, Jubula may close unexpectedly.

- This is documented in issue http://bugzilla.bredex.de/729.

Deprecated modules and Test Steps removed

- All unbound modules that were preceded with DEPRECATED have been removed. These modules should be removed from use in your Projects before switching to the new version.

- All Test Steps that had the status deprecated have also been removed. You should ensure that you no longer use deprecated Test Steps before switching to the new version.

Updated migration information

- The information on migrating to new versions has been updated.

- The Installation Manual contains the migration information.

Modelling removed

- The Modelling Perspective and the generation of Test Cases from UML diagrams has been removed from this version.

# Release Notes for Version 6.1.00106

## New Features and Developments

Multiple Test Case Browser instances now supported

- You can now open the Test Case Browser multiple times.

- You can designate one Test Case Browser as the main browser. This browser will be used for actions such as show specification etc.

Workspace dialog now allows remembering of workspace

- You can now select the option to remember your default workspace in the workspace chooser.

Remember password and auto-login for database

- In the database login dialog, you can select the option to remember your password.

- If you have selected this option, you can also specify that the database should be used as the default database you will be automatically logged in when a database connection is required.

- The above options are not available for the embedded database.

- To change the database you are connected to, or to change your default database login, use:
  Test-->Select Database

Auto-load for default Project

- In the Open Project dialog, you can now identify the selected Project and version number as your default Project.

- You can have one default Project per workspace.

- When you have a default Project set, then selecting:
  Test-->Open
  will automatically load this Project.

- You can remove the default loading in the Test preferences.

Testexec and DBTool can use -dburl instead of workspace (-data) parameter

- To make working with the testexec and dbtool easier, you can now use the dburl parameter to specify which database to connect to during the process.

- This removes the need to specify which workspace to use (via -data) when working with the testexec and dbtool.

- You can still enter the workspace and the -dbscheme information if you prefer not to use the -dburl parameter.

Selenium version and tested browsers updated

- Jubula now uses a newer version of Selenium that supports newer versions of Firefox.

- We have updated our tests to run on Firefox version 15.

Frames and iFrames now supported for Web Testing

- AUTs that contain Frames and iFrames can now be tested by Jubula

HTML:pre tags now supported as component with text

- In HTML AUTs, you can now map components that use the `<pre>` tag and perform e.g. check text actions on them.

Chronon: Embedded recorder no longer needs to be commented in

- You can now start the embedded Chronon recording in Jubula without having to comment it in in the .ini file.

- The only exception to this is on Linux systems, where you must comment Chronon in for the ITE in the .ini file by removing the hash signs from the two lines in the .ini file, and then restart Jubula. If you are starting Jubula from the command line with Chronon on Linux, please ensure that your current directory is the Jubula directory, otherwise Jubula will not start.

Chronon: New preference page and options for ITE Chronon

- In the preferences dialog, there is now a Chronon category. In this category, you can select the ITE Chronon page.

- On this page, you can configure options for the embedded Chronon in the ITE. You can configure the output directory for the Chronon recording, as well as any include or exclude patterns that should be included and / or ignored for the recording.

Chronon: Support for Chronon server installation for use with AUTs

- When you use Chronon with your AUT, you now have two choices – you can use the integrated Chronon to record your AUT or you can specify where your Chronon installation is, thus allowing you to use the Chronon Recording Server. This is the recommended choice for working in continuous integration processes.

Chronon: Support for exclude patterns in AUT configurations

- If you are using the integrated Chronon support for testing your AUT, then you now have the option to specify exclude patterns for the recording as well as include patterns.

Chronon: Jubula now uses Chronon 3

- Jubula now uses Chronon version 3 to perform embedded recording (in Jubula itself) and also for the integrated recording in AUTs.

JRE version updated

- Jubula now uses version 1.6.0_33 of the Java runtime environment.

Jubula supports the testing of .NET AUTs

- You can now also test .NET AUTs with Jubula.

- Currently, WinForms AUTs can be tested.

- Further information is available in the section on Toolkits in the User Manual.

New metric in Jubula: Waits and Delays

- There is a new metric in Jubula that analyzes the waits and delays used in a test that has run.

- You can start the metric from a Test Result Report and enter a parameter for the minimum amount of waited time (in milliseconds) that should be considered.

- The Search Result View displays all the static waits within the node you selected. They are sorted according to the action they belong to, and you can see how much time each type of wait accumulates to over the test.

New BIRT Report: Test Execution Overview

- There is a new BIRT report available to give an overview of the test execution.

- This report shows a list of executed, relevant Test Suites over the time period selected. For each day in the time period, there is a colored block for the Test Suite to display its status. Green means that the test ran without any errors. Red means that the test ran, but with errors. Yellow means that the test ran more than once on that day. White means that the Test Suite did not run on this day. This report is useful for teams with large amounts of Test Suites who need to ensure on a daily basis that all Test Suites were started.

New JaCoCo version used

- Jubula now uses JaCoCo version 0.5.9 for code coverage. Further information on the changes in the new JaCoCo version can be found in the JaCoCo release notes.

## Known issues and other information

Mac OSX Mountain Lion gatekeeper prevents install4j generated installer from starting

- This is caused by a too-restrictive setting on the Mountain Lion gatekeeper security feature.

- Setting the security level to Mac OSX Lion compatible level resolves the issue.

Actions: Check selection of entry by index/value only checks one entry

- The actions for checking whether an item in a list is selected have been adapted so that they only accept one piece of data, and not comma-separated values as was previously the case.

- To check whether multiple items are selected, use a data set which contains a list of the items to check.

Announcement for next release: removal of deprecated unbound modules and major API change to RC code

- In the next release, we will remove the unbound modules in all toolkits that are marked as deprecated. Please ensure that you have replaced any modules marked as deprecated before updating to the first released version in 2013.

- Due to changes we will be making to our implementation classes for the RC components (actions on components), there will also be major API changes which will affect extensions that have been written.

Removed BIRT Reports for Object Mapping Quality

- The BIRT reports for monitoring object name quality (OMNameQuality and OMNameQualityChart) have been removed.

# Release Notes for Version 6.0.1

## New Features and Developments

Chronon support

- Jubula now allows the use of an embedded Chronon recorder and also the production of Chronon recording files during automated tests (Jubula Feature users: this feature is currently only available in the standalone version).

- Activating the embedded Chronon recorder in Jubula will result in your actions being recorded in a monitoring file which can be used for analysis purposes should you encounter any errors.

- You can also configure your AUT to use Chronon as a monitoring agent so that you can generate recording files from your automated tests.

- The currently used version of Chronon is 2.0. There are some performance issues still in this version that may lead to test runs and performance being affected, particularly in larger AUTs and Projects. Please follow the instructions in the documentation for increasing heap size and ensuring the capability of your test machines.

- We do not recommend having Chronon running at all times, due to possible performance degradations through the monitoring. Instead, we recommend that you activate the Chronon recorder when you are trying to reproduce an error.

Tests updated to newer versions of IE and Firefox

- The tested versions for web AUTs now include IE 9 and Firefox 10

# Release Notes for Version 6.0.007x

## New Features and Developments

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 the Test Result View.

- You can use this information to see whether your tests or parts of your tests are taking longer than you expected them to, without having to set timers or manually check timestamps.

- The HTML and XML reports generated or exported for the test results also show the execution times.

- You can switch off the decoration in the Jubula client in the label decoration preferences.

Parameter values now shown for each node in Test Result View

- The parameter values entered or used at a specific level (Test Case, Test Step) are now shown in the Test Result View.

- You can use this information to see which data were used for your Test Cases, without having to click through each individual node in the Test Result View. This can be especially useful if you have one Test Case that runs multiple times with different datasets.

- You can switch off the decoration in the Jubula client in the label decoration preferences.

Missing data decoration now shown in the Test Case Editor and Test Suite Editor

- When working on a Test Case or Test Suite in their respective editors, you will now see small red crosses on any referenced Test Cases or Test Steps in that editor which have missing data at this level (i.e. data that should be entered in this editor).

- This will help avoid problems with forgetting to enter data in the Properties View.

Functions can be entered as parameter values

- Alongside concrete values (abc}}), references (=P1) and variables ($VAR), you can now enter functions as data, or as parts of your data.

- The sign to introduce a function is the question mark: ?

  | Any question marks used as test data will have to be escaped using one or more backslashes as of this new version. A warning in the console view will appear after importing your Project if you have any unescaped question marks in your data. You can then use the search function to find them and mask them.

- There are functions available out of the box for various mathematical calculations and for working with dates.

- Functions can be embedded in other functions, e.g. ?add(?sub(3,2),4) to add the result of (3-2) to 4.

- Functions can also make use of other data entry options in Jubula such as variables (?add($VAR1,=P1) adds the number in the variable VAR1 to the number in the reference P1).

- You can add your own functions via an extension point.

Categories now supported in the Test Suite Browser and Central Test Data Editor

- It is now possible to create categories for Test Suites and Test Jobs in the Test Suite Browser, as well as for central data sets in the Central Test Data Editor.

- Existing Projects will be shown as having two categories (Test Suites and Test Jobs) in the Test Suite Browser as was previously the case. However, you can now rename, delete and rearrange categories in the Test Suite Browser.

Teststyle framework and some guidelines now also in Jubula

- There is a new properties page in the Project properties for Teststyle.

- The Teststyle framework is a feature that allows Projects to be analyzed for their adherence to standards, best practices and rules for test specification.

- The framework was previously a part of GUIdancer and has now been migrated to Jubula.

- Jubula contains a small set of standard rules for test specification. Teststyle in GUIdancer contains more guidelines and rules for naming conventions, test specification and test structure.

Analysis framework in Jubula

- A new analysis framework has been added to Jubula to gain information on the size, ratios and details of a Project.

- The analysis framework currently contains three example metrics that can be run on existing or new 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 the Check Property action, except that the expected value must not be entered. Instead, the actual value is saved into a variable you define.

- You can use this value later on in the test, or you can compare various values using the actions to compare string values or compare numeric values.

- One example use case for this new action is to test table filters. The rowCount of the table can be saved into a variable before filtering, and the rowCount after filtering into a different variable. The variables can then be compared with each other to ensure that the second value is less than the first, for example.

New extensible adapter mechanism for Swing components

- Jubula now allows you to add support for renderers for Swing components without the getText() method.

- An example of the adapter mechanism can be found here:
  http://git.eclipse.org/c/jubula/org.eclipse.jubula.core.git/
  tree/org.eclipse.jubula.examples.extension.swing.rc.adapter

- This does not replace the support for custom Swing renderers that can be changed directly by your developers.

- If you are able to change the renderers yourself, you can still implement one of the following in your renderer:

  > public String getTestableText(); public String getText();

Completeness check shown as progress window

- After saving in the ITE, the completeness check which validates the state of the Project (test data, object mapping, missing Test Cases etc) is now shown explicitly as a progress window.

- This results from performance improvements made to the completeness check.

Eclipse Marketplace Client now accessible from within the ITE

- You can now open the Eclipse Marketplace Client from the Help menu.

- You can use the Marketplace Client to search for new software to install.

- Please be aware that we do not test Jubula for compatibility with plugins installed via the Marketplace that are not provided by BREDEX GmbH or the Eclipse Jubula project and therefore recommend caution when installing new software.

Changes to layout of properties view for test results

- The properties view for test results now shows all test data as two columns: the parameter name and the value.

- This reduces the amount of space required to see test data for test results.

GD_AUT_STARTUP_DELAY renamed to TEST_AUT_STARTUP_DELAY

- There is an undocumented variable that can be set as an environment variable to increase the delay between starting an AUT and checking that it is there.

- This delay was named GD_AUT_STARTUP_DELAY and has now been updated to TEST_AUT_STARTUP_DELAY. Any customers using this variable should update it in their test environment.

Selenium update

- The version of Selenium used by Jubula has been updated to 2.12.0.

New Dashboard application to view test result reports in the browser

- Jubula contains a new web application which displays the Reporting Perspective.

- Using this Dashboard, you can open and analyze Test Result Reports in a web browser without having to start Jubula, and over the network.

- The Dashboard consists of a server for the Dashboard ( dashboardserver.exe) can be found in <INSTALLATION_DIR>/dashboard.

- You can start the application in the browser by entering:
  http://<HOSTNAME>:<PORTNUMBER>/dashboard

- The Dashboard can also be started in a default mode which starts the dashboardserver with default parameters (for the embedded database) and opens the browser on your machine.

New JaCoCo Version allows large reports to be sent to ITE

- Jubula now uses the latest version of JaCoCo, 0.5.5

- In the new version, large reports must not be created as zipped files on the AUT Agent machine, but can be sent to the ITE as well. We have successfully performed code coverage analysis with JaCoCo in Jubula on an AUT with 72,000 classes.

- Any increase to heap space must now be done for the ITE, no longer for the AUT Agent, as the handling for reports is now in the client code.

- The documentation has been updated, and now also includes tips on using JaCoCo to see the Lines of Code executed by the test (Class files must be compiled with Debug information) and warns against using JaCoCo at the same time as other byte-code manipulations.

- JaCoCo can now be used if you are using the embedded AUT Agent.

Mylyn tasks can be created from the Reporting Perspective

- In the Reporting Perspective, you can now create a Mylyn report from within an open Test Result View for a test run.

- The Mylyn task is created with the information available in the node you select from the test result.

- This can be used to make entering e.g. issues in bug-tracking systems about failed tests more comfortable.

Mylyn connectors for Bugzilla and Trac available with Jubula

- In addition to local tasks, there are now Mylyn connectors for Bugzilla and Trac available with Jubula.

- The connectors must be configured to your system and are available from Add Task Repository in the New Task Dialog.

- The connector for Bugzilla supports 3.0 and later, the connector for Trac supports 0.10 to 0.12 through Web and XML-RPC.

Altered license terms for maintenance contracts

- The license terms for maintenance contracts have changed. Maintenance contracts are no longer automatically renewed, but customers are reminded two months in advance of their expiration.

- New maintenance contracts can be purchased before the expiration of the old contract for a discount, or for the full price if they are purchased after the expiration of the old maintenance contract.

## Known issues and other information

Text input problems on Mac systems for RCP (Indigo)

- Due to an issue in SWT, text input of characters involving the »SHIFT« key (upper case letters, some special characters) on Mac for RCP AUTs that use Indigo as a target platform does not work in this version.

- The issue has been fixed in SWT and will be available in Eclipse Juno.

New workspaces required

- Due to changes to internal IDs, a new workspace is required for this version.

- You can export your database preferences from your old workspace and import them into your new one.

- Other preferences must be noted and manually updated in the new workspace.

AUT Agent takes longer to start

- In the current version, the AUT Agent takes longer to start than in previous versions.

- If you try to connect to an AUT Agent before it is running, you will receive an information message that the connection could not be established.

- You may need to bear this in mind for automated tests in a continuous build and test environment.

License Agreement changes

- There have been changes to the way maintenance contracts work.

- Please check the license agreement for more details.

# Release Notes for Version 5.2.00265

## New Features and Developments

Embedded gdagent

- 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 AUT 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.

  Figure 1. Embedded AUT Agent

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, match parameters 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.

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.

  Figure 2. Deleting unused Component Names

HTML Test Result Reports can be expanded again

- Following changes made for the initial contribution to Eclipse, 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.

  Figure 3. HTML Reports

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 AUT

- As a side effect, the colors on the component names (green) and technical names (red) that were displayed in previous versions are now no longer shown. Once the Object Mapping Editor has been saved, all names are shown with plain black icons.

  Figure 4. Colored Dots for Object Mapping

Migration wizard re-enabled

- When migrating to the new version of Jubula, 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.

  Figure 5. Migration Wizard

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.

Progress View

- 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.

Object mapping: Degree of recognition accuracy for a test run can be viewed

- The Object Mapping Editor has been extended so that the accuracy of component recognition is persisted and can be displayed.

- As well as displaying the state of component recognition when a technical name is collected from the AUT the section called “New Features and Developments”, the degree of recognition accuracy is also noted for each test run.

- You can see the values for the recognition accuracy in two new BIRT reports in Jubula.

  OMNameQuality

    shows a breakdown of the component names used in your test, and displays the degree of accuracy they were located during the test. You can use this report to see whether there are any component names that may need to be remapped (i.e. who are close to the threshold of not being found) before the test encounters a Component Not Found error.

  OMNameQualityChart

    This report is a visual (graph) representation of the accuracy with which components were located during the test run. You can use the report to help you decide which components may need to be remapped, as they may soon result in a Component Not Found error during the test.

Mylyn: Refactored Test Cases are added to context

- When working on a Mylyn task in app, Test Cases you create using the refactor function are now automatically added to the context.

Mylyn: Test Cases opened via »Ctrl+Shift+T« are added to context

- When working on a Mylyn task in Jubula, Test Cases opened using the key combination »Ctrl+Shift+T« are now automatically added to the context.

Mylyn: Test Cases added via Test Case reference dialog are added to context

- When working on a Mylyn task in Jubula, Test Cases added using the Add Test Case reference dialog are now automatically added to the context.

Teststyle: Rules can now be viewed via the Properties View

- When working with Teststyle, you can now open the Project properties dialog to see the rule that has been flouted via:
  Show Teststyle Rule
  from the Problems View.

Changes to BIRT reports

- The BIRT report GUIdancerFULL has been removed.

- There are new BIRT reports:

  - GUIdancerComments shows a table of all failed relevant tests for the time specified, including the comment title that can be entered in the Test Result Summary View. This report is useful for delivering daily status reports of the tests.

  - GUIdancerDuration shows the duration of the chosen tests.

  - GUIdancerExecutionHistogram shows the proportion of executed, failed and non-executed Test Steps for a test. This report is most useful when one specific Test Suite is compared to see its progress over time.

  - TestresultSummary shows a table of the Test Result Summary View for the dates and tests chosen.

- You can now also enter the Test Job as a parameter for the report. The Test Suites in the Test Job are still displayed individually, however.

License Dialog: Restart prompt

- Once a license has been added via the Preferences, a dialog is shown to remind you to restart Jubula before continuing.

- From the dialog you can choose to restart Jubula automatically.

## Known issues and other information

autrun directory has changed

- The autrun application has been moved from its own directory in the installed version to within the server folder. The autrun directory no longer exists.

- Scripts using the autrun option will have to be adjusted to reflect this change.

The type of error an Event Handler reacts to cannot be changed once the Event Handler has been added

- In the current version, the type of error you choose for an Event Handler cannot be changed in the Properties View once the Event Handler has been added.

- If you want to change the error type for an Event Handler, then you must delete it and re-add it with the correct error type.

JFace decoration error

- Under some circumstances, there may be an error in the decoration resulting from our use of the org.eclipse.jface.resource.CompositeImageDescriptor. This results in a Null Pointer exception.

- If this occurs, please restart Jubula.

Necessary SWT Version

- To be able to test AUTs on Mac systems, the required SWT version is 3.6.

- The required SWT version for Windows and Unix systems is 3.1.

French (FR) keyboards

- The current keyboard layout mechanism for SWT and RCP keyboards does not work for French (FR) keyboards.

- Testers with AUTs in French should consider using a Canadian keyboard layout or any other keyboard where the base keys do not include special characters such as ampersand.

# Release Notes for Version 5.0 and 5.1.00155

## New features and developments

Code coverage

- Jubula now lets you run code coverage for Java applications written in Java 1.5 or higher.

- The code coverage tool JaCoCo is supported out-of-the-box and can be added to your AUT configuration in the AUT configuration dialog.

- You can view the results of the code coverage monitoring from the Test Result Summary View.

Teststyle

- Jubula has a new feature to improve the quality and structure of the tests you write.

- The Teststyle plugin lets you define guidelines for your Project and informs you when a guideline is not upheld.

- You can set the message level (information, warning, error) for the guidelines as well as the context they should be valid for.

- Teststyle is added by default to all Projects. You can alter the Teststyle settings via the Project properties.

New license mechanism

- The license mechanism in Jubula has been changed.

- Jubula no longer uses a license server to manage floating licenses. The new individual user licenses can be requested from the Jubula team as part of your maintenance contract.

- The licenses can be entered in the Preferences, under: Jubula - Licenses.

ID Attribute Name for HTML AUTs

- Each supported component in HTML AUTs can have its own attribute used to identify it during test execution.

- In your AUT configuration, you can define an attribute name which should be used as an identifier for components.

- For example if your attribute name is: testid
  (e.g. <div testid=''Username''></div>)
  then you would enter testid in the AUT configuration.

Test debugging - continue without Event Handler

- There is a new option in Jubula to make running interactive tests more comfortable.

- On the toolbar, there is a new button to ”Continue without Event Handler”. You can use this button in combination with the ”Pause on Error” option.

- If a test you are running encounters an error, the test is paused die to the Pause on Error option. You can then click ”Continue without Event Handler” to ignore the error and continue as if no error had occurred.

Copy ID to clipboard and open Test Case via its ID

- There is a new option in the Test Case Browser to copy the unique ID for a Test Case to the clipboard.

- You can use this ID to refer to the Test Case from external systems such as bug-tracking systems or requirements management systems.

- You can open a Test Case based on its ID by pressing »Shift+F9«.

Support information package

- To reflect the changes to the support system, the option to send a support email has been updated to create a .zip file as a support information package.

- Should you find an error, you can upload the information package to Bugzilla as a part of the error description.

New database configuration

- The configuration tool and database configuration tool are no longer a part of the installation package.

- The configuration options for the database connections are now in the preferences under: Test - Database Connections.

- The embedded database is configured as the default. You can add other database configurations using the buttons and the dialog to add database connection details.

- You can export and import your database preferences using the File-->Export menu.

New -data parameter in the test executor and dbtool

- As the database configurations are now in the preferences, you must enter a workspace (where the correct preferences are saved) for test execution via the test executor and for working with the dbtool.

- The workspace parameter is »-data <path to workspace>«.

- The workspace parameter cannot currently be entered in the configuration file for the test executor, it must be entered directly into the command line interface.

Project migration to the new version

- We have changed our database abstraction layer from Hibernate to JPA/Eclipse Link.

- For this reason, the migration of your Projects to the new version cannot be carried out automatically by the database migration tool.

- Instructions on migrating your Projects and clearing your database scheme are in the Installation Manual.

Amount of results shown in the Test Result Summary View is now configurable

- You can now configure how many results should be shown in the Test Result Summary View based on how old they are.

- In the Test result preferences, you can specify how many days’ worth of test result summaries should be shown. The default is set to 30 days.

- You can see the current setting in the Test Result Summary View.

- Results not displayed are not removed from the database and are still considered for report generation. They are simply not visible to make filtering and sorting over more recent results more comfortable.

Two new BIRT reports

- There are two new reports that can be generated from the Test Result Summary View.

- The first is a report that shows code coverage for the chosen Test Suites.

- The second is a report that shows any comments written for unsuccessful Test Suites which can be used as a daily summary of the test status.

BIRT reports show comment title for executed Test Steps

- If you have a BIRT report which shows the executed Test Steps for a Test Suite, you can hover over the point on the graph marking the number of executed Test Steps to see the title of any comment you wrote for the test run.

- If the expected Test Steps and executed Test Steps are the same (i.e. the whole test ran), you will not see the comment.

Test execution speed increased

- We have significantly increased the speed at which tests are executed.

- Should you want to slow a test down to watch it, then you can set a step delay in the Properties View for the Test Suite.

- You may notice that some tests require explicit synchronization (e.g. waiting for windows to appear or to close) to ”keep up” with the increased speed. If you prefer, then adding a step delay of 1000(ms) should produce the test execution speed from previous versions.

Extensions must be adapted

- As there have been changes to our API, any extensions you are using in your Projects must be adapted to the new changes.

- The largest change is that package prefixes have been changed. Instead of com.bredexsw.guidancer, the new name is org.eclipse.jubula.

- Other changes include modified class names (the GD prefix has been removed or replaced by JB).

- Your client and RC (server) extensions must be adjusted and recompiled with the new Jar files.

Support for div containers in HTML

- We now support components created using <div></div> containers on the level of Graphics Component.

- This means you will be able to perform certain checks on such components and also send clicks to them.

Support for lists in HTML

- You can now check the existence of entries in lists created in HTML using the <ol> and <ul> tags.

Support for sliders, date and time, spinner and scale components in SWT

- The SWT components slider, date and time, spinner and scale components in SWT are now supported as Graphics Components.

- This means you will be able to perform certain checks on the components as well as click them or in them.

New names for various Jubula components

- We have renamed various parts of Jubula:

  - What we previously referred to as the client (the application where tests are written) is now known as the Integrated Test Environment (ITE).

  - The gdrun command for starting AUTs is now called autrun. The command is also now called autrun and must be changed in any scripts that use it.

  - The command line client for test execution is now called the test executor. The command is called testexec and must be changed in any scripts that use it.

  - The RCP Accessor is now called the RCP Remote Control Plugin.

  - The environment variables that can be used in Jubula have also been renamed:

    - GD_COMP_NAME (used for setting a unique name for RCP components) is now called TEST_COMP_NAME.

    - GDAutStarterPort (used to set a default port number for the system) is now called TEST_AUT_AGENT_PORT.

    - GDUDV_ (used to set your own environment variables is now called TEST_UDV.

    - The pre-defined test execution variables are now preceded with TEST_ instead of GD_.

New perspective names

- The perspectives have been renamed. Each perspective type (specification, reporting, execution) is preceded by Functional Testing.

New and moved menu options

- The ITE now contains a menu point:File.

- This menu allows you to import and export database preferences to Jubula, to save, rename, refresh and exit the ITE.

- The previous Project menu is now called Test. Here you will find the menu options that used to be under Project, including creating, deleting, importing and exporting Projects.

Moved preferences

- The preferences for the test can now be found in the preference dialog under the option Test.

New BIRT version

- If you create your own reports for Jubula from this version, then you must use version 2.6.1 of the BIRT viewer and engine. Our reports are created with this version of BIRT and Eclipse version 3.6.1.

## Known issues

OS X: Green borders in AUT “flicker” in Object Mapping Mode

- This issue occurs when collecting components from an SWT or RCP AUT running with the Cocoa implementation of SWT. As such, this problem may affect AUTs running on OS X.

- When the mouse is moved over components in the AUT, the green border alternately disappears and reappears with each movement. A component cannot be collected when the green border is not visible. In order to work around this issue, it may be necessary to move the mouse within the component until the green border (re)appears.

# Release Notes for version 4.3.01105

## Information

This release is a patch to fix a problem that occurred in the unbound modules concrete whereby the tree component had a false component type. The database and license are the same as in version 4.3.01105.

## New features and developments

Mylyn integration

- The Mylyn plugin is now available for use within the ITE.

- You can connect to repositories (e.g. bug-tracking systems) to work on testing tasks directly in the ITE.

- You can also create your own local tasks, and reduce the amount of Test Cases visible to only those required for the current task.

Central test data

- The ITE has a new editor for managing data centrally for a Project

- The Central Test Data Editor can be opened via a button on the toolbar.

- Within the editor, you can add data sets which can then be referenced in Test Cases.

New data option and display in Properties View

- The Properties View now shows what type of data is currently being used for a Test Case.

- The possible data sources are:

  Referenced Test Case

    the data being used have come directly from the original specification of this Test Case.

  Local Test Case

    the data being used were entered for this Test Case. You can change from local to referenced test data using the combo box to reset the default value from the referenced Test Case.

  Central test data set

    the data have come from a central test data set.

  Excel data file

    an Excel file has been entered as the data source.

New search dialog and options

- There are new options to search for items and test data within a Project.

- The search dialog can be opened from the toolbar and offers searches for:

  Keywords

    Names of Test Steps, Test Cases, Test Suites, Test Jobs and categories in the Project

  Test data

    Data contained in Test Cases, Test Steps and central data sets

  Files

    File types and contents in the workspace

  Tasks

    Tasks from repositories

- Search results are shown in the Search Result View. Items can be opened in their editors by double-clicking the specific search result.

Manual Test Steps

- You can now define manual Test Cases

- There is a new module for a manual Test Step.

- Manual Test Cases can be combined into Test Suites and executed.

- During execution, a dialog appears to inform the manual tester which steps to perform.

- The tester can mark the action as passed or failed and can write comments about the Test Step.

- The result reports from manual tests can be examined and analyzed just like result reports for automated tests.

Testing AUTs started by other AUTs

- It is now possible to test an AUT that was started by another AUT.

- There is a new mode for the AUT Agent to allow this, the lenient mode.

- AUTs started in this way must be of the same toolkit as the original AUT.

- For each newly started AUT, a new AUT ID is generated with a running number.

Test results

- Test results that are reopened from the Test Result Summary View now contain complete information about each Test Step.

- Test results can also be exported from the Test Result Summary View in HTML and XML format.

- The option to automatically clean up test result details is now part of the Project properties, and no longer a user preference.

- In the Test Result Summary View, you can now enter comments about each test run to document the reason for failing or passing.

New split pane view for the Object Mapping Editor

- The Object Mapping Editor has a new view – the split view.

- In the split view, each category (assigned names, unassigned component names and unassigned technical names) has a different pane.

- This allows you to navigate to the place you require in each category separately to make mapping in large Projects more comfortable.

New actions

- Check existence of window by title

- Check text at mouse position in trees

- Store value at mouse position on trees

- Store value on selected node in trees

- Store value at mouse position in tables

New parameters for existing actions

- The action for selecting a node from a tree now also has the parameter extend selection so that multiple nodes can be selected in trees.

- The parameters for actions requiring modifiers (control, alt etc.) have been changed so that a space-separated list of modifiers can be entered. Content assist is available for the modifier parameters.

Protection for reused Projects

- There is a new option in the Project wizard and Project properties to protect a Project.

- We recommend marking a Project as protected if you are using it as a library (referenced) Project for another Project.

- In protected Projects, Test Cases cannot be deleted, and the edit parameters dialog cannot be opened.

- This is to stop any irrevocable changes being made that would affect the Projects that reuse the protected Project.

- The protected status of Projects can be altered in the Project properties.

Viewing BIRT reports in embedded database

- BIRT reports generated from the Test Result Summary View can now be viewed when using the embedded database.

Show where used on Test Suite

- The action Show where used (»F6«) is now also possible on Test Suites that have been reused in Test Jobs.

Open specification action

- There is a new action available on Test Cases and Test Suites which have been reused (in other Test Cases or in Test Jobs).

- Use »Ctrl+F6« to open the specification of the selected Test Case or Test Suite in the relevant editor.

- This action is possible even if the Test Case or Test Suite to open is hidden due to an active filter.

Open Test Case action

- There is a new dialog to open an existing Test Case or multiple Test Cases in their editors.

- Use »Ctrl+Shift+T« to open the dialog and select the Test Cases to be opened.

- This action is possible even if the Test Case or Test Suite to open is hidden due to an active filter.

Show corresponding specification in Object Mapping Editor

- In the Object Mapping Editor there is a new option to show the corresponding specification of a component name.

- You can use this option when a component name appears in the Object Mapping Editor that you should have overwritten.

- The Search Result View only shows places which could have lead to this component name appearing in the Object Mapping Editor, not all places in the test where it has been used.

Key combination to switch views in the client

- We have introduced shortcuts to switch to specific views in the specification perspective.

- To switch to the Test Suite Browser, use »Alt+Shift+1«

- To switch to the Test Case Browser, use »Alt+Shift+2«

- To switch to the Properties View, use »Alt+1«

- To switch to the Data Sets View, use »Alt+2«

- To switch to the Component Names View, use »Alt+3«

- To switch to editor, use »F12«

The key combinations can be changed in the preferences.

Support for custom renderers in Swing

- Custom renderers in Swing AUTs can now be tested as long as the renderer implements either getText() or getTestableText().

- The method signatures you implement must be:

  > public String getTestableText(); public String getText();

- If you don’t have a getText() method, then we recommend using the getTestableText() option to avoid conflicts.

Dropping Test Cases directly into the editor area

- You can now drop Test Cases directly into the editor, without having to place the Test Case before or after another Test Case in the editor.

- The Test Case is placed at the bottom of the tree in the editor.

## Other information

New workspace recommended for 4.3

- We recommend setting up a new workspace for version 4.3.

Object mapping in RCP AUTs that do not use GEF

- We have fixed an issue with automatic component naming in RCP AUTs.

- Customers testing RCP AUTs where no GEF bundles are present are advised to remap their components.

# Release Notes for version 4.2.01053

## New features and developments

Eclipse 3.6 supported

- Tests can be written for Eclipse applications that are written in 3.6

Viewing test results

- Full test result details that are still in the database can now be opened in the Test Result View from the Test Result Summary View.

- This lets you review tests that ran overnight directly in the ITE.

Automatic database migration

- The ITE now contains a database migration wizard.

- When a connection to a database is made in a new version, the ITE automatically recognizes whether the database version is incompatile.

- If so, you can start the migration wizard. You specify which Projects should be imported into the new database (the Projects must have been exported from the previous version).

- The migration wizard converts the database automatically to the new version.

Commenting out Test Cases

- You can now comment out Test Cases and Test Steps in editors.

- Items that have been commented out are inactive and are neither validated for Test Suite completeness, nor executed.

New parameters for table actions

- Actions on tables now have new parameters for row operator and column operator.

- You can now select rows and columns based on their title and also determine how you want the selection to occur (equals, matches, simple match, not equals).

New parameter for select actions

- Actions that select items from tables, lists and trees have a new parameter for mouse button.

- You can now define which mouse button should be used to select the item.

Number of failed Test Steps shown

- The Test Result Summary View now also has the information about how many Test Steps failed in a test run.

Information about whether test result details are available

- The Test Result Summary View now also has the information about whether the details for a test run are still in the database.

- If the results are still available, then the Test Result View can be reopened.

Spring to next/previous error

- In the Test Result View which opens when you open the results for a test run from the Test Result Summary View, you can use two new toolbar buttons to spring to the next/previous error.

Showing comments for Test Cases

- Any comments you write on Test Cases are now visible as a tooltip when you hover over the Test Case in the browsers or in the search result view.

Pause on error

- There is a new button on the toolbar to pause the test execution if an error occurs.

- This can be switched on and off during a test run and allows you to easily stop the test to see what went wrong.

- The test can be continued by clicking the pause test execution button on the toolbar.

Using running AUT details to define an AUT

- AUTs that have been started using the gdrun command can now be automatically defined in the ITE.

- You can select the option to create an AUT definition from the running AUTs view for any AUT that is currently unknown.

Show referenced children

- There is a new option in the preferences to show referenced children in Test Cases in the Test Case Browser.

- This preference is activated by default.

- Deactivating the preference means that any children of referenced Test Cases are not displayed in the Test Case Browser.

- This can help in particularly large Projects to inprove performance.

New action

- There is a new action to wait for the menu component.

## Other information

XML and HTML reports scheduled for removal

- The XML and HTML reports that can be generated by the ITE (configurable in the preferences) are scheduled for removal in the next versions.

- There will be an alternative feature to create a HTML report from the test result report, as long as the test details are still in the database.

- For queries about this plan, please contact the support team.

Deprecated unbound modules earlier than 3.0 scheduled for removal

- The unbound modules that have been deprecated in versions earlier than 3.0 are also scheduled for removal in the upcoming version.

- We always recommend updating to the latest version of the unbound modules and removing any references to deprecated modules in your tests.

New unbound modules for tables and for select actions on lists, trees and tree-tables

- Because we have added new parameters to actions on these components, there are new unbound modules for the actions.

- The old unbound modules have been set to deprecated.

- We recommend updating any deprecated modules in your tests with the new modules.

- You can see what the new module is by looking in the deprecated module - these now contain the new actions.

Merging in the Object Mapping Editor

- The option to merge components in the Object Mapping Editor has been temporarily deactivated for this release.

# Release Notes for version 4.1.01039

## New features and developments

New option in delete Project dialog

- When you delete a Project, you can now decide whether you want to keep the test results for the Project or delete them as well.

Performance improvements

- We have further improved the performance for the saving and loading of Projects. The validation of Test Suites now runs as a background job so that test specification can continue while the tests are being validated.

- Test Suites must be validated before they can be executed.

Generated names penalty removed

- The generated names penalty has been removed from the object mapping configuration area and from the object recognition calculation.

Optional automatic screenshots when errors occur

- You can now define whether or not screenshots should automatically be taken when an error occurs.

- Screenshots taken in this manner are saved into the database and can be viewed in the Image View by clicking on the failed Test Step.

- You can alter this preference in the Test Result preference page.

- In the command line client, screenshots are automatically taken unless you include the parameter -s.

New relevance flag for test results

- You can now specify at the beginning of each test execution whether the test results are relevant for your test reports.

- You can alter this preference in the Test Results preference page.

- In the command line client, test executions are automatically relevant unless you include the parameter -r.

MAC OSX no longer in BETA

- We have now removed the BETA status of our MAC support.

- Please be aware that pure SWT tests are not supported on MAC systems.

- Testing RCP AUTs also has some limitations on MAC, e.g. the action to select a value from a combo box does not work, and there are problems with the selection of tabs by their values.

- The license server will now run on MAC machines, as long as the development kit for the environment is installed.

## Other information

Compatibility with 4.0

- The database is compatible with version 4.0, so your 4.0 database can continue to be used with 4.1.

- The server and client components have been changed, so these will need to be reinstalled for 4.1.

- There have been no changes to the license mechnism or license administrator - you do not need to reinstall your license server.

Eclipse plugin removed

- The functionality to run the ITE as an Eclipse plugin has been removed.

HTML actions deprecated

- The action follow link in HTML is deprecated. Use the action click on Graphics Component instead to follow links.

- The action select window is also deprecated, and has not yet been replaced with a new action in this release.

New database configurations in DB Configuration

- We have added separate database configurations in the DB Configuration Tool for Oracle 8,9 and 10 as well as the embedded database and Oracle XE.

- There are also two new options: MySQl and Postgresql. These are shown as unsupported: we have tested that the ITE can connect to them and open Projects, but do not let our full tests run on them at this time.

New colors for Test Cases

- The unbound modules are now colored blue to make them easier to distinguish from other Test Cases.

- We have also made Test Cases that cannot be directly edited slightly grayer to make it easier to see which Test Cases are editable.

## Known issues

Console output for DBTool

- The DBTool does not yet produce an output when parameters are false or when errors occur.

Edit parameters dialog

- When editing parameters via the edit parameters dialog, it is currently necessary to save the Test Case and reopen it to see the changes in the Properties View.

Merging component names in the Object Mapping Editor

- At the moment, the merging of component names does not work in the Object Mapping Editor.

- You can use the Component Names Browser to merge component names instead.

# Release Notes for version 4.0.01205

## New features and developments

New implementation for HTML testing

- We have a new implementation for the testing of HTML AUTs.

- The new HTML toolkit is multi-browser compatible and has been tested for Windows (for IE6 and higher and for Firefox 2 and higher), Linux (Firefox 2 and higher) and Mac (Firefox 2 and higher and Safari 3 and higher).

- Firefox 3.6 is not yet supported.

- The new implementation also supports the testing of dynamic components.

- Please be aware that Frames and IFrames are not yet supported in this new implementation.

New handling for starting AUTs

- It is now possible to start multiple AUTs.

- Each AUT now receives an ID which can be used to differentiate between various AUTs (or instances of the same AUT) for object mapping, observation, and test execution.

- Some buttons that were previously on the toolbar have been moved to the Test Suite Browser and the new Running AUTs View.

New gdrun option to start AUTs independently of the ITE

- AUTs can now be started in one of two ways.

- They can be started as in previous versions via an AUT configuration. There is also a new option to start an AUT without an AUT configiration, independently of the ITE.

- For this, you can use the command gdrun with parameters for toolkit, AUT ID etc.

- This option is not currently available for HTML or SWT AUTs.

New running AUTs view

- There is a new view in the specification perspective which shows a list of running AUTs.

- The AUTs are shown using their ID.

- Via this view, you can start Test Suites and stop AUTs.

Testing different AUTs in one test

- Being able to start multiple AUTs and the new gdrun command mean that it is now possible to test multiple AUTs (or instances of the same AUT) in one test.

- Test Suites can now be combined to Test Jobs. A Test Job executes each Test Suite on the specified AUT.

- This feature is currently only available for AUTs that are written with the same toolkit (e.g. Swing) or when the Project toolkit is set to concrete (i.e. no specific actions for particular toolkits are used in the test).

- All AUTs to be tested in a Test Job must have been started using the gdrun command.

New reporting perspective

- The ITE has a new reporting perspective. After every test run, the test results are now stored in the database. Both detailed results and a test result summary are saved.

- The test result summaries are shown in the new Test Result Summary View. You can use this view to sort and filter your test results.

- The test result details can be automatically removed from the database after a specified number of days. This feature can be activated and configured in the preferences.

Generation of test result statistics

- From the Test Result Summary View, you can create BIRT reports of your test runs.

- There is a selection of example reports available in the Test Result Summary View.

- You can also use a BIRT designer to create your own reports.

- The built-in BIRT reports can currently only be used with an Oracle Database.

Duplicate AUT configuration

- To ease the configuration of multiple AUTs, there is now the option to duplicate an existing AUT configuration.

New action: take screenshot of active window

- There is a new action in the concrete toolkit to take a screenshot not of the whole screen, but of the currently active window.

New action: check property on figure

- For the RCP toolkit, there is a new action to check the property of a figure in GEF editors.

Timestamps in test result reports

- The HTML and XML test reports have been extended so that timestamps for each step are documented.

Mac BETA Support

- The Mac Version is still in beta status.

- Pure SWT AUTs cannot be started by on Mac systems. RCP AUTs, however, can be.

New options for the DBTool

- The DBTool has two new options: -deleteall deletes all Projects (and test results) in the database. -keepsummary leaves the test result summaries in the database when a Project is deleted.

## Information

Altered XML Scheme for extensions

- We have made a small change to the XML scheme for extensions.

- In the ComponentConfiguration.xml the tag componentClass has changed.

- Instead of specifying your component class as:

  > `<componentClass>javax.swing.JComboBox`

  > `</componentClass>`

  Use the following:

  > `<componentClass name="javax.swing.JComboBox"/>`

AUT Starter renamed AUT Agent

- To reflect the change in behavior of the server component, we have renamed the AUT Starter to AUT Agent.

- The commands to start and stop the Agent have also changed. See the user manual for more details.

Fix for GEF Editor figure recognition

- We have fixed an error for figure recognition in multi-page GEF editors.

- Figures are now correctly found if an editor has multiple tabs.

New licenses

- Version 4.0 requires new licenses. You can request your new license from the support team.

New support service available

- We have updated our support service so that customers can also purchase premium support for questions relating to test environment, process etc.

- Full details about the new support service are in the license agreement and in the shop.

Alternative classloading

- We have made some changes to the classloading for AUTs.

- Should you notice any problems when starting your AUTs with the new version, you can switch to the old classloading mechanism by performing one of the following:

  - Setting an environment variable GD_USE_CLASSIC_CL=true

  - Setting the Java property -DGD_USE_CLASSIC_CL=true

Running the License Server on Windows 7

- When starting the License Server as a Service (for example, after installing GUIdancer with administrator access rights), the firewall must be explicitly configured to allow incoming traffic for the License Server process.

## Known issues

Refresh problem in the Component Names Browser when renaming components in the Object Mapping Editor

- After renaming a component name in the Object Mapping Editor, the Component Names Browser is not refreshed until the Project is re-opened.

- We recommend renaming component names in the Component Names Browser until this issue is resolved.

Incorrect display of technical component name

- In some cases, a technical name may be collected from the AUT in the form guidancer.concrete.button instead of Button/Radio Button/Checkbox, for example.

- This is a problem with the display of the component name and does not in any way affect the object recognition or mapping.

Pausing and stopping test execution during restart AUT

- There is a known issue which occurs when a test is paused or stopped while the action restart AUT is being executed.

- Doing this leads to the buttons on the toolbar being incorrectly disabled. Please wait until the action is finished before stopping or pausing the test, to avoid this problem.

Start Incomplete Test Suite is no longer supported

- The action to start an incomplete Test Suite is no longer supported.

Closing an AUT in the observation mode

- AUTs cannot currently be stopped during a test.

- If the observation mode is running, and you close the AUT (e.g. via File-Close), this leads to the object mapping for the Test Case being falsely marked as incomplete.

Default Event Handlers in Test Suites: RETURN

- The return default Event Handler in Test Suites does not yet exist, although this is documented.

Automatically ending Check Mode

- When recording a verification step in Observation Mode, the button Ok, but stop Checking does not end the Check Mode. The mode must be ended manually.

# Release Notes for version 3.2.02004

This release is a patch for version 3.2.01081 which contains updates to the documentation.

## Information

New software license version

- The software license has been updated.

- You can read the new license in the installation directory in the guidancer folder.

New object mapping shortcut

- The standard shortcut to collect objects from an AUT in the Object Mapping Mode is now: »Ctrl+Shift+Q. You can see and change this shortcut in the preferences.

# Release Notes for version 3.2.01081

## New features and developments

New actions

- This version contains a variety of new actions to:

  - Check enablement, existence and selection of items in context-menus.

  - Open context menus with any button (right, left or middle).

  - Check the existence of tabs.

  - Check the value of a specific tab.

  - Check the existence of a value in a row or column in a table.

  - Check the editability of a selected cell in a table.

  - Check the editability of a cell at a specific mouse position.

  - Refresh components in a web application.

Collecting components using clicks

- Customers whose AUTs cannot accept keystrokes can now set the object mapping preferences to collect components using clicks.

Improvement for dynamic web testing

- There is now a new option in the object mapping preferences to refresh components in a web application. This can be used during object mapping to recognize newly added components since the last refresh.

- This action is also available as a Test Step to achieve the same effect during a test.

Switching database and database configurations

- There is a new database configuration tool to select, add and configure databases for use with the ITE. More information on this is available in the Installation Manual.

- It is now possible to switch between databases or database users in the ITE. This saves having to restart the client to switch the database.

Windows 7 supported

- Version 3.2 has been tested with Windows 7 as well as XP and Vista.

## Other information

Administrator privileges required for configuration tools and license administrator

- The configuration tool, the database configuration tool and the license administrator may require administrative privileges.

- Run these tools as an administrator to be able to configure your installation.

New AUT Agent commands under Linux

- The AUT Agent commands under Linux have changed.

- To start the AUT Agent, enter: ./AutStarter (-p <port number>)

- To stop the AUT Agent, enter: stopAutStarter.sh

Fixed issue with a component name

- We have fixed a falsely calculated component name in the unbound modules for dragging and dropping list items.

- The affected component names are: nn_dragSource_lst and nn_dropTarget_lst.

- Customers who have used unbound modules containing these component names should take the following steps to update their Projects:

  1. Open the Project and switch the version of the unbound modules from 3.1 to 3.2.

  2. Find the places where the affected component names were used in the test by using F7 on the unbound modules for dragging and dropping in lists.

  3. Any affected places will display a message in the Component Names View: no component type exists!.

  4. Make a note of the component name that you used here.

  5. Make a small change in the Test Case Editor to make the editor ”dirty” and save the editor.

  6. Add the component name that you previously used in this Test Case and save the editor again.

## Known issues

Selection of multiple SWT list items under Linux

- There is an issue in some versions of GTK and the selection of multiple list items.

- Items further down in the list may be clicked falsely. This is a known error in GTK.

# Release Notes for version 3.1.2003

This release is a patch for the previous 3.1.01019 version. For more information about the 3.1 version, see the previous release notes.

## New features and developments

New timer actions

- Application - Start Timer - This action allows you to start a timer with a given name. In addition to the timer name this action requires a variable in which to store the start time.

- Application - Read Timer - Use this action to read the current value of a timer you have started and store this value in a given variable.

- Application - Check Numeric Values - With this action two numeric values can be compared. Valid comparison methods are e.g. “less-than” or “greater-or-equal-than”.

## Other information

Fix for GEF figure recognition

- The figure recognition in the GEF toolkit has been corrected.

- Figure positions will now be correctly calculated regardless of which side the palette is on.

Connect to AUT Agent

- The issue in the previous release with connecting to the AUT Agent and then disconnecting before a Project was open has now been fixed.

Wait for Window actions

- The Swing implementation for the Application - Wait for Window... actions has been modified.

- The modification fixes an issue with the occasional incorrect evaluation of the window status.

- Affected actions are: Wait for Window, Wait for Window to Close and Wait for Window Activation

# Release Notes for version 3.1.01019

## New features and developments

GEF support

- We have added support for the figure canvas and figure testing for RCP applications.

- See the section in the user manual on GEF testing and the reference manual for details on testing applications with GEF components.

- GEF actions can not be recorded using the observation mode.

Eclipse 3.5 compatibility - important information

- You can now test applications written with Eclipse 3.5.

- Existing customers wishing to test Eclipse applications on more than one platform should activate the new generate names option in the AUT settings.

- This option improves the generated names and object recognition for buttons in RCP wizards and dialogs. It is deactivated in existing Projects and activated in new ones. Activating this option will mean remapping affected components from the AUT.

- The affected components can easily be found by filtering the Object Mapping Editor using this text:
  *swt.widgets.button.
  Delete the affected components and then refresh the Object Mapping Editor. You will then see the component names which need to be remapped.

Mac OSX BETA support

- Testers wishing to try out the BETA for Mac support are invited to do so.

- The license manager cannot run on a Mac system; it must be installed on a Windows or Linux system.

New actions

- The action Copy to clipboard has been added to the Application component. This can be used on native dialogs during the test, to enter filepaths etc.

- We have updated the actions on tables to allow selection and checking of cells by the header value as well as the column index. Entering an integer will result in the column being found based on its position. Entering a string will mean that the column is found based on its header text. Header texts currently only support the equals operator. Old table actions are now deprecated and should be exchanged for the new actions.

- It is now possible to select and check the selection of checkboxes on SWT Trees.

RCP component name generation

- In the AUT settings, there is a new option for RCP AUTs to generate unique names for buttons in dialogs and wizards.

- This option is automatically on for new Projects and deactivated in existing Projects.

- If your tests must be platform independent, we recommend activating this option for your existing Projects. Information on how to easily remap the affected components is available above in the section on Eclipse 3.5.

Filter in Object Mapping Editor

- The Object Mapping Editor now has a text filter like the browsers.

- Unlike the browsers, the Object Mapping Editor filter searches based on both the text and the technical component type in the editor.

Control decoration

- We have added control decoration to various components in the user interface to help new users understand some of the more advanced options.

New cheat sheet

- A new cheat sheet on using Event Handlers is available in the help menu.

Show unused Test Cases

- There is a new filter in the Test Case Browser – show unused Test Cases.

- Use this filter to refactor and clean up your tests by identifying which Test Cases are no longer referenced.

Show where used on Test Cases

- This action now also works on Test Cases from reused Projects.

- This means that you can easily search for references to deprecated unbound modules from our Test Case library in your Project to switch them.

New preferences

- In the preferences, you can choose to hide the information behind Test Step names.

- You can also deactivate the option to show the original Test Case name behind a new name when you rename a reused Test Case.

## Other Information

Coolbars and Toolbars in Eclipse

- To fix an issue with the recognition of coolbars in Eclipse, we have introduced better component recognition for coolbars and toolbars.

- Customers testing RCP applications will have to remap their toolbar and coolbar buttons unless these have been given names by the development team.

Whitespaces in commands

- The action execute external command has been changed to allow whitespaces in commands and in parameters.

- Relative paths can be written simply with the white spaces included. You will need to use quotes (") around the path or command if you are using path fragments (e.g. ./ or ../) for the relative path.

- When using absolute paths, use quotes (") around the command or parameter containing the whitespaces.

For example, instead of:
`C:\Program Files\guidancer\guidancer.exe`
`-data C:\Program Files\guidancer\ws`
enter: `"C:\Program Files\guidancer\guidancer.exe"`
`-data "C:\Program Files\guidancer\ws"`

- In Linux, quotes may be placed around the command and the parameter. Windows cmd.exe can only accept quotes in either the parameter or the command.

- Please bear in mind that strings within the quotes are not checked for validity.

Absolute and relative searches in tables

- The relative search in tables now searches starting from the next item after the selected item.

- Move actions in the table search relative to the mouse position.

Keyboard mappings

- We have added documentation how to add keyboard mapping files to the RCP accessor.

New parameters for the keyboard modifiers

- The parameters »Cmd« and »Mod« have been added to actions for key combinations to allow testing on MAC systems, and to ensure platform-independent testing across Windows, Unix and MAC systems.

## Known issues

Connecting to the AUT Agent

- When no Project is open, connecting to the AUT Agent and disconnecting again results in no longer being able to connect to the AUT Agent until the ITE is restarted.

Exit Code 11

- Restarting an RCP AUT may cause an error in Eclipse which displays an error code 11.

- This can be hindered by updating the launcher to Eclipse version 3.3 and using the parameter `--launcher.supressErrors (Executable)` .

Click in component

- We do not recommend using the percentages 0 and 100 for click in component when scrollbars surround the component.

GIJ and OpenJDK

- These are not supported.