-
Notifications
You must be signed in to change notification settings - Fork 140
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
integration_tests_sv2
docs cleanup
#1340
base: main
Are you sure you want to change the base?
integration_tests_sv2
docs cleanup
#1340
Conversation
c7759e4
to
98938bd
Compare
Bencher Report
Click to view all benchmark results
|
Bencher Report
Click to view all benchmark results
|
Bencher Report
Click to view all benchmark results
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1340 +/- ##
=======================================
Coverage 19.14% 19.14%
=======================================
Files 166 166
Lines 10987 10987
=======================================
Hits 2104 2104
Misses 8883 8883
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
this is a misleading name, as this is not really a response, but rather the new message to replace the intercepted one
it's not fully designed and motivation is not clear, we can re-design if needed
we need 2 sniffers to assert the message was correctly replaced and fully delivered over the TCP connection
- improves wording on `Sniffer` docs, as it implied that messages from upstream are always a response, which is not true - adds some brief docs to `InterceptMessage` struct - removes links to private items (which generate warnings on `cargo doc`)
98938bd
to
b193189
Compare
/// Can be useful for testing purposes, as it allows to assert that the roles have sent specific | ||
/// messages in a specific order and to inspect the messages details. | ||
/// |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this paragraph was just moved from the bottom to the top, as it feels more like an introduction about Sniffer
it was a bit confusing to read it on the bottom, as it wasn't clear what it was referring to (Sniffer
in general vs some internal detail)
/// between the downstream and upstream roles. The downstream will send its messages to the | ||
/// [`Sniffer`] which will save those in the `messages_from_downstream` aggregator and forward them | ||
/// to the upstream role. When a response is received it is saved in `messages_from_upstream` and | ||
/// forwarded to the downstream role. Both `messages_from_downstream` and `messages_from_upstream` | ||
/// can be accessed as FIFO queues. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this was re-rewitten below, as it implies that messages from upstream are always a response, which is not necessarily true
/// In order to alter the messages sent between the roles, the [`Sniffer::intercept_messages`] | ||
/// field can be used. It will look for the [`InterceptMessage::expected_message_type`] in the | ||
/// specified [`InterceptMessage::direction`] and replace it with | ||
/// [`InterceptMessage::replacement_message`]. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this was replaced with a new paragraph about InterceptMessage
in the bottom in a more summarized way
builds on top of #1339
closes #1317