Mock out gateway <-> federation network layer in gateway testing #1004
Conversation
This file contains 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
okjodom
changed the title
okjodom
force-pushed
the
mock-gateway-fed-net
branch
from
752aad9 to
83469a4
Compare
elsirion
approved these changes
Nov 29, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Gateway test framework changes to mock out gateway-federation network layer by using a custom client builder for gateway integration tests.
The gateway test client builder generates clients that have a mock federation api, unlike the normal clients that establish and maintain a websocket connection with some fedetation.
This is referenced in #545 , but the solution proposed by this PR is custom to the gateway test framework