Integrations

This section describes various ways to integrate MBT with other testing tools.

UFT integration

To integrate with UFT One, install and configure the Application Automation Tools plugin. This enables MBT to integrate with UFT One via Jenkins. These steps are described in Set up UFT One integration. Make sure to follow the instructions on integrating via Jenkins.

After setting up the plugin, configure MBT. For details, see Set up MBT.

Back to top

Design integration: working with codeless tests

Functional Test Design enables you to create codeless tests and run them in the cloud. For details on creating codeless tests with FT Design, see Functional Test Design Help Center.

In this workflow, you use Functional Test Design to write test scripts for your units. The test script is saved in FT Design and not in Git. You then schedule and run the tests using Functional Test Execution. For details, see Functional Test Execution.

This integration requires a license for Functional Test Design and Functional Test Execution.

To create codeless test scripts with FT Design:

  1. In an MBT unit, click Open in Design. FT Design opens locally.

  2. Create your codeless test script in FT Design. For details, see Functional Test Design Help Center.

  3. After saving the script in FT Design, click View in Model-Based Unit, or refresh the unit in MBT.

    The testing tool type is automatically defined as FT Design. The repository path is automatically filled with an internal filename, and the automation status is set to Automated. These cannot be changed. If needed, delete the unit.

  4. Schedule and run the tests using Functional Test Execution. Select the test runner called Codeless Runner. For details, see Functional Test Execution.

Tip: You can also perform this process in the opposite direction:

First, create a script in FT Design, then click Associate with > New Codeless Unit. A new unit is created in MBT, in a folder called VEFT Design.

To move the unit to another folder, add the Parent field in the grid view and select a different folder in the MBT repository.

Back to top

BPMN integration

Business Process Model and Notation (BPMN) is a graphical representation for specifying business processes in a business process model.

You can import a BPMN file to inject its model into MBT.

To import a BPMN file:

  1. In the Settings menu, choose Import > Model Items.

  2. Select BPMN, and navigate to the BPMN file.

    Bulk import: For bulk import of multiple BPMN files, zip the files into zip or 7zip format, and then select the zip file for importing. A parent folder is created in the MBT repository representing the zip file, and each BPMN file is imported to a dedicated folder under the parent folder.

  3. Click Import.

    The models are checked for validity.

    • If there are errors, an error report is displayed. At the bottom of the report you can click Export to Excel and save the error report.

      Fix the errors and import again.

    • If there are no errors, the import begins.

Note: If you re-import the same file, new entities are created. Updating is not supported.

Mapping BPMN elements in MBT

During import, the following are created in MBT:

  • A folder is created with the name of the BPMN file, and the date and time of import. This contains the BPMN file as an attachment.

  • A model with the name of the BPMN file is created as the parent model, under the above folder.

  • If your BPMN file contains information on roles, a corresponding input parameter is created in MBT. Each unit is populated with the value of its role, and the role is displayed when hovering over the unit in the model. When you run a test, the data set displays the roles of each unit.

  • If your BPMN file contains parallel gateways, these are converted to a chain of units in MBT.

The following table lists the MBT entities that are created, and their corresponding BPMN elements:

MBT entity BPMN element
Model

Process (ID, name), Subprocess (ID, name), CallActivity (ID, name, calledElement – ID of process for reuse)

Unit

Task (ID, name), UserTask , UntypedTask, SendTask, ReceiveTask, ServiceTask, ScriptTask, BusinessRule Task, ManualTask

Decision Gateway (ID, name, gateway type), Exclusive, Inclusive, Parallel Event
Note

textAnnotation (ID, children with text attribute)

Placeholder Events (ID, name, eventType, eventGatewayType, children except incoming/outgoing attributes), attachedToRef - sourceNode
Start node startEvent (ID, name)
End node endEvent (ID, name)
Edge Incoming/outgoing (ID, name), sequenceFlow

Note: The following elements are ignored during import: Pool, Participant, Collaboration, Message, messageFlow, DataObjects, messageEventDefinition, DataStore.

Back to top