Change word length due to error on mechanical-markdown

[mcruzdev]

Description

This pull request adjust the mechanical-markdown scenario due to an issue that lives on mechanical-markdown lib.

Closes #1266

Issue reference

We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.

Please reference the issue this PR will close: #[issue number]

Checklist

Please make sure you've completed the relevant tasks for this PR, out of the following list:

• Code compiles correctly
• Created/updated tests
• Extended the documentation

[mcruzdev]

@cicoyle @salaboy could you take a look?

[salaboy]

@mcruzdev looking at the code changes.. I am confused on how this fixes the flaky test.. I remember seeing a comment somewhere where it was explained.. but I cannot find it now.

[salaboy]

Ok found it.. #1266 (comment)
but if the issue is with the order, then there is a bug with match_order: none on mechanical markdown right?

I still don't understand how changing the word count fixes the issue. @mcruzdev maybe you can share the sequence of things that happened and what are the expected values to make it easier to review.

[salaboy]

Ok for context, we are looking at the execution of this test: https://github.com/dapr/java-sdk/blob/3e54d98cf056162dc3bc237f337a359bffa8be18/examples/src/main/java/io/dapr/examples/workflows/README.md#fan-outfan-in-pattern

This test executes five activities in parallel. Each activity counts the words (tokens), and then the workflow sums up all the results.

The issue seems to be here:

java-sdk/examples/src/main/java/io/dapr/examples/workflows/README.md

Line 246 in 3e54d98

expected_stdout_lines:

where only 4 of 5 activities are expected.. hence depending on the order one might be missed, or removed as @mcruzdev mentioned. There are no five checks for all the activity results, I think if we add another check (and make sure that the checks are not in order) we should get a more consistent behavior.

Ok.. so changing the word count makes sense because of this: dapr/mechanical-markdown#37

[salaboy]

Ok.. now I think I understand the full context.. I would recommend to change the output
Right now - 'Activity returned: 2' and - 'Activity returned: 21' are clashing. We can quickly fix that by changing the output format.

For example.. we can just add a period at the end and match with the period, for example:

'Activity returned: 2.'
'Activity returned: 21.'

Those two will not clash when compared by mechanical markdown right? @mcruzdev
This change will keep it simple and will not change the input text for the test.

Does this make sense?

[mcruzdev]

Yes, it makes sense 😅

[cicoyle]

Thank you for looking into this!