Running Tests

VSAG uses Catch2 for testing, organized in two layers:

• Unit tests live next to source files under src/.
• Functional tests live under tests/ and cover cross-module, end-to-end behavior. Typical files include test_hgraph.cpp, test_ivf.cpp, test_pyramid.cpp, test_sindi.cpp, test_brute_force.cpp, and test_memleak.cpp.

Run the Full Suite

make test configures a Debug build with tests enabled and runs the full unit + functional suite:

make test

Note: make test does not enable coverage instrumentation. To produce a coverage report, use make cov — it configures the build with ENABLE_COVERAGE=ON; run the test binaries afterwards to collect and aggregate coverage data:

make cov
# then run the test binaries, e.g.:
./build-debug/tests/functional_tests
# open build-debug/coverage/index.html

Run a Single Binary

./build-debug/tests/functional_tests "[hgraph]"
./build-debug/tests/functional_tests "[hgraph][concurrent]"

Catch2 supports filtering by name, tag, and wildcards — see --help.

Coverage Expectations

Contributions are expected to keep the C++ line coverage over src/ and include/ at 90% or higher, as measured by the make cov flow and the CI coverage job.

Memory & Concurrency

• test_memleak.cpp: run under AddressSanitizer / LeakSanitizer to verify construction and destruction paths.
• test_index/test_index_concurrent.cpp: shared concurrent add and search correctness for maintained indexes that advertise the corresponding feature flags.

Python Tests

make pyvsag PY_VERSION=3.10
cd tests/python && pytest -q

References

• tests/ directory
• Makefile entries: test, cov, asan