// Run Rust tests after making changes to verify correctness. Use this when you want to verify your changes to Rust code.
| name | run-rust-tests |
| description | Run Rust tests after making changes to verify correctness. Use this when you want to verify your changes to Rust code. |
Run Rust tests after making changes to verify correctness.
all: Run all Rust tests<crate>: Run tests for specific crate (e.g., /run-rust-tests hyperloglog)<crate> <test>: Run specific test in crate (e.g., /run-rust-tests hyperloglog test_merge)Arguments provided: $ARGUMENTS
Run this skill after modifying Rust code to ensure tests pass.
src/redisearch_rs/ using git status and git diff --name-onlysrc/redisearch_rs/, e.g., src/redisearch_rs/hyperloglog/src/lib.rs → hyperloglog)cargo nextest run --manifest-path src/redisearch_rs/Cargo.toml -p <crate1> -p <crate2> ...
src/redisearch_rs/, or if you cannot determine affected crates, run all testsall is provided, run all Rust tests:
cargo nextest run --manifest-path src/redisearch_rs/Cargo.toml
cargo nextest run --manifest-path src/redisearch_rs/Cargo.toml -p <crate_name>
cargo nextest run --manifest-path src/redisearch_rs/Cargo.toml -p <crate_name> <test_name>
# Test specific crate
cargo nextest run --manifest-path src/redisearch_rs/Cargo.toml -p hyperloglog
cargo nextest run --manifest-path src/redisearch_rs/Cargo.toml -p inverted_index
cargo nextest run --manifest-path src/redisearch_rs/Cargo.toml -p trie_rs
# Run a specific test
cargo nextest run --manifest-path src/redisearch_rs/Cargo.toml -p <crate_name> <test_name>
# Run tests under miri (for undefined behavior detection)
cargo +nightly miri test --manifest-path src/redisearch_rs/Cargo.toml
Compile the project to verify changes build successfully. Use this to verify your changes build properly together with the complete project and dependencies, and make sure to use it before running end to end tests.
Investigate a RediSearch flaky-test report from a Jira key, CI failure, test id, or local logs. Use this to collect evidence, identify a supported root cause, and propose a real fix; if the evidence is insufficient, say so and ask for the missing data instead of suggesting workaround-only fixes or skip_until.
Fix merge conflicts in a jj change and its ancestors, starting from the oldest conflict. Use this when a jj change or its ancestors have conflicts that need resolving.
Check code quality and formatting before committing changes. Use this to verify your changes meet our coding standards.
Guide for porting a C module to Rust. Use this when starting to port a C module to Rust.
Run Rust benchmarks and compare performance with the C implementation. Use this when you work on migrating C code to Rust and want to ensure performance is not regressed.