Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MI Collection output variable not properly mapped in MI task #1727

Open
martinweiler opened this issue Dec 20, 2024 · 0 comments
Open

MI Collection output variable not properly mapped in MI task #1727

martinweiler opened this issue Dec 20, 2024 · 0 comments
Labels
area:engine Related to the runtime engines area:workflows Related to the general workflow engine

Comments

@martinweiler
Copy link

Add the following assert to the end of IntermediateEventTest.testMultiInstanceLoopCharacteristicsTaskWithOutputCmpCondSequential:

assertThat(((String) instance.variables().getListOut().get(0))).isEqualTo("test");

and the test shows that the variable is not mapped to the collection ouput variable:

expected: "test"
 but was: null

Note: This is also blocking the migration of the testMultiInstanceLoopCharacteristicsTaskWithOutputCompletionCondition2 test as mentioned in apache/incubator-kie-kogito-runtimes#3682

@yesamer yesamer added area:engine Related to the runtime engines area:workflows Related to the general workflow engine labels Jan 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:engine Related to the runtime engines area:workflows Related to the general workflow engine
Projects
None yet
Development

No branches or pull requests

2 participants