Closed turing85 closed 2 months ago
@christophd It would be nice if we could produce a 3.x
release with this fix.
it's hard to imagine what's happening currently and what should happen, with just this change being present. please add a test that proves the desired behavior.
it's hard to imagine what's happening currently and what should happen, with just this change being present. please add a test that proves the desired behavior.
This is just a cherry-pick from a commit that is already on main...
hmm, I see. sorry, didn't read the description to the end.
would you mind cherry-pick'ing it upon the updated base?
we're planning to release the backport of https://github.com/citrusframework/citrus/pull/1148 soon. we could easily include this PR as well.
would you mind cherry-pick'ing it upon the updated base?
we're planning to release the backport of #1148 soon. we could easily include this PR as well.
@bbortt here you are.
Reopened and set base back to 3.x
. See https://github.com/citrusframework/citrus/pull/1152#issuecomment-2074444403
I am so sorry @turing85 .. I didn't know what branch @christophd uses and had already done https://github.com/citrusframework/citrus/pull/1148 into support/3.0.0
. totally my bad! thanks for the contribution ❤️
Avoid all test steps to be reported as "TEST STEP 0" for incremental tests
(cherry picked from commit 21aeb4385587cae7a35911a517f41b372189d53d)