TestingOps.ai

Process models (BPMN) · Native connection

IBM Blueworks Live and TestingOps: test scenarios from process blueprints

Blueworks Live blueprints are where business teams document how work flows. TestingOps exports the latest revision of a blueprint as BPMN 2.0 and turns the paths through it into scenario candidates for testers and agents.

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

In short

IBM Blueworks Live and TestingOps in short

The IBM Blueworks Live connection uses a Service ID with the Artifact Reporting category, acting on behalf of a user, or a User Service ID; it lists active process blueprints and exports the latest revision of a linked blueprint as a single BPMN 2.0 file.

The export goes through the same BPMN 2.0 parser as the other process connections, so each process becomes a knowledge-base document with steps, decisions, exceptions and bounded paths from start to end, marked as scenario candidates.

A blueprint is exported again only when its revision or last change differs from the last sync, and nothing in Blueworks Live is changed.

What it does

What it does for your testing

  1. 1

    Documented processes become test input

    Input
    Active process blueprints with their space name
    TestingOps
    Lists them newest first, up to 500, for linking to a project
    Output
    Scenarios based on the process the business documented instead of a separate test model
  2. 2

    The diagram becomes numbered paths

    Input
    The BPMN 2.0 export of the blueprint's latest revision
    TestingOps
    Parses steps, lanes, gateways and boundary events and numbers the paths from start to end
    Output
    A bounded list of scenario candidates for review
  3. 3

    New revisions are picked up

    Input
    The blueprint's tip revision and last change
    TestingOps
    Exports again only when they changed since the last sync
    Output
    Candidates that match the latest revision, without downloading unchanged blueprints

Step by step

How it works

  1. Create a Service IDIn Blueworks Live, create a Service ID with the Artifact Reporting category, or a User Service ID. A Service ID acts on behalf of a user who has editor access to the processes.
  2. ConnectUnder Integrations → Platforms → Process models (BPMN 2.0) → IBM Blueworks Live, enter the client ID and secret and, for a Service ID, the on-behalf-of user e-mail. Leave the e-mail empty for a User Service ID.
  3. Link a blueprintIn the project's Knowledge tab, add a source under Process models (BPMN 2.0): pick a blueprint or paste its Blueworks Live link or process ID.
  4. SyncTestingOps checks the blueprint's revision, exports the latest one as a single-file BPMN 2.0 export and parses it; automatic syncs follow.
  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 Blueworks Live, create a Service ID with the Artifact Reporting category (or a User Service ID) and copy its client ID and secret.
  2. In TestingOps, open Integrations → Platforms → Process models (BPMN 2.0) → IBM Blueworks Live and enter the client ID, the client secret and, for a Service ID, the on-behalf-of user e-mail. Select Test connection, then Save.
  3. In the project's Knowledge tab, select Add source under Process models (BPMN 2.0) and pick a blueprint, or paste its link or process ID.
  4. Select Sync now. Automatic syncs export a blueprint again only after a new revision.
Where you connect it in TestingOps: Integrations → Platforms → Process models (BPMN 2.0) → IBM Blueworks Live

Use cases

Use cases

Turn a documented onboarding process into scenarios

Trigger
An operations team links its employee onboarding blueprint
Uses
Steps, lanes, gateways and paths of the exported BPMN
Agent activity
Writes a scenario per path with the role that acts at each step
Result
Scenarios that follow the process the business documented
Condition
Blueprint content outside the BPMN export is not read

Retest when a blueprint is revised

Trigger
A new revision of the blueprint is saved
Uses
The new export on the next sync
Agent activity
Searches the existing scenarios before writing scenarios for new or changed paths
Result
Scenarios for what the revision added
Condition
No automatic analysis of which existing cases a revision breaks

Cover exception handling

Trigger
A blueprint whose export has timer or error events
Uses
The exceptions listed per activity
Agent activity
Proposes scenarios for timeouts and failures
Result
Exception scenarios next to the main flow
Condition
Timer durations are not parsed, only the event type

Capabilities

Capabilities and limits

What is read

  • Active process blueprints (newest first, with space name, up to 500), their revision (tip and last change) and the latest revision exported as a single-file BPMN 2.0 export
  • 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 Blueworks Live: blueprints are only listed and exported

How it connects

Blueworks Live API with the OAuth 2.0 client credentials of a Service ID, sent on behalf of a user, or of a User Service ID

Account and permissions

  • A Service ID with the Artifact Reporting category and the e-mail of a user with editor access to the processes, or a User Service ID
  • The account's API rate limits apply; a rate-limited sync is retried on the next sync

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
  • A blueprint without a revision cannot be exported
  • Downloads up to 15 MB and unpacked exports up to 60 MB
  • Content of the blueprint that is not in its BPMN 2.0 export is 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 shared services team links its Vendor invoice exception blueprint. The export shows lanes for Requester, AP clerk and Manager, a gateway "Price matches purchase order?" and a timer boundary event on Manager approval.

The document lists four candidates, including the escalation when the manager does not respond. An agent drafts scenarios for the mismatch and escalation paths, and the team reviews them with the process owner.

Frequently asked questions

Which Blueworks Live credentials are needed?

A Service ID with the Artifact Reporting category plus the e-mail of the user it acts for, who needs editor access to the processes, or a User Service ID with the e-mail left empty. The client ID and secret are exchanged for a short-lived token.

Which part of a blueprint is read?

The BPMN 2.0 export of its latest revision: events, tasks, gateways, flows, lanes and documentation in the export. Content that exists only in Blueworks Live and not in the export is not read.

Why can a blueprint not be exported?

A process without a revision cannot be exported. Save a revision in Blueworks Live, then sync again.

Does TestingOps change anything in Blueworks Live?

No. It lists blueprints, checks revisions and downloads exports. It does not create, edit or comment on blueprints.

How large can a blueprint be?

The download may be up to 15 MB and the unpacked export up to 60 MB. In the knowledge base, each process section holds up to 12,000 characters and up to 30 paths.

Next step

See a blueprint as scenario candidates: request a demo and bring one Blueworks Live process.

Request a demoMore process models integrations