-
Notifications
You must be signed in to change notification settings - Fork 5.3k
improve renegotiation ssl tests #470
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
Conversation
|
/azp run runtime-libraries outerloop |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Outerloop test failures are unrelated. Updated renegotiate tests passed. |
eiriktsarpalis
left a comment
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.
LGTM 👍
| // There's no good way to ensure renegotiation happened in the test. | ||
| // Under the debugger, we can see this test hits the renegotiation codepath. | ||
| // Renegotiation will trigger another validation callback/ | ||
| Assert.True(validationCount > 1); |
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.
| Assert.True(validationCount > 1); | |
| Assert.InRange(validationCount, 2, int.MaxValue); |
| // There's no good way to ensure renegotiation happened in the test. | ||
| // Under the debugger, we can see this test hits the renegotiation codepath. | ||
| // renegotiation will trigger validation callback again. | ||
| Assert.True(validationCount > 1); |
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.
| Assert.True(validationCount > 1); | |
| Assert.InRange(validationCount, 2, int.MaxValue); |
Improve test to make sure we actually do renegotiation.
It is curious that we actually never set _pendingReHandshake to true in production code.
I will address it as part of #453