TestingOps.ai

Process models (BPMN) · Exported file link

ARIS and TestingOps: test scenarios from exported BPMN diagrams

ARIS holds many kinds of models, and its BPMN diagrams can be exported as BPMN files. Link those files, and TestingOps lists the paths through each process, with pools and lanes, as test scenario candidates.

  • Exported file link
  • Available
Request a demo
Connection
Exported file link
Writes back
Nothing, the file is only read
Last checked
7 Nov 2026

In short

ARIS and TestingOps in short

TestingOps does not connect to ARIS directly: it reads BPMN files you export from ARIS and link, from GitHub or GitLab or any other https address, either one model at a time from its context menu or many with an ARIS report script that calls startBpmnExport.

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

Only BPMN exports are read, not EPCs or other ARIS model types, and a file is re-read on each sync with its document rewritten only when the file changed.

What it does

What it does for your testing

  1. 1

    Pools and lanes become responsibilities

    Input
    Pools and lanes of the exported BPMN diagram
    TestingOps
    Names the process after its pool and writes the lane next to each step
    Output
    Scenarios that say which role performs each step
  2. 2

    Bulk exports become a process library

    Input
    Many BPMN files exported with a report script
    TestingOps
    Reads each linked file as its own source
    Output
    One process document per model in the project's knowledge base
  3. 3

    Event types become exception paths

    Input
    Boundary and intermediate events with their type
    TestingOps
    Branches paths from the activity and lists the exceptions
    Output
    Candidates for the error and timeout handling in the diagram

Step by step

How it works

  1. Export from ARISOpen the model's context menu and choose Export → Export BPMN diagram as BPMN file. For many models, use an ARIS report script that calls startBpmnExport.
  2. Put the files behind a linkCommit the .bpmn files to a Git repository or place them at an https address TestingOps can reach.
  3. Add the ARIS connectionUnder Integrations → Platforms → Process models (BPMN 2.0) → ARIS, save the connection, with an access token only for private links.
  4. Link each fileIn the project's Knowledge tab, add a source under Process models (BPMN 2.0) for each file and paste its link.
  5. Sync and reviewSync now reads the files, and automatic syncs follow. Agents and testers write scenarios from the candidates they keep.

Connect

Setup

  1. In ARIS, export each BPMN diagram with Export → Export BPMN diagram as BPMN file from the model's context menu, or export many with a report script that calls startBpmnExport.
  2. Commit the .bpmn files to a repository, or publish them at https addresses TestingOps can reach.
  3. In TestingOps, open Integrations → Platforms → Process models (BPMN 2.0) → ARIS and save the connection, with an access token only for private links.
  4. In the project's Knowledge tab, select Add source under Process models (BPMN 2.0), paste each file's link and select Sync now.
Where you connect it in TestingOps: Integrations → Platforms → Process models (BPMN 2.0) → ARIS

Use cases

Use cases

Bring an ARIS process scope into test planning

Trigger
A process office exports the BPMN diagrams of a release scope with a report script
Uses
One linked file per model
Agent activity
Writes scenarios per process from the numbered paths
Result
Scenario drafts for the scope, each tied to its exported model
Condition
Each file is linked separately; there is no folder import

Keep a test baseline in line with the model

Trigger
A modeler re-exports a changed diagram to the same link
Uses
The file's content, compared on each sync
Agent activity
Revises scenarios from the updated paths
Result
Candidates that match the latest export
Condition
Changes reach TestingOps only after a new export replaces the file

Plan role-based test accounts

Trigger
Diagrams with a lane for each organisational unit
Uses
The lane of every step on each path
Agent activity
Lists which role acts at each step of a scenario
Result
A clear list of the test users a scenario needs
Condition
Organisational models outside the BPMN export are not read

Capabilities

Capabilities and limits

What is read

  • BPMN files exported from ARIS, one model per file, fetched from their links: GitHub and GitLab page links become raw file links, other http(s) addresses are fetched as they are, Google Drive links are refused
  • 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: TestingOps only downloads the linked files

How it connects

Links to exported files. There is no live connection to ARIS; changes arrive when a file at a link changes

Account and permissions

  • No ARIS account
  • An access token only for private links; it is sent as a bearer token

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
  • Only BPMN exports: EPCs and other ARIS model types are not read
  • Each exported file is linked separately; files are not uploaded
  • 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 process office exports the BPMN diagrams of its order management scope from ARIS with a report script and commits them to a GitLab repository. The Order cancellation diagram has a pool for Customer service, lanes for Agent and Supervisor, and a gateway that asks whether the refund is above the limit.

After the file is linked, the document lists the direct cancellation, the supervisor approval and the rejected refund. An agent writes scenarios for each path, and the supervisor path notes the test user it needs.

Frequently asked questions

Does TestingOps connect to ARIS directly?

No. It reads BPMN files exported from ARIS from their links. When you export a model again to the same link, the next sync reads the new file.

How do we export many ARIS models at once?

Use an ARIS report script that calls startBpmnExport, then link each exported file. Each file becomes its own source in the project.

Are EPCs read?

No. Only BPMN exports are read. EPCs and other ARIS model types are not part of this connection.

Which BPMN elements shape the scenarios?

Start, end, intermediate and boundary events, tasks, sub-processes, gateways and the names or conditions of sequence flows decide the paths; pools and lanes say who acts. Message flows between pools, data objects and annotations are not parsed.

Can the files stay private?

Yes. Add an access token to the ARIS connection; it is sent as a bearer token when a file is fetched. Google Drive links are refused because they need a Google sign-in.

Next step

See an ARIS diagram as scenario candidates: request a demo and bring one exported BPMN file.

Request a demoMore process models integrations