Incorrect Order Handling in expected_stdout_lines Matching Logic

Open mcruzdev opened this issue 9 months ago • 2 comments

Given an step:

name: Run Chaining Pattern workflow
match_order: none
output_match_mode: substring
expected_stdout_lines:
  - 'Activity returned: 2'
  - 'Activity returned: 9'
  - 'Activity returned: 21'
  - 'Activity returned: 17'
  - 'Workflow finished with result: 60'

The verification executes in the expected_stdout_lines in order, then the first line to be verified is Activity returned: 2.

If the output shows first Activity returned: 21 the first line (Activity returned: 2) will be matched and the following line will be removed.

Mar 24 '25 16:03 mcruzdev

oh I see haha.. so - 'Activity returned: 2' and - 'Activity returned: 21' are clashing..

Mar 25 '25 08:03 salaboy

While I see why this can be a problem, I don't think is an issue with mechanical markdown and more with the test output and the strings that we are matching..

Mar 25 '25 08:03 salaboy