envoyproxy/envoy

Extend //test/integration tests that run against H1 and H2 so they also run against H3/QUIC

Open

#12,930 opened on Sep 1, 2020

View on GitHub
 (5 comments) (0 reactions) (1 assignee)C++ (5,373 forks)batch import
area/quichelp wantedquic-mvp

Repository metrics

Stars
 (27,997 stars)
PR merge metrics
 (Avg merge 8d) (378 merged PRs in 30d)

Description

HTTP integration test cases like those defined in //test/integration:protocol_integration_test should be run against HTTP3/QUIC when the QUIC extension is enabled in order to ensure that H1, H2 and H3 have the same functionality and semantics. Some of the functionality tested by H2 only tests may also apply to H3/QUIC since the two protocols have similar semantics; also consider extending those tests so they run against QUIC when the extension is enabled.

Contributor guide

Research direction
Examine the existing H1/H2 integration tests in //test/integration:protocol integration test and understand how they are structured. Investigate the QUIC extension and how tests can be parameterized to run against H3/QUIC when the extension is enabled. Look for similar H2 only tests that may also apply to H3/QUIC and extend them accordingly.
Tech stack
cpp
Domain
networkingtesting qa
Issue type
Test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C++BazelIntegration testing
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60