메뉴
Run FalkorDB's test suites - Rust unit tests, Python e2e/function/MVCC/concurrency tests, openCypher TCK compliance tests, and flow tests. Use when asked to run, narrow down, or debug a failing test, or to decide which suite covers a change.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | test |
| description | Run FalkorDB's test suites - Rust unit tests, Python e2e/function/MVCC/concurrency tests, openCypher TCK compliance tests, and flow tests. Use when asked to run, narrow down, or debug a failing test, or to decide which suite covers a change. |
| allowed-tools | Bash |
All Python suites require the virtualenv. Locally it's ./venv (create once
with python3 -m venv venv && pip install -r tests/requirements.txt); inside
the devcontainer/CI it lives at /data/venv. The activation lines below fall
back between the two so they work in either environment. The module must be
built first (cargo build, see the build skill) for anything that loads
libfalkordb.{so,dylib}.
cargo test -p graph
source venv/bin/activate 2>/dev/null || source /data/venv/bin/activate
pytest tests/test_e2e.py tests/test_functions.py -vv # e2e + function tests
pytest tests/test_mvcc.py tests/test_concurrency.py -vv # MVCC + concurrency tests
Run a single file/suite by narrowing the pytest args, e.g.
pytest tests/test_mvcc.py -vv.
source venv/bin/activate 2>/dev/null || source /data/venv/bin/activate
TCK_DONE=tck_done.txt pytest tests/tck/test_tck.py -s # all currently-passing scenarios
TCK_INCLUDE=<path> pytest tests/tck/test_tck.py -s # only scenarios under <path>
tck_done.txt is the checked-in allow-list of scenarios expected to pass;
a scenario newly failing there is a regression, one newly passing should be
added to the file.TCK_INCLUDE paths: tests/tck/features/expressions/list,
tests/tck/features/expressions/map, tests/tck/features/clauses/match,
tests/tck/features/clauses/return.cargo build # debug build required first (flow.sh defaults to target/debug)
./flow.sh
flow.sh supports env vars for narrowing/debugging a run:
TEST="tests/flow/test_function_calls" ./flow.sh — one fileTEST="tests/flow/test_function_calls:testFunctionCallsFlow.test89_JOIN" ./flow.sh — one testFAIL_FAST=1 — stop on first failure, run serially (--parallelism 1)RELEASE=1 — run against target/release instead of target/debugflow_tests_done.txt / flow_tests_todo.txt; logs
land in tests/flow/logs.rust-pr.yml) runs all of the above per PR/push, plus fuzzing and
coverage — see the fuzz, profile, and coverage skills for those.-svc) are known-flaky under
ASAN/coverage instrumentation due to a pre-existing concurrency race
(atomic_refcell "already mutably borrowed"); if only those fail under
those configurations, re-run before treating it as a regression.If tests fail, analyze the output and help the user understand what went wrong.
Profile FalkorDB performance - generate samply flamegraphs and run the benchmark suite. Use when investigating a performance regression/bottleneck or comparing benchmark results. For code-coverage reports use the coverage skill.
Build FalkorDB (Rust code plus its native GraphBLAS/RediSearch dependencies), and run formatting/lint checks. Use when asked to build or compile the project, set up native dependencies for the first time, fix a build/compile/lint error, or run cargo fmt/clippy.
Measure FalkorDB code coverage with LLVM source-based instrumentation across Rust unit tests, Python e2e/MVCC/concurrency tests, flow tests, and TCK - producing an lcov report. Use when asked to measure/report test coverage or reproduce the CI coverage job locally.
Debug FalkorDB crashes, hangs, panics, and incorrect query results - attach lldb/gdb to redis-server with the module loaded, understand panic/crash behavior, step through query execution, and triage failing CI runs. Use when investigating a crash, hang, wrong query result, or a red CI job.
Run and manage FalkorDB's cargo-fuzz pipeline for the query runtime (fuzz_target_runtime) - build the fuzz target, run/minimize the corpus, generate coverage, and reproduce a crash artifact. Use when asked to fuzz test the runtime, investigate a fuzzing crash/artifact, or update the fuzz corpus.
Run FalkorDB's stricter opt-in Clippy pass (pedantic/nursery/cargo lints) beyond the basic CI gate, optionally auto-fixing. Use when asked for a deep/strict lint pass or to auto-fix clippy warnings; for the standard fmt+clippy CI gate use the build skill.