Skip to main content

What's new in Jubula Indigo

What's "old"

The Indigo release for Jubula consists for the most part of the features released with the pre-release version, which in turn is almost the same feature-set as was in GUIdancer 4.3.
Because of this, everything is new for this first release of Jubula!

A really quick overview of what was in already:

  • You can create (automate) tests by dragging and dropping modules from libraries of actions installed with Jubula.
  • Tests can be automated for AUT's (Applications Under Test) written with Swing, SWT/RCP/GEF and HTML.
  • Tests can be executed interactively or via the test executor (e.g. for continuous integration).
  • Test results can be viewed directly in the Integrated Test Environment after execution and can also be reopened for later analysis, as they are stored in the database.
  • Errors in the test are recorded automatically as screenshots and can be dealt with using "Event Handlers".
  • There are various options for searching, categorizing and filtering to make working with Jubula more comfortable.

The best thing to do to find out more is to read the documentation and do the cheat sheets to see what you can do with the tool. Look at the documentation page for more details.

What's new

Interactive test analysis:
Continue without Event Handler

When running tests from the Integrated Test Environment (ITE), you could already globally opt to pause the test execution if any errors occur. Using the new "continue without Event Handler" button on the toolbar, you can specify on an error-for-error basis whether to execute an Event Handler for the error or whether to continue the test as if no error had occured.
This lets you get a quick overview of the status of the whole test without having to restart the execution / reset the application after each error.

Continue without Event Handler
Copy ID to clipboard and Open Test Case from ID

To allow a light integration with external systems, the unique ID for a Test Case can now be copied to the clipboard. An ID already in the clipboard can be used to open a Test Case using the key combination Shift+F9.

Copy ID to clipboard
Database configuration

Database configuration is now a part of the preferences. The default database is the embedded (H2) database. Other databases can be added via the database preference page.

Test execution speed

We have significantly increased the speed at which tests are executed. Use the Step Delay field in the Properties View for a Test Suite to set a global delay between executed steps to make watching a test easier.

Added support for components

Div containers and lists in HTML applications are now supported.
The SWT components slider, date and time, spinner and scale are now supported as Graphics Components (i.e. they can be mapped, clicked and checked for existence, focus and various properties).

HTML ID Attribute Name

In the AUT configuration, you can now specify an attribute name which will be use to identify components in the HTML AUT.

Renaming and restructuring

The perspective names and some names for components have changed. The options to open, import, export and delete projects are now in the "Test" menu not in the "File" menu, and the preferences are now under the topic "Test".

Migrating from GUIdancer 4.3 to Jubula

Read the Installation Manual for information on migrating from a 4.3 database to the new database scheme. Any existing extensions must also be migrated:

  • The package names have changed from com.bredexsw.guidancer to org.eclipse.jubula
  • The class prefix name GD has been replaced by JB
  • Client and server (RC) files must be adapted and recompiled with the new Jar files.

Fixed Bugs for Indigo

Back to the top