Details
-
Task
-
Resolution: Unresolved
-
L3 - Default
-
None
-
None
-
Not defined
Description
Context:
While implementing another ticket, we noticed that the IT test cases which check that userTask and flownode report evaluations work with processes with multiInstanceBody do not necessarily hold much value because during setup, they usually apply the same changes to all instances of the given flownode which means the result of the report evaluation would not differ even if the report did not take into account the additional instances.
Example:
FlowNodeDurationByFlowNodeReportEvaluationIT.processDefinitionContainsMultiInstanceBody
After creating the multi instance process, this test then adjust the duration of all flownode instances in this process. Then, it asserts that the report result has the correct flownode count and the correct average duration. Because all flownode instances have the same duration, the report result will not differ between a "normal" and a multi instance process. The flownode count will also not differ as it counts flownodes, not flownode instances.
Instead, it would be more useful to give both flownode instances a different duration as this will affect the report result.
AT:
- multiInstanceBody process IT are adjusted so that the report result differs depending on whether the evaluation takes all flownode instances into account