feat(events): CLI tool for testing event integration#539
Merged
Conversation
2d071c4 to
1685332
Compare
1685332 to
e74f8ff
Compare
Codecov Report
@@ Coverage Diff @@
## dev #539 +/- ##
==========================================
- Coverage 83.20% 83.19% -0.01%
==========================================
Files 211 211
Lines 18644 18644
Branches 2590 2590
==========================================
- Hits 15512 15511 -1
- Misses 2562 2563 +1
Partials 570 570 see 2 files with indirect coverage changes Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
msbrogli
approved these changes
Mar 10, 2023
jansegre
approved these changes
Mar 10, 2023
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
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.
Acceptance Criteria:
events_simulatorCLI command to enable a dummy stream of events to a WebSocket endpoint, simulating real scenarios--scenarioto choose the scenario betweenSINGLE_CHAIN,BEST_CHAIN_WITH_SIDE_CHAINS, andMULTIPLE_FORKS--portto chose the WebSocket server port*That's as simple as setting the list of
BaseEvents for each scenario in thescenario.pyfile. This will be done in a separate PR after pending design discussions and definition of which events should be emitted in each case. Creating this list should be almost a 1:1 conversion from the list of events that will be specified in the design.