-
Notifications
You must be signed in to change notification settings - Fork 9.8k
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
Add unit test for newClientCfg #13830
Conversation
Codecov Report
@@ Coverage Diff @@
## main #13830 +/- ##
==========================================
- Coverage 72.57% 72.47% -0.11%
==========================================
Files 467 467
Lines 38280 38282 +2
==========================================
- Hits 27781 27743 -38
- Misses 8722 8749 +27
- Partials 1777 1790 +13
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
43f4ae0
to
7d2ca9b
Compare
7d2ca9b
to
3780435
Compare
Resolved all comments. |
} | ||
} | ||
|
||
func TestNewClientConfigWithSecureCfg(t *testing.T) { |
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.
What is the reason this can be added as test case to above test?
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.
Because github.com/stretchr/testify/assert doesn't support comparing function, and tls.Config contains fields of function type if we provide Cert/Key/Cacert.
Added a unit test for the original newClientCfg.
cc @serathius @spzala