Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[uss_qualifier/scenarios/utm/data_exchange_validation] Factor away fragment 'expect_uss_obtained_op_intent_details' #835

Merged
merged 1 commit into from
Nov 12, 2024

Conversation

mickmis
Copy link
Contributor

@mickmis mickmis commented Oct 31, 2024

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).

…agment 'expect_uss_obtained_op_intent_details
@mickmis mickmis force-pushed the 797/obtain-details-fragment branch from e3cdd18 to 75ad3c2 Compare November 12, 2024 13:49
@mickmis mickmis merged commit a1302ef into interuss:main Nov 12, 2024
20 checks passed
@mickmis mickmis deleted the 797/obtain-details-fragment branch November 12, 2024 14:02
github-actions bot added a commit that referenced this pull request Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants