Testing · evidence · limitations

Correctness and compatibility

What we check for protocol behavior and client correctness. Workflow coverage describes tests that can run, not proof that every test passed on the current revision.

Automatic gate versus extended checks

Scope: pr-gate.yml runs on pull requests and pushes to main on Ubuntu. It checks Rust formatting and core tests, benchmark-regression units, first-party Rust and .NET client tests, a two-shard routing smoke, and live Rust client routing. The extended ci.yml and integration-package workflows remain manually dispatched. Outcome: these are configured checks; consult the linked workflow run for results on a specific commit. Limit: a passing smoke test is not a compatibility or production-readiness certification.

Automatic gate source Extended workflow Test guide

Reproduce locally

From a checkout of the revision under test, run ./scripts/test.sh on macOS/Linux/WSL or .\scripts\test.ps1 on Windows. The default covers formatting, Rust all-target tests and store smoke; --clippy is optional. Run the live-client tests with their documented server prerequisites. Results here intentionally do not attach a passing count from an older checkout to today's HEAD.

Supported-command Redis differential checks and multi-platform checks are in the manual extended workflow, not in every push gate. See the workflow definitions for the actual matrix and commands.