Quick links: How to test a tool? -> Test Results
Table of Contents generated with DocToc
BPMN 2.0 Test Cases (Models, Diagrams, Serializations) created by the BPMN Model Interchange Working Group (BPMN MIWG) at the OMG. For more information see: http://www.omgwiki.org/bpmn-miwg
If BPMN interchange is important to you:
Everybody is welcome to test BPMN tools and submit results to the working group, not just tools vendors but also end users that have access to a tool.
Here is how you do it:
First download the latest version of the BPMN Model Interchange Test Suite and unpack it.
There is a directory called Reference
, which contains the files needed for testing.
Next to that, there will be multiple folders with test results of other tools.
There are different test procedures that can be performed with the provided reference models depending on the capabilities of the tool. You will find explanations of these procedures below.
Package all result files in a zip file and send it via email to MIWG@trisotech.com. Please use the following template for your email:
Vendor:
Tool name:
Version:
Website:
Tool supports BPMN 2.0:
Tool has BPMN XML import:
Tool has BPMN XML export:
Tool supports BPMN XML roundtrip:
License:
Notes:
Alternatively, you may also fork the repository on GitHub, upload the files using your Web browser and submit test results through a pull request. If you do so, make sure to update the JSON file with the list of tools.
Usually one day after your submission our automated tools should have generated a report that shows findings in your submitted files:
Note: By submitting test results you agree that they will be published under a Creative Commons Attribution 3.0 Unported License.
Available Features | Possible Tests |
---|---|
import only | import, cross |
export only | export |
import & export | import, export, roundtrip, cross |
If the tool under test supports the import of BPMN XML files, you can test that feature using the following procedure:
A.1.0.bpmn
.<test id>-import.<diagramNumber>.png
, e.g. A.1.0-import.1.png
.
You can either do that through an export feature of the tool or by taking a screenshot of the canvas. It needs to be saved in PNG format. The <diagramNumber>
should be counted in the order in which the diagrams appear inside reference XML file.A.1.0.png
.Tool name:
Tool version:
Test case id:
Test procedure: import
Description:
Repeat these steps for all reference models and submit your result files to BPMN MIWG.
If the tool under test supports the export of BPMN XML files, you can test that feature using the following procedure:
A.1.0.png
.<test id>-export.png
, e.g. A.1.0-export.png
.
You can either do that through an export feature of the tool or by taking a screenshot of the canvas. It needs to be saved in PNG format.<test id>-export.bpmn
, e.g. A.1.0-export.bpmn
.A.1.0.bpmn
.Tool name:
Tool version:
Test case id:
Test procedure: export
Description:
Repeat these steps for all reference models and submit your test results to BPMN MIWG.
If the tool under test supports the import and export of BPMN XML files, you can test a roundtrip using the following procedure:
A.1.0.bpmn
.<test id>-import.<diagramNumber>.png
, e.g. A.1.0-import.1.png
.
You can either do that through an export feature of the tool or by taking a screenshot of the canvas. It needs to be saved in PNG format. The <diagramNumber>
should be counted in the order in which the diagrams appear inside reference XML file.<test id>-roundtrip.bpmn
, e.g. A.1.0-roundtrip.bpmn
.A.1.0.bpmn
.Tool name:
Tool version:
Test case id:
Test procedure: roundtrip
Description:
Repeat these steps for all reference models and submit your test results to BPMN MIWG.
If the tool under test supports at least the import of BPMN XML files, you may optionally do a cross test with the roundtrip and export test results submitted by other tools:
A.1.0-roundtrip.bpmn
or A.1.0-export.bpmn
from the folder of the other tool, e.g. camunda Modeler 2.4.0
.<name of imported file>-import.<diagramNumber>.png
, e.g. A.1.0-roundtrip-import.1.png
or A.1.0-export-import.1.png
.
You can either do that through an export feature of the tool or by taking a screenshot of the canvas. It needs to be saved in PNG format. The <diagramNumber>
should be counted in the order in which the diagrams appear inside reference XML file.
Store the result file in a folder with the name and version of the other tool that exported the file, e.g. camunda Modeler 2.4.0
.<name of imported file>-roundtrip.bpmn
, e.g. A.1.0-roundtrip-roundtrip.bpmn
or A.1.0-export-roundtrip.bpmn
.
Store the result file in a folder with the name and version of the other tool that exported the file, e.g. camunda Modeler 2.4.0
.A.1.0.bpmn
, and/or the imported file, e.g. A.1.0-roundtrip.bpmn
or A.1.0-export.bpmn
.Tool name:
Tool version:
Name of imported file:
Tool name of imported file:
Tool version of imported file:
Test procedure: cross
Description:
Repeat these steps for all roundtrip and export test results of all tools and submit your test results to BPMN MIWG.
If the tool does neither support import nor export of BPMN XML files you can not perform the tests described above. However, if the tool supports other model interchange formats, we are still interested to record this information:
Tool name:
Tool version:
Description:
The BPMN XML format is not supported.
Model Interchange is only possible in the `XPDL` format.
The name and version of a tool must be the same across folder name, issue label name, and entry in JSON file tools-tested-by-miwg.json.
For example:
{
"vendor": "IBM",
"tool": "IBM Process Designer",
"version": "8.0.1",
...
}
The top level is either a vendor or the submitted reference.
The second level holds the individual test case files in the form <identifier>-<test type>.filetype
.
The vendor who provided the reference model for a test case will be identified in the file test-case-structure.json
.
test-case-structure.json
to find vendor who provided this referenceDepict Abstract Elements on a single Sequential Flow
Depict divergence and convergence of flows with unmarked Gateways
Depict divergence and convergence of flows with unmarked Gateways using different type of sequence flows
Depict Exception Flows associated to boundary attachments
Depict graphical elements contained in expanded Sub-Processes, Lanes and Pools
Vertical Modeling Direction
Descriptive Sub-Class (Conformance class coverage) - Validate that all the elements prescribed for the Descriptive Conformance Sub-Class in the BPMN 2.0 Specification are present.
Analytic Sub-Class (Conformance class coverage) - Validate that all the elements prescribed for the Analytic Conformance Sub-Class in the BPMN 2.0 Specification are present.
Invoice Collaboration - Executable process containing multiple extension elements and attributes (derived from 2013 Demo in Berlin)
Invoice Collaboration - Process from 2015 Execution Demo in Berlin that can be executed in Camunda BPM, OmnyLink and W4 BPMN+
Buying at Amazon Collaboration - Collaboration from 2015 Diagram Interchange Demo in Berlin
Fridge Repair Service - Process with hidden BPMN attributes and elements from 2015 Hidden Attribute Demo in Berlin
New Employee Onboarding - Process with signal and message events and multiple diagrams, from 2017 Demo in Brussels
New Bank Customer - Process with data objects and stores and their hidden attributes from 2018 Demo in Seattle
Travel Booking - Process with data input/outputs and event sub-process from 2019 Demo in Amsterdam
Advertise a job vacancy - Process with data inputs and data object connected to sequence flow from 2020 Virtual Demo
Vacation Request - Process with color and internationalization from 2022 Demo
Vacation Request - Process with automation extensions from 2022 Demo
This work is licensed under a Creative Commons Attribution 3.0 Unported License.