[
https://issues.apache.org/jira/browse/CASSCPP-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18123918#comment-18123918
]
Bret McGuire commented on CASSCPP-18:
-------------------------------------
One possible middle ground here might be to do TLS-specific testing on a less
frequent cadence, say as some kind of a weekly build (or something similar).
Even then I'm not completely convinced it's worth it... but it seemed like a
useful conversation to have.
> Consider testing support for varying TLS versions
> -------------------------------------------------
>
> Key: CASSCPP-18
> URL: https://issues.apache.org/jira/browse/CASSCPP-18
> Project: Apache Cassandra C/C++ driver
> Issue Type: Improvement
> Components: Test
> Reporter: Bret McGuire
> Priority: Normal
>
> An outgrowth of CASSCPP-16. As part of work on that ticket we identified
> some tests that _rely_ on TLS 1.2 in order to function correctly (as
> implemented). This raises some interesting questions around how we test TLS.
> Specifically two things should be considered as part of this ticket:
> First: is there an argument to make TLS version configurable for the
> unit/integration tests? Presumably this could be added as a googletest flag
> (or something similar). I'm fairly sure we _can_ do this but do we get
> enough return to make it worthwhile?
> Second: do we want to configure our CI to use TLS version as an axis for
> running tests? This isn't an obvious "yes" to me; doing so would add time to
> each test run and there's a legit question about whether we'd get enough
> value from doing so to make adding that time worthwhile.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
