Skip to content
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

Write additional fault injection tests for QUIC server #716

Open
1 task
Tracked by #878
nhorman opened this issue Jun 19, 2024 · 1 comment
Open
1 task
Tracked by #878

Write additional fault injection tests for QUIC server #716

nhorman opened this issue Jun 19, 2024 · 1 comment
Labels
epic This issue is EPIC subepic child epic of a parent epic
Milestone

Comments

@nhorman
Copy link
Contributor

nhorman commented Jun 19, 2024

Write additional fault injection tests to cover QUIC server functionality

We should, during refinement, potentially break this into several subtasks, to increase parallelism

Tasks

  1. Spike
    nhorman
@nhorman nhorman changed the title Write additional fault injection tests for QUJIC server Write additional fault injection tests for QUIC server Jun 19, 2024
@nhorman nhorman added epic This issue is EPIC subepic child epic of a parent epic labels Jun 19, 2024
@nhorman nhorman added this to the 3.5.0 milestone Jun 19, 2024
@nhorman
Copy link
Contributor Author

nhorman commented Oct 31, 2024

currently, we have the following tests for quic:

  • quic_wire_test
  • quic_txp_test
  • quic_txpim_test
  • quic_stream_test
  • quic_srtm_test
  • quic_srt_gen_test
  • quic_record_test
  • quic_rcidm_test
  • quic_qlog_test
  • quic_newcid_test
  • quic_multistream_test
  • quic_lcidm_test
  • quic_fifd_test
  • quic_fc_test
  • quicfaulttest
  • quic_cfq_test
  • quic_cc_test
  • quicapitest
  • quic_ackm_test
  • buildtest_c_quic
  • quic_client_test
  • quic_tserver_test

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
epic This issue is EPIC subepic child epic of a parent epic
Projects
Status: New
Status: Todo
Development

No branches or pull requests

1 participant