The test functionality allows to test the model in the automation environment as a service.

If the test functionality is grayed out, it is most likely that your model is not executable. This is most likely because your elements do not define decision logic.

Test Mode

When shifting in test mode, the model will become read-only and will display a left panel with the test controls and a test bar at the top.

  • The square button stops the currently running service.

  • The play-pause button continue the service at the next step.

  • The x button closes the test mode.

While in test mode, the test panel on the left will contextually the following information


This is an option to select which decision service should be evaluated. We can also select Decision or Business Knowledge Model to run a single decision logic. And we can also select the Whole model to run all the model which includes all the imported models.

Depending on the selection, the inputs of the service / Decision / Business Knowledge Model are shown on the Form. When we click on a Decision service, the associated page or shape will be opened or selected. When we select a Decision or Business Knowledge Model, the decision logic page associated will be opened.

When we run the Test for the first time, if the opening tab is a diagram, the decision service related to this diagram is selected on this option. If we are on a decision logic tab, the Decision or Business Knowledge Model of this logic is on the selection by default. We can switch the selection at any time to run another service.

Mode Description


User input required for the current element. There are 3 modes for providing user inputs that can be switched using the icons:


A web form when you type the inputs manually. See the Form section below for more information on the different widgets that compose the form.


An input to select or drop a file to be used as input for the service. The service accepts JSON, XML or Excel files. A template can be downloaded to have the expected format for each type of file. Note that the Excel file support is limited to models that do not contain collections as input.

Test case

A selector that allows to load a previously saved test case inside the HTML mode to edit and/or submit.

Test Data (Require Automation)

A web form that allows to persist each inputs as test data to be reused across models. Test data is shared across all users and keyed using the data type of the input. Therefore two models using a data type tPerson can be started using the same test data. This form also allows to manage the full life cycle of test data. See the Form section below for more information on the different widgets that allows to define the test data


The trace view displays the executed service nodes. It is possible to click on them to obtain the detail of the inputs and outputs of each nodes. The inputs and outputs of the nodes are presented in a user readable format and also raw as the events emitted for the ServiceNodeStarted/ServiceNodeFinished events.

The trace view presents the history of everything that already occurred in the service and when the service is stopped waiting for an external trigger (user task, message, breakpoint, …​), the trace presents required data to input to continue the service.


This tab presents all the service variables. It is possible to modify them and update them using the Update button when the service is still executing.


When the service completes, the output results are presented. From there, you can save the results as a Test case or download the results as a JSON file.


Display the configured breakpoints and allows to check an option to skip all breakpoints.

When the service progresses, the taken path is highlighted in green.


When hovering on the diagram, breakpoints overlay become visible when you mouse-over a supported node. Clicking on these icons will set/clear breakpoints. The following breakpoints can be set:

  • Before a decision: Stop before executing the decision logic of a decision

  • After a decision: Stop after executing the decision logic on a decision

  • Before an invokable (BKM, decision service): Stop before executing the decision logic of the invokable

  • After an invokable (BKM, decision service): Stop after executing the decision logic of the invokable

Breakpoints can be added/removed while the test session is active.

In modeling mode, it is also possible to display the breakpoints overlays using the overlay right side panel.


The test interface presents in different context a form to input data.

Each input has an associated widget that allows you to enter the data. These widgets follow the data type defined for the input in the model. Note that if no data is entered in a field, the value is considered null except for Text inputs where it is considered an empty string. A null value can also be entered for a Text input by pressing the delete or backspace key.

Structures and collections will also have a caret to the left to their name to allow to expand or collapse them. They also have a null icon that will either be grayed out (the value is not null) or dark (the value is null). Clicking on the null icon nulls out the value of a structure or collection.

The collection input also offers an excel button to import and export the data in the collection as an Microsoft Excel file. Please note that complex data structure will not all be possible to represent in an Excel file.

Data type validation

By default, test is done using the "None" Data type validation. You may change that by going to the Preferences panel.

test 2