[uss_qualifier/scenarios/utm/data_exchange_validation] Factor away fragment 'expect_uss_obtained_op_intent_details' #835
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.
Issue #797.
Stacked on top of #833, please consider only last commit.
This creates the test step fragment
expect_uss_obtained_op_intent_details
which is used in the scenario data_exchange_validation, replacing some parts of the scenario that were attempting to do the same with some conditional test steps.With that change we do a single call to the mock USS to retrieve the interaction logs, and from there we are able to determine whether the tested USS has obtained the operational intent details, no matter how. This makes the documentation clearer.
The implementation of the check now validates as well that the status code of the notification or details retrieval is a success (previously a failed call would be considered as valid).