← ClaudeAtlas

grpc-streaming-test-authorlisted

Use when a server-streaming, client-streaming or bidirectional gRPC call needs tests, or a suite needs auditing for gaps: ordering, completion, cancellation, deadlines and partial failures, with skeletons for Go, Python, JVM and Node, plus the 17 gRPC status codes and their retry rules.
testland/qa-skills · ★ 0 · API & Backend · score 72
Install: claude install-skill testland/qa-skills
# grpc-streaming-test-author ## Overview Streaming RPCs are where gRPC clients and servers most often diverge from the proto contract - message ordering, completion signalling, cancellation, and partial-failure semantics are all testable surfaces. gRPC defines four streaming patterns - unary, server-streaming, client-streaming, bidirectional - per [grpc.io/docs/what-is-grpc/core-concepts/](https://grpc.io/docs/what-is-grpc/core-concepts/); Step 1 classifies each RPC by pattern. This skill walks through producing a comprehensive test suite from the proto file. It composes `grpc-mock` for the test harness and [references/status-codes.md](references/status-codes.md) for status-code assertions; live-server (non-bufconn) patterns are in [references/wire-level-testing.md](references/wire-level-testing.md). ## When to use - Adding tests for a new streaming RPC. - Auditing an existing streaming-RPC test suite - is each pattern's required category covered? - Investigating a streaming-RPC bug - minimal repro from the test matrix. - PR review of changes to streaming RPCs (the proto-evolution rules on `stream` changes are subtle - per `buf-cli-lint-breaking-build` references/versioning-strategy.md). ## Step 1 - Classify each RPC Walk the `.proto` file and tabulate: ```proto service Chat { rpc Send(Message) returns (Ack); // unary rpc Subscribe(SubReq) returns (stream Event); // server streaming rpc Upload(stream Chunk) returns (Upl