A Step-by-Step Guide to Jubula – The Open Source Automated Functional Testing Tool

[Thorough walkthrough with numerous visuals, please give time for them to load]

In this lesson, we will be delving into the vastly recognized open-source functional testing tool: Jubula.

Jubula is an automated functional GUI testing project under the Eclipse banner. Its strength lies in its ability to facilitate automated tests from the user’s viewpoint, requiring minimal to no coding knowledge. This tool leads to enhanced lucidity and maintenance of tests, as well as saving a significant amount of time.

There exists a plethora of open-source automation applications in the industry, complete with robust online support.

As for Jubula, the online assistance provides an abundance of details about its native framework. This data is immensely beneficial for testers with limited technical expertise who are not directly involved in the coding phase, but are eager to compose automation scripts via the Jubula GUI.

However, automated testers with a technical background may find it challenging to access the help required to develop a customized framework using Jubula.

This in-depth walkthrough aims to disseminate the wisdom I have accumulated in Jubula, hoping it will assist you in devising an adjustable, robust, and dependable automation testing framework.

Before we start, let’s explore its native framework (This part of the instruction will walk you through the fundamentals) and subsequently move onto Developing a framework using Java coding in Jubula.

The Necessities – Native Framework:

Installation and Initiation:

(Please Note: Click on any image for an enlarged view)

1) Clink this link to visit the download page.
Note – Explore various choices based on your interests by visiting this download webpage.
2) Register and Log in.
3) Select Download Installers.
4) Press on the download page found under the Jubula downloads section.
5) Choose the installer suitable for your OS.
6) Install using the downloaded exe file and save in your chosen folder (in my case, it is placed in C:Program Files).
7) Following the successful installation, you can start the tool from ‘All programs’.

8) While launching the tool, designate the workspace in your preferred location.

Example AUTs:

One remarkable feature of this tool is its bundling with sample AUTs (Applications Under Test). The AUTs can be located in <Installation Directory>examplesAUTs.

In our case, it is located here: C:Program Filesjubula_8.2.0.021examplesAUTs

Example Project

With both Jubula installed and the sample AUTs ready, let’s venture into automating a basic addition function using a ‘swing’ app known as ‘SimpleAdder’.

The application is initialized using the file:

‘C: ProgramFilesjubula_8.2.0.021examplesAUTsSimpleAdderswingSimpleAdder.cmd’ and appears as follows:

The objective is to input ‘value1’, input ‘value2’, press ‘=’ button, and confirm the ‘result’.

The Testing Process:

Below are the instructions needed to automate the task:

Step 1 – Arrange a project.
Step 2 – Define an AUT (Application Under Test).
Step 3 – Establish a test case, incorporate test steps, and map the data.
Step 4 – Assemble a test suite.
Step 5 – Allocate the AUT to the test suite.
Step 6 – Map the test case onto the test suite.
Step 7 – Pair logical test objects with technical object identifiers.
Step 8 – Initiate the test suite.

Let us dive into each step in more detail:

Step #1 – Arrange a project

A Project in Jubula functions as a logical workspace that consolidates all necessary components needed to complete a testing task.

Initiating a project is done as follows:

1) Navigate to Test > New.

2) Input the project name, for example, ‘DemoProject’ and choose ‘Finish’. (Selecting ‘Next’ should permit you to create an AUT. But for now, we’ll select ‘Finish’ and proceed with AUT creation in Step #2).

3) The Test Suite browser displays the newly formed project.

Step #2 – Define an AUT

A running instance of the application under test (SimpleAdder) must be constituted in Jubula for object mapping and running the test suite.

1) Go to Test > Properties.

2) Choose ‘AUTs’.

3) Input the AUT name (this can be any user-given value. For example, Demo