ISSUE-623 : Execute specified previous steps while retrying a given step( for scenarios where current step is dependent on previous steps, such as auth) #627
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Branch
#ADD LINK TO THE PR BRANCH
fixes #623
Motivation and Context
The idea here is that instead of maintaining a List for ScenarioExecutionState, we will maintain a LInkedHashMap of StepExecutionState. This will make it easier to mutate ScenarioExecutionState in complex retry scenarios where previously successfully executed steps need to be re-executed (such as in the
withSteps
feature.We can now run retries with previously executed steps like so:
This will run the steps mentioned in
withSteps
in the order specified before retrying the step on failure.Checklist:
Unit tests added
Integration tests added
Test names are meaningful
Feature manually tested
Branch build passed
No 'package.*' in the imports
Relevant Wiki page updated with clear instruction for the end user
Http test added to
http-testing
module(if applicable) ?Kafka test added to
kafka-testing
module(if applicable) ?