| commit | 7ddea9b1f700989d097536d5b4f6ae2f4c24c2b6 | [log] [tgz] |
|---|---|---|
| author | bnc <bnc@google.com> | Wed May 18 08:36:18 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed May 18 08:39:46 2022 -0700 |
| tree | 2460e4471c568c35d29de6a7080bdd311a6a10d3 | |
| parent | 842dc4ac880bdfd715fb1b6f1abb84fc9f101775 [diff] |
Move QUICHE test helper functions and classes into quiche::test namespace. Move QuicheFlagSaver, QuicheTest, QuicheTestWithParam<>, ScopedEnvironmentForThreads, and QuicheGetTestMemoryCachePathImpl() from top level namespace to quiche::test. Move QuicFlagSaver, QuicTest, and QuicTestWithParam<> from top level namespace to quic::test. There were two implementations of QuicheTestImpl and of QuicheTestWithParamImpl in net/quic/platform_overrides/quiche_platform_impl/quiche_test_impl.h, one each within quiche::test on lines 24-27, one each in the top level namespace on lines 186-205 (not actually used). This CL removes the unused ones. PiperOrigin-RevId: 449490232
QUICHE stands for QUIC, Http, Etc. It is Google‘s production-ready implementation of QUIC, HTTP/2, HTTP/3, and related protocols and tools. It powers Google’s servers, Chromium, Envoy, and other projects. It is actively developed and maintained.
There are two public QUICHE repositories. Either one may be used by embedders, as they are automatically kept in sync:
To embed QUICHE in your project, platform APIs need to be implemented and build files need to be created. Note that it is on the QUICHE team's roadmap to include default implementation for all platform APIs and to open-source build files. In the meanwhile, take a look at open source embedders like Chromium and Envoy to get started:
To contribute to QUICHE, follow instructions at CONTRIBUTING.md.
QUICHE is only supported on little-endian platforms.