TestingOps.ai

Design tools · Exported file link

draw.io and TestingOps: test scenarios from your diagrams

Flowcharts and swimlane diagrams are often the only written description of a process. TestingOps reads draw.io files from a link and gives its AI test agents the shapes, lanes and arrows as context.

  • Exported file link
  • Available
Request a demo draw.io: export a diagram to SVG
Connection
Exported file link
Writes back
Nothing, the file is only read
Last checked
7 Nov 2026

In short

draw.io and TestingOps in short

draw.io diagrams reach TestingOps as files: you paste the link of a .drawio file, or of an SVG or PNG export that includes the diagram, from a Git repository, a raw file address or diagrams.net, and TestingOps downloads and reads it.

Each diagram page becomes a knowledge-base document that lists the shapes in reading order under their swimlanes and groups, with labelled arrows as flows.

Agents use those flows and branches as context for scenarios and test cases; no tests or visual checks are generated from the diagram.

There is no draw.io account to connect, and a token is needed only for files in a private GitHub or GitLab repository.

What it does

What it does for your testing

  1. 1

    Swimlanes show who does what

    Input
    Swimlanes, groups and tables with the shapes inside them
    TestingOps
    Lists the shapes in reading order, nested under their lane or group
    Output
    Context for role-by-role steps, for example what the approver does after the requester submits
  2. 2

    Labelled arrows become branches

    Input
    Arrows between shapes, with labels such as "approved" or "rejected"
    TestingOps
    Records each arrow as "A" → "B" with its label
    Output
    Branches a scenario can follow, one per labelled outcome
  3. 3

    A changed file is the only trigger

    Input
    A diagram file kept in a repository or behind another reachable link
    TestingOps
    Downloads the file on each sync and compares its content fingerprint with the previous one
    Output
    Documents are rewritten only when the file itself changed

Step by step

How it works

  1. Add a draw.io connectionCreate a draw.io connection under Integrations → Project tools → Design tools → draw.io. Leave the access token empty for public files; add one only for files in a private GitHub or GitLab repository.
  2. Paste the file linkIn the project's Knowledge Base, add a Design tools source with that connection and paste the link: a GitHub or GitLab file link, a raw file address or a diagrams.net link that points to the file. There is no list to pick from.
  3. TestingOps reads every pageIt accepts .drawio and .xml files, and .drawio.svg and .drawio.png exports that carry a copy of the diagram.
  4. Pages become documentsEach page lists its shapes under their lanes and groups, followed by the labelled arrows, and ends with a link back to the file.
  5. Re-read when the file changesEach sync downloads the file again and leaves it alone when its content is unchanged.

GitHub and GitLab file links are turned into raw file addresses automatically. The GitHub or GitLab integration is not involved: the file is fetched straight from its link.

Connect

Setup

  1. In TestingOps, open Integrations → Project tools → Design tools → draw.io and create the connection; add an access token only for files in a private GitHub or GitLab repository.
  2. Open Knowledge Base, pick the project, select Add source on Design tools, choose the draw.io connection, paste the file link and select Link to RAG.
  3. Select Sync now. Later syncs run automatically and leave unchanged files alone.
  4. For SVG files, export from draw.io with "Include a copy of my diagram"; PNG exports need the same embedded copy.

Documentation: draw.io: export a diagram to SVG

Where you connect it in TestingOps: Integrations → Project tools → Design tools → draw.io

Use cases

Use cases

Test an approval process drawn as swimlanes

Trigger
A business analyst keeps the purchase approval flow as a .drawio file in the project repository
Uses
Lanes per role, decision shapes and labelled arrows
Agent activity
Writes a case for each labelled branch, with steps for the role in each lane
Result
Draft cases that cover the branches the diagram shows
Condition
Only what is drawn is known; rules that are not in the diagram need another source

Use diagrams published as SVG in documentation

Trigger
A team publishes .drawio.svg files in its documentation repository
Uses
The diagram copy embedded in each SVG
Agent activity
Reads each page as context while it plans scenarios
Result
One document per diagram page, from files the team already maintains
Condition
The SVG must be exported with "Include a copy of my diagram"

Scope integration tests from a system diagram

Trigger
A context diagram shows which systems call which
Uses
Shapes for the systems and labelled arrows for the calls
Agent activity
Uses the arrows as the list of interfaces to cover when it plans integration scenarios
Result
A scenario outline for each interface the diagram draws
Condition
Arrow labels are the only detail available; request and response formats need an API source

Capabilities

Capabilities and limits

What is read

  • Every page of a draw.io file: shape labels in reading order, nested under swimlanes, groups and tables
  • Arrows between shapes, with their labels
  • Files: .drawio and .xml, and .drawio.svg or .drawio.png exports that include a copy of the diagram
  • Links: GitHub and GitLab file links, raw file addresses and diagrams.net links that point to such a file

What is produced

One knowledge-base document per diagram page, with the link to the file

Where it can write

Nothing. The file is downloaded and read; it is never changed.

How it connects

A direct download of the file link; for a private GitHub or GitLab file, with the access token saved on the connection

Account and permissions

  • No draw.io account
  • Public files: nothing else
  • Private repository files: a GitHub or GitLab access token that can read the file

Limits

  • Files up to 15 MB and up to 200 pages
  • diagrams.net links that open a file from Google Drive are refused, because they need a Google sign-in
  • SVG and PNG exports without the embedded diagram copy cannot be read
  • Shapes without a label are left out
  • No runnable tests or visual checks are generated from diagrams

Example

Example: how a team uses it

Illustrative scenario, not a customer story.

An insurance team keeps its claim-handling flow as claims.drawio in a GitHub repository, with lanes for customer, adjuster and payments, and arrows labelled "under limit" and "needs review".

After the file link is added, an agent writes one case per labelled branch, with steps for each lane's role. When the analyst edits the file, the next sync rewrites the page that changed.

Frequently asked questions

Do I need a draw.io account?

No. You give TestingOps the link of a diagram file. A token is needed only when the file sits in a private GitHub or GitLab repository.

Which file formats can be read?

.drawio and .xml files, and .drawio.svg or .drawio.png exports that include a copy of the diagram. A plain SVG or PNG image without that copy has no diagram data to read.

Can I link a diagram stored in Google Drive?

Not today. diagrams.net links that open a Google Drive file need a Google sign-in, which TestingOps does not perform. Keep the file in a Git repository or behind another link TestingOps can download.

My process is modelled in BPMN. Should I use draw.io?

A draw.io file is read as a diagram: shapes, lanes and arrows. If the process also exists as a BPMN 2.0 (.bpmn) file, link that file through the BPMN 2.0 file source under Platforms to get start-to-end paths as scenario candidates.

How are changes picked up?

On every sync TestingOps downloads the file and compares its content with the last read. Unchanged files are skipped; when a page changes, its document is replaced, and pages that were removed are retired.

Is the GitHub or GitLab integration required?

No. The file is downloaded straight from the link, and GitHub and GitLab file links are converted to raw file addresses. The access token on the draw.io connection is used only for private repositories.

Next step

Bring one of your process diagrams to a demo and see the scenarios agents plan from its lanes and branches.

Request a demoMore design tools integrations