You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Within that list, all but the last 2 item test code that is common to both client and server code, so our coverage is reasonably good in terms of unit testing
the quic_tserver_test creates a 'dummy' server using internal api calls, so doesn't really address our server testing goals I think.
If our goal is to exercise our quic client and quic server in what might approximate 'real world' usage, I would suggest the best approach is to augment our quic interop testing such that we:
create an hq-interop-server (a companion to our quic-hq-interop client in the demos/guide directory
augment our interop container in tests/quic-openssl-docker, to run the server as part of our interop ci.
Write additional fault injection tests to cover QUIC server functionality
We should, during refinement, potentially break this into several subtasks, to increase parallelism
Tasks
The text was updated successfully, but these errors were encountered: