[uss_qualifier/scenarios/data_exchange_validation] Fix test step expect_no_interuss_post_interactions #1238
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ct_no_interuss_post_interactions
BenjaminPelletier
approved these changes
Oct 23, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This was initially to fix the incorrect call to
e.stacktracewhen the check fails.Then I realized when we retrieve those interactions from the mock USS, we may actually have invalid ones, e.g. when another test has injected some invalid values. As such I removed the attempt at validating the
PutOperationalIntentDetailsParametersand only retrieve the operational intent ID treating the request as a raw JSON.And this also aligns the severity of the Mock USS interaction can be parsed check with its implementation, as we expect to continue the processing of requests if the parsing fail, or rather now when the request does have an operational intent ID.