Bredex

Jubula Software Downloads

### End of support for Jubula ###

We have made the decision to discontinue support, development and maintenance for Jubula. For the last few years, Jubula has been in maintenance mode (occasional updates for new Java versions, but not much more). Our internal observations in projects that use Jubula is that it is relatively mature and stable, and is generally capable of testing the current generation of Java applications. We still provide the most recent downloads here, as-is. That means that if it works for your project, then you are free to use it. Please be aware, though, that we will not be able to provide support or information about its use or any issues you may find. Customers with existing support contracts will of course receive support until the end of their contracts.

### End of support for Jubula ###

 

Jubula – a free, professional automated test tool

Jubula is a cross-platform, code-free, automated GUI test tool that support a variety of GUI toolkits. BREDEX GmbH provides Jubula for free. It is open source under the Eclipse Public License.

Jubula 8.8.1

Installer for Jubula on 64-bit Windows:

SHA Key fingerprint Download for Windows:

Installer for Jubula on 64-bit Linux:

SHA Key fingerprint Download for Linux:

Usage and features

Jubula is an automated GUI testing tool. Its area of expertise is functional (black-box) testing through the GUI. Workflows that are often left to be tested manually can be automated so that the software is thoroughly and reliably tested on a regular basis. Tests automated with Jubula can serve as system tests for new features and can be run as regression tests to ensure the continued functionality of a system after changes to the software.

The following table gives an overview of Jubula’s features:

  • Supported applications: Swing, SWT/RCP/GEF, Java FX
  • Platforms: Windows and Linux
  • Test specification language: Either code-free or in Java
  • Test design: Ready-to-use action libraries, Modular approach, Data-driven testing, Wide reaching search and refactor options, Tests can be written before the application is available, Support for new components can be added
  • Test execution: Integrates with Continuous Integration pipelines, Heuristic, robust object recognition, Automatic screenshot on error, Error handling for test failures
  • Test result analysis: Interactive test analysis, In-tool analysis of test runs, HTML Reporting, Code coverage

Getting Started

There are two ways to write tests with Jubula: you can use the Integrated Testing Environment (ITE) to write tests via drag-and-drop without code, or you can use the Jubula actions from our library directly in Java. Details and information about using Jubula is available from the documentation, which is installed with the program.
Using the ITE, we recommend starting with the “Cheat Sheets”. Simply go to “Help -> Cheat Sheets” in the main menu.

How do I get set up to use the Jubula Client API for writing tests in Java?

There are two ways to write tests with Jubula: you can use the Integrated Testing Environment (ITE) to write tests via drag-and-drop without code, or you can use the Jubula actions from our library directly in Java. Details and information about using Jubula is available from the documentation, which is installed with the program.

If you are using the ITE, we recommend starting with the “Cheat Sheets”. Simply go to “Help -> Cheat Sheets” in the main menu.

How do I get set up to use the Jubula Client API for writing tests in Java?
If you want to write tests with Jubula in Java using the Jubula Client API, you can follow these steps to get up and running. The steps assume that you are familiar with working with Eclipse.

You will need:

Familiarize yourself with the examples 

  • Clone the Jubula repository: org.eclipse.jubula.core
  • Have a look at the examples.
  • The examples are in the namespace o.e.j.examples.api You can make the examples runnable using the target platform in o.e.j.examples.api.configuration.
  • To execute the examples, you will need to start the AUT Agent from within the Jubula standalone installation. Then you can run the tests using the prepared launch configurations.
  • The simplest example is org.eclipse.jubula.examples.api.swing. This is an example which only runs with junit as a standard java project. Please read the README.md for the correct setup.

There are two ways to create your own project. 

  • First way with using plain java.
    • Copy the org.eclipse.jubula. examples.api.swing project and rename the project.
    • Remove the existing Junit test and OM class.
    • Configure your own AUT and startup script(See the AUTs class and the SimpleAdder.cmd).
    • Create your own Junit test with the Annotation @ExtendWith( JubulaJunitExtension.class) on the class.
    • To perform object mapping for tests via the API, you must:
      • Start your application under test, either via autrun or via a class you write using the Jubula API e.g. see StartAgentAndAUT
      • Right-click on the AUT Agent icon in the system tray Select “Object Mapping/Start/<your application name>
      • Use the key combination “ctrl+shift+q” to collect the technical identifier for the component you want to address
      • Copy the identifier from the object mapping window and paste it into the relevant part of your test do not forget to stop the AUT Agent!
  • Second way using the target platform from eclipse.
    • Add the target platform from the Jubula standalone installation: <installationDirectory> /development/ org.eclipse.jubula.repo.zip to a default target platform.
    • Write your tests!
    • You will need to connect to a running AUT Agent in your tests.
    • The AUT Agent can be started from the Jubula standalone installation.
    • Start the AUT Agent with the parameter -om to be able to use the AUT Agent to perform object mapping for your application without requiring the ITE (see more about this in our Object Mapping FAQ)
    • You will need to configure how your AUT should be started.
    • Use the examples to see how AUTs are started.
    • If your AUT is an RCP AUT, you will need to configure it for testing. To perform object mapping for tests via the API, see the section above.
    • Use the CAPs to execute actions on your AUT. The actions are described in the reference manual. You can read more about the Client API in the developer manual here.

2024 © BREDEX GmbH