Integration with External Tools

There are several ways to integrate TestOptimal with other systems and tools, allowing you to leverage your investment in the existing test automation tools. These interfaces are:

Cloud Services

You can run your testing on Selenium-based cloud service for cross browser testing and load testing with hundreds or even thousands of virtual users:

Please refer to their website for instruction on how to set up the connection to their service.


You can bring in requirements from external files or ALM systems like Jira and Azure ALM.


ALM.jira.req.query={"jql"\: "project \= @PROJECT@ and (issuetype \= Story or issuetype\=Task or issuetype\=Sub-Task) and status \= 'In Progress'", "fields"\: ["summary", "priority", "updated", "description"]}
  • IDE / Requirement / Parameters:
 { "project": "DEMO" }

Azure ALM

  • IDE / Requirement / Parameters:
 {  "PROJECT": "Demo",
    "QUERY_ID": "a2ae7670-...-ff40d088e533" 


Besides Basic, additional authentications are possible. Below is the list of authentication options:

    • ALM.'xxx'.auth.basic.username
    • ALM.'xxx'.auth.basic.password
  • FORM
    • ALM.'xxx'.auth.form.username
    • ALM.'xxx'.auth.form.password
    • ALM.'xxx'.auth.oauth.consumer.key
    • ALM.'xxx'.auth.oauth.consumer.secret
    • ALM.'xxx'.auth.oauth.access.token
    • ALM.'xxx'.auth.oauth.secret.token
  • OAUTH2
    • ALM.'xxx'
    • ALM.'xxx'.auth.oauth2.signature


Add steps to Jenkins build job to run models using TestOptimal REST APIs.

This feature is only available for V5.0. For v6.0, you would achieve the same with http://localhost:8888/swagger.

  • Check and install HTTP Request plugin installed in your Jenkins
  • Add admin to connect to Runtime Servers
    • select menu Jenkins / Credentials
    • click “(Global)” under “Domain” column
    • fill out form and save
  • open /create build job
  • add a build step with HTTP Request plugin

  • click “Advanced” button and fill out form as follows:

  • click “Save”

Run the job and you should see the output in Job Console Output:

Azure DevOps

Add a step to Azure DevOps to run models remotely using REST APIs.


TestOptimal provides a suite of REST APIs to allow 3rd party tools and applications to communicate with TestOptimal server.

You can use these REST APIs to access start and stop model execution, access model artifacts/files as well as perform system functions remotely.

Organization of REST APIs

REST APIs are grouped and organized in these categories (to match Swagger-UI):

  • ALM - ALM source definition and model requirements
  • Agent - TestOptimal Agent APIs: register remote agent and receive agent commands
  • Client - TestOptimal Agent APIs: remote execute model and data set execution
  • Dashboard - Dashboard data: KPI and model execution statistics
  • Demo - REST API used by demo models
  • File - access to model and system files
  • Graph - generate / download graphs for model executions: model graph, coverage graph, traversal graph and test case graph (MSC)
  • Model - access to model artifacts/files
  • Report - Dashboard reports
  • Runtime - start/stop model execution
  • Security - user login
  • Stats - model execution statistics
  • SvrMgr - Server manager functions
  • System - perform system functions
  • web-redirect-controller - internal use

Security and Authorization

Most of the REST APIs are access controlled.

Basic Auth is used to authenticate users. It is highly recommended that you enable SSL if you access TestOptimal server from the internet to prevent your user id/password from being intercepted.

Swagger UI

Swagger UI is provided for your convenience. You can access Swagger UI with the following URL:


If you are prompted to Login screen, go ahead and login and re-launch the above URL in the same browser session again.

Integrate TestOptimal in your java project (Java /IDE Connector)

TestOptimal can be used in your testing project as a maven dependency.


You can build your model using POJO java classes and submit it to TestOptimal server to generate test cases from the model. The test cases are returned back to your java code for your further test case execution.

You can generate test cases for state model and data set (combinatorial testing).

See JavaConnector README for more details.