Test BPMN Standard coverage with BPMN MIWG Test Suite

Problem you would like to solve

Goal

Run our new Operaton BPMN Modeler against the BPMN MIWG Test Suite and track our results, so we can claim verified BPMN 2.0 interchange compliance.

What it is

The BPMN Model Interchange Working Group (MIWG) is an OMG community that maintains a standardized set of BPMN 2.0 reference models (XML + reference diagrams, cases A.1.0…C.8.1,
from basic elements to executable processes). It's the de-facto industry benchmark for "can tool X exchange BPMN with tool Y without data/layout loss."

Proposed solution

How it's run

Per reference model, three checks:

1. Import – load the reference XML, render it, compare against the reference diagram (PNG).
2. Export – recreate the diagram, export XML, diff against the reference XML.
3. Round-trip – import → export and verify the model survives unchanged.
   (Optional: cross-test importing other tools' exports.)

We'd start by wiring the reference XML files into an automated import/round-trip test in the modeler's test pipeline; export/visual checks can follow.

Why it matters

• No vendor lock-in / real interoperability – users can move models between tools (Camunda, Signavio, etc.) and our modeler.
• Market transparency & credibility – MIWG publishes vendor results; passing is a recognized quality signal.
• Regression safety – catches serialization/layout drift in our BPMN read/write code early.

Alternatives considered

None.

Additional context

No response

Start by locating the modeler’s test pipeline and the BPMN read/write code, then review the BPMN MIWG Test Suite reference XML files and diagrams. Begin with automated import and round-trip coverage; done means the reference models are wired into tests and model survival is verified, with export and visual checks left for later.