4 Client and server use
20 Client  section in Negative HTTP/2 Interop Test Case Descriptions
23 Clients implement test cases that test certain functionality. Each client is
38 Note that the server and client must be invoked with the same test case or else
40 that invokes both server and client at the same time, with the same test_case.
47 This test verifies that the client correctly responds to a goaway sent by the
48 server. The client should handle the goaway by switching to a new stream without
51 Client Procedure:
52  1. Client sends two UnaryCall requests (and sleeps for 1 second in-between).
64 Client asserts:
72 * Two different connections were used from the client.
76 This test verifies that the client fails correctly when the server sends a
77 RST_STREAM immediately after sending headers to the client.
80  1. Client sends UnaryCall with:
91 Client asserts:
95   1. Server sends a RST_STREAM with error code 0 after sending headers to the client.
98 languages. Those checks will be added once all client languages behave the same way. [#9142](https:…
102 This test verifies that the client fails "correctly" when the server sends a
103 RST_STREAM halfway through sending data to the client.
106  1. Client sends UnaryCall with:
117 Client asserts:
122      the requested data to the client.
126 This test verifies that the client fails "correctly" when the server sends a
127 RST_STREAM after sending all of the data to the client.
130  1. Client sends UnaryCall with:
141 Client asserts:
146   data to the client.
148 *Certain client languages allow the data to be accessed even though a RST_STREAM
149 was encountered. Once all client languages behave this way, checks will be added on
154 This test verifies that the client correctly acknowledges all pings it gets from the
158  1. Client sends UnaryCall with:
169 Client asserts:
175   when it receives an ack from the client).
183 This test verifies that the client observes the MAX_CONCURRENT_STREAMS limit set by the server.
185 Client Procedure:
186 …1. Client sends initial UnaryCall to allow the server to update its MAX_CONCURRENT_STREAMS setting…
187   2. Client concurrently sends 10 UnaryCalls.
189 Client Asserts:
199 This test verifies that the client can correctly receive padded http2 data
200 frames. It also stresses the client's flow control (there is a high chance
201 that the sender will deadlock if the client's flow control logic doesn't
204 Client Procedure:
208  1. Client calls UnaryCall with:
219 Client asserts:
226   1. Reply to the client's request with a `SimpleResponse`, with a payload
239 This test verifies that the client can correctly receive a series of small
246 Client Procedure:
250  1. Client calls UnaryCall with:
261 Client asserts:
268   1. Reply to the client's request with a `SimpleResponse`, with a payload