Is your feature request related to a problem? Please describe.
Currently, the integration of the Polyflow Connector is difficult to impossible to test because the engine itself is so difficult to test and brings so many dependencies. At the same time the connector is not only used in the engine.
For this reason, we want to create our own independent integration test with a reduced Camunda form,
Describe the solution you'd like
Create sample tests for the AssignmentCreateTaskListener in a separate project digiwf-task-itest
Build reduced Camunda engine for the tests, to test the interaction of the connector with the engine.
....
Describe alternatives you've considered.
Connector is only tested via the engine -> In the long run with several engines of different characteristics error-prone and redudant
Is your feature request related to a problem? Please describe.
Currently, the integration of the Polyflow Connector is difficult to impossible to test because the engine itself is so difficult to test and brings so many dependencies. At the same time the connector is not only used in the engine.
For this reason, we want to create our own independent integration test with a reduced Camunda form,
Describe the solution you'd like
Describe alternatives you've considered.
Connector is only tested via the engine -> In the long run with several engines of different characteristics error-prone and redudant
Additional context
https://github.com/it-at-m/digiwf-core/tree/dev/digiwf-task/digiwf-task-itest