TestingOps.ai

Process models (BPMN) · Native connection

ADONIS and TestingOps: test scenarios from your BPMN process repository

In ADONIS, BPMN 2.0 business process diagrams sit next to the rest of the process landscape. TestingOps finds those diagrams in your repositories, exports them as BPMN and lists the paths through each one as scenario candidates.

  • Native connection
  • Available
Request a demo
Connection
Native connection
Writes back
Nothing, it only reads
Last checked
7 Nov 2026

In short

ADONIS and TestingOps in short

The ADONIS connection signs in to the ADONIS REST API with a standard user over Basic authentication, finds BPMN 2.0 business process diagrams with the Search API in every repository the user can see or in one repository you name, and exports a linked model as BPMN DI XML.

Each process in the export becomes a knowledge-base document with steps, decisions, exceptions and bounded paths from start to end, marked as scenario candidates for review.

Because ADONIS's REST API returns no model revision, the model is downloaded on every sync and written to the knowledge base only when its content changed; other ADONIS model types are not read.

What it does

What it does for your testing

  1. 1

    Repository search finds the BPMN models

    Input
    Repositories the user can see (up to 20) or one repository ID
    TestingOps
    Searches for BPMN 2.0 business process diagrams and lists them with their group path, up to 500
    Output
    A pick list of the BPMN models in your process landscape
  2. 2

    Diagrams become numbered paths

    Input
    The BPMN DI export of a linked model
    TestingOps
    Parses steps, lanes, gateways and events and numbers the paths from start to end
    Output
    Scenario candidates for review
  3. 3

    Content hashes decide what is rewritten

    Input
    The export downloaded on each sync
    TestingOps
    Compares its hash with the last one
    Output
    A knowledge-base document that changes only when the model did

Step by step

How it works

  1. Prepare a userUse a standard ADONIS user with a password, and make sure Basic authentication is enabled for the REST API. Technical users and identity-provider logins cannot be used.
  2. ConnectUnder Integrations → Platforms → Process models (BPMN 2.0) → ADONIS, enter the web client address (for example https://adonis.example.com/ADONIS), the user name and password, and optionally a repository ID.
  3. Link a modelTest connection lists the BPMN models. In the project's Knowledge tab, add a source under Process models (BPMN 2.0): pick a model or paste its ADONIS link or its model ID@repository ID.
  4. SyncEach sync exports the model as BPMN DI and rewrites the process document only when the export changed.
  5. Review the candidatesAgents and testers read the process document from the knowledge base and write scenarios from the candidates they keep.

Connect

Setup

  1. In ADONIS, make sure Basic authentication is enabled for the REST API and pick a standard user that can read the BPMN models.
  2. In TestingOps, open Integrations → Platforms → Process models (BPMN 2.0) → ADONIS and enter the web client address, the user name, the password and, optionally, the repository ID. Select Test connection, then Save.
  3. In the project's Knowledge tab, select Add source under Process models (BPMN 2.0) and pick a model, or paste its link or model ID@repository ID.
  4. Select Sync now. Automatic syncs follow and rewrite the document only when the model changed.
Where you connect it in TestingOps: Integrations → Platforms → Process models (BPMN 2.0) → ADONIS

Use cases

Use cases

Test the processes behind a compliance requirement

Trigger
A team links the BPMN models a regulated process depends on
Uses
Steps with lanes and documentation, and the paths through each gateway
Agent activity
Writes scenarios per path and notes the role responsible at each step
Result
Scenarios that trace back to the ADONIS model
Condition
Only BPMN 2.0 business process diagrams are read; other ADONIS model types are not

Pick models across repositories

Trigger
Processes are spread across several ADONIS repositories
Uses
The search across up to 20 visible repositories
Agent activity
A tester picks the models to link
Result
Process documents from several repositories in one project
Condition
Set a repository ID on the connection to list one repository only

Follow model updates

Trigger
A modeler changes a linked diagram
Uses
The export's hash on the next sync
Agent activity
Works from the updated paths when revising scenarios
Result
Candidates that match the current diagram
Condition
The model is downloaded on every sync, even when it did not change

Capabilities

Capabilities and limits

What is read

  • BPMN 2.0 business process diagram models found with the Search API (name, group path, repository) in up to 20 repositories and 500 models, exported as BPMN DI XML
  • Per process (named after its pool when there is one): start, end, intermediate and boundary events with their type, such as timer, error or message; tasks, including user, service, script, business rule, manual, send and receive tasks; call activities, without following the called process; sub-processes, ad-hoc sub-processes and transactions with their inner steps; exclusive, inclusive, parallel, event-based and complex gateways; sequence flows with their name or condition; lanes; documentation; inline form fields such as camunda:formField
  • Not parsed: message flows between pools, data objects and data stores, text annotations, the DMN tables behind business rule tasks, linked forms, and timer or expression details beyond the event type

What is produced

One knowledge-base document per process: steps with kind, lane and documentation, decisions with their outcomes, exceptions from boundary events, form fields, and numbered paths from start to end marked as test scenario candidates

Where it can write

Nothing in ADONIS: models are only searched and exported

How it connects

ADONIS REST API (Search API 4.0, with 3.0 as fallback, and the Model Data API) with Basic authentication

Account and permissions

  • A standard ADONIS user name and password, with Basic authentication enabled for the REST API
  • Technical users and identity-provider logins cannot be used
  • Optionally, a repository ID to list one repository

Limits

  • Paths are bounded: at most 30 per process and 60 steps per path; a loop is followed once and the path ends with "back to" the step it returns to; each outgoing branch of a gateway, parallel and inclusive ones included, becomes its own path, so branches are not combined
  • Paths are candidates for review: no TestingOps scenarios or cases are created from them automatically
  • No model revision is available, so each sync downloads the model; the document is rewritten only when the export changed
  • Other ADONIS model types are not read
  • Up to 12,000 characters per process section and 200 processes per model; files and exports up to 15 MB

Example

Example: how a team uses it

Illustrative scenario, not a customer story.

A bank's process office keeps its account-opening process in ADONIS as a BPMN 2.0 diagram with lanes for Branch, Back office and Compliance. The export shows an exclusive gateway "Identity verified?" and an error boundary event on the credit bureau check.

The document lists the approval path, the manual verification path and the bureau failure path. An agent writes a scenario for each and marks the steps that need a Compliance test user.

Frequently asked questions

Which ADONIS user can TestingOps use?

A standard ADONIS user with a password, over Basic authentication, which must be enabled for the REST API. Technical users and identity-provider logins cannot be used.

Which ADONIS models are read?

Only BPMN 2.0 business process diagrams. TestingOps finds them with the Search API and exports them as BPMN DI XML; other model types are not read.

Why is the model downloaded on every sync?

ADONIS's REST API does not return a revision or last-change date for the model, so TestingOps downloads the export and compares its hash. The knowledge base is rewritten only when the model changed.

Can we limit it to one repository?

Yes. Enter a repository ID on the connection. Left empty, TestingOps lists the BPMN models of up to 20 repositories the user can see.

Are scenarios created in TestingOps automatically?

No. The paths are listed as candidates in the process document, up to 30 per process. Agents or testers write scenarios and cases from the ones you keep.

Next step

See an ADONIS process as scenario candidates: request a demo and bring one BPMN model from your repository.

Request a demoMore process models integrations