test(integration): add rust test for prefer low latency#5684
Merged
kaukabrizvi merged 10 commits intoaws:mainfrom Dec 31, 2025
Merged
test(integration): add rust test for prefer low latency#5684kaukabrizvi merged 10 commits intoaws:mainfrom
kaukabrizvi merged 10 commits intoaws:mainfrom
Conversation
jmayclin
approved these changes
Dec 30, 2025
Contributor
jmayclin
left a comment
There was a problem hiding this comment.
Should we also delete the corresponding IntegV2 test as part of this PR?
jouho
approved these changes
Dec 30, 2025
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
3 participants
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.
Goal
Add Rust integration tests to verify s2n_connection_prefer_low_latency() results in small TLS record sizes.
Why
This is a wire-format behavior that should be validated end-to-end as an integration test.
How
Enable prefer_low_latency on s2n-tls, perform a large data transfer with OpenSSL as the peer, record application data traffic, and assert that TLS records are small when the feature is enabled. Both client and server roles are covered.
Callouts
Separate test cases are included for TLS 1.2 and TLS 1.3 because the negotiated protocol version affects per-record overhead and therefore the observed application-data record sizes. Distinct tests ensure we assert the correct bounds for each protocol and avoid masking regressions by using a single upper bound limit.
Testing
This is a test, it runs in the PR workflow as part of the IntegRustNix batch.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.