test-consistency

To validate Moon output against Redis for consistency, you can run automated tests using a provided shell script that checks data parity across strings, hashes, lists, sets, zsets, graphs, and MVCC features.

Yes, you need redis-server available on your system PATH to run Moon consistency tests, as Redis serves as the ground truth database for validating all data types and configurations.

Yes, Moon consistency tests support multiple shards and custom port mappings, allowing you to mirror production configurations using command line options like --shards and --port-rust.

The best way to automate Moon and Redis consistency checks in CI is by executing the test script with the --skip-build flag, catching data drift and regressions before release across all supported data types.

Moon consistency testing compares outputs against Redis to reduce data drift and ensure behavioral parity, using Redis as a reliable ground truth across complex data structures like graphs and MVCC features.

Testing Moon consistency is limited to the data types and configurations supported by both systems, requiring redis-server on PATH and relying on specific script flags to manage sharding and build steps.