TestingOps.ai

Process models (BPMN) · Native connection · Exported file link

Flowable and TestingOps: test scenarios from deployed BPMN processes

With Flowable, the process that matters for testing is the one deployed to the engine. TestingOps reads the latest deployed version of a process definition and lists the paths through it as scenario candidates.

  • Native connection
  • Exported file link
  • Available
Request a demo Flowable REST API documentation
Connection
Native connection, Exported file link
Writes back
Nothing, it only reads
Last checked
7 Nov 2026

In short

Flowable and TestingOps in short

The Flowable connection reads the Flowable REST API, at …/flowable-rest/service for open source Flowable or …/process-api for Flowable Work and Engage, with Basic authentication or a bearer token, and takes the BPMN XML of each definition's latest deployed version; a .bpmn or .bpmn20.xml file link works too.

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

A definition is read again only after a new deployment changes its ID; CMMN and DMN models are not read, and nothing is deployed or started.

What it does

What it does for your testing

  1. 1

    The deployed version becomes the reference

    Input
    The latest deployed version of a process definition, tenant aware
    TestingOps
    Reads its BPMN XML from the engine
    Output
    Scenarios based on what actually runs, not on a draft
  2. 2

    Conditions become test data

    Input
    Sequence flows with a conditionExpression, for example ${amount > 1000}
    TestingOps
    Shows the condition in brackets on the path it starts
    Output
    Candidates that state the data each branch needs
  3. 3

    New deployments trigger a re-read

    Input
    The process definition ID, which changes with each deployment
    TestingOps
    Downloads the XML only when the ID changed
    Output
    Candidates that follow your deployments

Step by step

How it works

  1. Prepare a REST userUse a Flowable user with the access-rest-api privilege and its password, or a bearer token in the password field with no user name.
  2. ConnectUnder Integrations → Platforms → Process models (BPMN 2.0) → Flowable, enter the REST API address (for example https://flowable.example.com/flowable-rest/service), the user name and the password.
  3. Link a definition or a fileIn the project's Knowledge tab, add a source under Process models (BPMN 2.0): pick a definition, or paste a definition key (key or key@tenant), a Flowable link that shows the definition, or a .bpmn file link.
  4. SyncSync now reads the BPMN XML of the latest version; automatic syncs follow and skip a definition whose ID did not change.
  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 Flowable, give a user the access-rest-api privilege, or prepare a bearer token.
  2. In TestingOps, open Integrations → Platforms → Process models (BPMN 2.0) → Flowable and enter the REST API address, the user name and the password (or only the token in the password field). Select Test connection, then Save.
  3. In the project's Knowledge tab, select Add source under Process models (BPMN 2.0) and pick a definition, or paste a key, key@tenant, a Flowable link or a .bpmn file link.
  4. Select Sync now. Automatic syncs read a definition again after each new deployment.

Documentation: Flowable REST API documentation

Where you connect it in TestingOps: Integrations → Platforms → Process models (BPMN 2.0) → Flowable

Use cases

Use cases

Test a process before promoting a deployment

Trigger
A new version of a process definition is deployed to a test engine
Uses
The latest version's BPMN XML on the next sync
Agent activity
Writes or revises scenarios for the paths of the new version
Result
Scenarios that match the deployed definition
Condition
Older versions of the definition are not read

Keep tenants apart in a shared engine

Trigger
A multi-tenant engine with the same key in several tenants
Uses
A key@tenant link
Agent activity
Works only from that tenant's definition
Result
Scenarios for the tenant you test
Condition
Use one link per tenant

Read a model that is not deployed yet

Trigger
A process is still in a Git repository as a .bpmn20.xml file
Uses
A file link on the Flowable connection
Agent activity
Works from the file's paths
Result
Candidates before the deployment exists
Condition
File links on the Flowable connection are fetched without a token; private files need the BPMN 2.0 file connection

Capabilities

Capabilities and limits

What is read

  • Latest deployed process definitions (name, version, tenant), up to 500 listed, and the BPMN XML of the latest version
  • A .bpmn or .bpmn20.xml file link
  • 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 Flowable: definitions are only listed and read; no deployment, process start or task action

How it connects

Flowable REST API (…/flowable-rest/service, or …/process-api for Flowable Work and Engage) with Basic authentication or a bearer token

Account and permissions

  • A user with the access-rest-api privilege and its password
  • Or a bearer token in the password field, with no user name

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
  • CMMN case models and DMN decision tables are not read
  • File links on the Flowable connection cannot carry a token
  • 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 team runs its expense approval process on Flowable. After linking the definition key expenseApproval, the document lists a user task Manager review, an exclusive gateway with the conditions ${amount <= 500} and ${amount > 500}, and a second approval for larger amounts.

An agent writes scenarios for a small expense, a large expense with both approvals and a rejection at each step. When the team deploys a version with a new limit, the next sync reads the new definition and the conditions in the document change with it.

Frequently asked questions

Which Flowable editions work?

Open source Flowable through …/flowable-rest/service, and Flowable Work or Engage through …/process-api. TestingOps reads BPMN process definitions from either.

Does TestingOps read CMMN or DMN models?

No. Only BPMN process definitions are read. CMMN case models and DMN decision tables are not, and a business rule task appears as one step without the rules behind it.

Which version of a definition is read?

The latest deployed version. Each deployment gives the definition a new ID, and TestingOps downloads the XML again only when that ID changed.

Can we use a process that is only in Git?

Yes. Paste a .bpmn or .bpmn20.xml file link on the Flowable connection. It is fetched without a token; for a private file, use the BPMN 2.0 file connection.

Does TestingOps start processes or complete tasks in Flowable?

No. It only reads definitions. Test cases written from the candidates run as AI-executed steps against your application on your execution provider.

Next step

See a deployed Flowable process as scenario candidates: request a demo and bring one definition key from a test engine.

Request a demoMore process models integrations