grpc-streaming-tests

Streaming RPCs need test coverage for deadline behavior, cancellation propagation, flow control under backpressure, and status-code semantics that differ from unary calls - covering all four patterns (Unary, Server-streaming, Client-streaming, Bidirectional-streaming) per the [gRPC core concepts docs].

When to use

• Service exposes streaming RPCs (price ticker, log tail, IoT telemetry, AI streaming inference).
• Pre-deploy gate: deadline + cancellation propagate correctly, partial-stream errors return correct status codes.
• Load test gate: streams handle backpressure without OOM or silent drops.

How to use