Repository navigation
Conversation
Exercise multiplexed request and response streams, fragmented wire delivery, stream ends, trailers and resets, window settings and ping acknowledgments against an independent application model. Co-authored-by: generaltony007 <144252170+GeneralTony007@users.noreply.github.com>
Track expected and observed request/response trailers so a dropped or duplicated TrailersReceived event fails the invariant, not only malformed contents. Co-authored-by: generaltony007 <144252170+GeneralTony007@users.noreply.github.com>
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.
Refs #365.
Add a bounded Hypothesis state machine that connects a client and server in memory. It generates request/response sequences across up to eight streams, including data, end-of-stream, trailers, resets, window settings and ping acknowledgments. Wire bytes are fragmented into 1-257-byte chunks before delivery, including automatic peer responses.
An application-side model checks delivered payloads, headers, stream-end/reset/trailer events and ping acknowledgments independently of the peers' internal state. The default run uses 100 examples of up to 50 steps. There are no sockets or product-code changes. This is an initial interaction harness, not exhaustive protocol coverage.
Validation on Linux: