Add itest oracle harness #1395
Open
Add itest oracle harness #1395
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
The public oracle server RPC endpoints for querying prices would only accept a specifier that sets only the asset ID. We may now accept group keys as well, so we consider any specifier to be valid. This is needed as we're later going to create a oracle rpc server harness to test out this code path.
In order for the oracle server harness to have a native way of providing us with logs in the itests we need to set up an itest logger, which is also initiated during test harness setup.
Adds a simple oracle server harness, this is a copy of the oracle harness implementation in LitD. We need this to have greatest code coverage in our tapd itests and also to have moving prices during the itest execution, allowing the creation of more complex scenarios.
Not all itests need to use an oracle server harness, so we introduce a functional option that may be defined when setting up a harness. This will reduce the overall diff as previous callers of the harness setup functions won't need to change their arguments.
In order to test the new harness and the previous changes, we introduce the oracle server harness in one of our rfq related tests. The 2 peers in this test will now query a real oracle price server instead of defaulting to their mock.
Pull Request Test Coverage Report for Build 13377535608Details
💛 - Coveralls |
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.
Description
This PR adds the oracle harness that is used in the LitD itests to our tapd repo. This will allow us to run an actual dummy grpc oracle server that the tapd instances of our itests can use. This will offer a slightly bigger code coverage in itests plus enable more complex scenarios with moving prices.
This branch is based on
rfq-negotiation-groupkey, which is also set as the base of this GH pull request in order to not see duplicate commits.SubscribeRfqEventNtfnsRPC endpoint will crash if it tries to marshal the rfq message sent by our peer if they consider our price unacceptable.