The Hub UT framework should send what it received #206
+140
−18
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.
What this PR does / why we need it
Before this PR the UT framework would send the registered operation. This was not useful for unit tests as it is those same tests that registered the operation, so they are aware of what it is. What is the tests need is for the framework to send the actual received GraphQL request so that it can be verified.
This PR does this.
NOTE: This change is not backwards-compatible. However, I feel it is early enough in the use of the UT framework and that the only ones using it are probably the CLI team, that we can easily adapt.
The unit tests of the UT framework are updated to check that the sent value is the actual query received by the mock server.
Which issue(s) this PR fixes
Follow-up to #202
Describe testing done for PR
I have an internal set of unit tests that now detects more failures by comparing the received graphql request with what the tests expect.
Release note
Additional information
Special notes for your reviewer