DelegateExecution Input of Parallel User Tasks Based On Collection Expression Different
Opened this issue · 2 comments
huangliang992 commented
Environment (Required on creation)
Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket)
like the test in camunda-engine test shows, the test mehtod testParallelUserTasksBasedOnCollectionExpression
in MultiInstanceTest
shows, the input DelegateExecution delegateExecution
in different loops not same as each other.
@Deployment
@Ignore
@Test
public void testParallelUserTasksBasedOnCollectionExpression() {
DelegateEvent.clearEvents();
runtimeService.startProcessInstanceByKey("process",
Variables.createVariables().putValue("myBean", new DelegateBean()));
List<DelegateEvent> recordedEvents = DelegateEvent.getEvents();
assertEquals(2, recordedEvents.size());
assertEquals("miTasks#multiInstanceBody", recordedEvents.get(0).getCurrentActivityId());
assertEquals("miTasks#multiInstanceBody", recordedEvents.get(1).getCurrentActivityId()); // or miTasks
DelegateEvent.clearEvents();
}
reason
in the method prepareScopeExecution
of class ParallelMultiInstanceActivityBehavior
the code line scopeExecution.setActivity(null);
changed the activity of exectution
Steps to reproduce (Required on creation)
run the test mehtod testParallelUserTasksBasedOnCollectionExpression
in MultiInstanceTest
can reproduce the bug
Observed Behavior (Required on creation)
Expected behavior (Required on creation)
Root Cause (Required on prioritization)
Solution Ideas
Hints
Links
Breakdown
Dev2QA handover
- Does this ticket need a QA test and the testing goals are not clear from the description? Add a Dev2QA handover comment
yanavasileva commented
Hi @huangliang992,
Thank you for raising this, I will have a look and get back to you with feedback.
Best,
Yana
yanavasileva commented
might be duplicate of #2082