When writing tests, I stumbled upon an issue, that may affect almost all pure quic related tests.
If you do not specify an alpn it defaults h3. Most tests that are supposed to test only quic (so no h3 in the name), do not specify alpn, so these use h3.
This matters, as the used application is quite different between h3, which uses nghttp3and somehting like foo which uses the default application, which is a quite different code path.
So I wonder, if it is possible in the node.js test framework, to run these tests for both cases (without writing seperate tests, similar to certain wpt tests?). (I am still alien to the details of the tests).
Currently, half of the code is not tested.
@jasnell , @pimterry any ideas?
When writing tests, I stumbled upon an issue, that may affect almost all pure quic related tests.
If you do not specify an
alpnit defaultsh3. Most tests that are supposed to test only quic (so noh3in the name), do not specifyalpn, so these useh3.This matters, as the used application is quite different between
h3, which usesnghttp3and somehting likefoowhich uses the default application, which is a quite different code path.So I wonder, if it is possible in the node.js test framework, to run these tests for both cases (without writing seperate tests, similar to certain wpt tests?). (I am still alien to the details of the tests).
Currently, half of the code is not tested.
@jasnell , @pimterry any ideas?