Jubula 8.5.0 release

On the 17th May, we released the latest version of Jubula. This release has got a few really nice features in it that I’d like to introduce you to.


A while ago, we gathered some feedback from users and found that navigating in the ITE could be more comfortable in some places. Two new options are available as of 8.5:

  • Double-clicking on a root node in the Test Case Editor jumps to the open editor where this Test Case is reused. This is really useful for navigating “back up” the hierarchy when you have multiple editors open.
  • For users working with the function getCentralTestDataSetValue, it’s now possible to navigate between the properties view and the central test data sets view (and back again) to quickly see where a value is referenced, and which value is actually used in the function. This feature should save users a lot of clicking and scrolling.

Deleting with orphans

A project using Jubula was doing some cleanups of unnecessary Test Cases. It occurred to them that it was very difficult to find out which Test Cases are no longer used and can therefore be deleted. The new feature “delete with orphans” lets you delete an unused Test Case (that you’ve found for example using the filter to show unused Test Cases) – and all of the Test Cases in it that will become unused once their parent is deleted. This works recursively as well, so you can really clean up your unused Test Cases quickly and easily.

Test Result Reports

We’ve made two improvements to test result reports – first of all, they can now also be exported in JUnit report format to make it easier to integrate them into your continuous build and integration process. Secondly, screenshots taken on error now highlight the component that was under test to make it easier to identify what the problem could be.

New actions for the API

Testers working with the API often want to do a little more grey-box testing – with the new actions getProperty and isSelected this becomes easier. getProperty lets you access properties of a component, and isSelected can be used to find out the toggle state of a check box or radio button.

As always, more information is in the release notes, but these are the main highlights! We hope you enjoy working with the new version!