Skip to content

[FEAT] miwg-test-suite: evaluate automation for submission #27

@tbouffard

Description

@tbouffard

We have done the first submission manually: https://github.com/process-analytics/bpmn-visualization-tools/tree/v0.4.0/bpmn-rendering-miwg-test-suite#submission-process
If we want to do frequent submission, automation would help.

Warning

To date (2023-07-02), we only did a single submission which is not merged. Automation is not required until it has been accepted and until we decide if we are going to do frequent submission. Frequency" must be examined to determine whether automation brings advantages over manual processes.
The first submission was rejected: see bpmn-miwg/bpmn-miwg-test-suite#896

First we should update the bpmn-visualization lib frequently in the tool. This could be done automatically on bpmn-visualization release (we already send dispatch_event to the bpmn-visualization-examples and bpmnVisualizationR repository) or using tools/apps like Dependabot/Renovate.
See #35.

We should also be able to generate the screenshots with a single command. In v0.4.0, the dev server must first be run in a process then the screenshots generation can run

Then we could automate the creation of the submission. The creation of the submission will be started on demand but the entire submission process could be automated:

  • retrieve the reference file from the miwg-test-suite repository
  • run the image generation
  • retrieve the version of bpmn-visualization
  • update the json file referencing bpmn-visualization
  • create the Pull Request

Notice that bpmn.io automates submission See for instance

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions