f65a52f3ec
Migrate mock-based rescoring and oversampling tests from test/vector_search/rescoring_test.cc to pytest and delete the C++ file. Index option validation tests go to test_vector_index.py; rescoring tests go to a new test_vector_search_rescoring.py which introduces shared infrastructure (EmbeddingRow dataclass, TEST_DATA dict, reversed_ann_response() helper, rescoring_test_table() context manager). Two tests have updated assertions (semantic change): filters_invalid_similarity_scores now uses per-function expected result sets including a zero-vector row, and rescoring_with_zerovector_query asserts empty results after NaN filtering (cosine only). Both are marked xfail pending SCYLLADB-924. Follow-up to #29593. Does not require backport - simple refactoring of tests Closes scylladb/scylladb#29906 * github.com:scylladb/scylladb: test/vector_search: migrate zero-vector query rescoring test to pytest; delete rescoring_test.cc test/vector_search: migrate invalid similarity score filtering test to pytest test/vector_search: migrate non-ANN similarity argument rescoring test to pytest test/vector_search: migrate wildcard select rescoring test to pytest test/vector_search: migrate similarity_function rescoring test to pytest test/vector_search: migrate rescoring and f32 quantization tests to pytest test/vector_search: migrate oversampling tests to pytest test/vector_search: migrate vector_index option validation tests to pytest
Scylla in-source tests.
For details on how to run the tests, see docs/dev/testing.md
Shared C++ utils, libraries are in lib/, for Python - pylib/
alternator - Python tests which connect to a single server and use the DynamoDB API unit, boost, raft - unit tests in C++ cqlpy - Python tests which connect to a single server and use CQL topology* - tests that set up clusters and add/remove nodes cql - approval tests that use CQL and pre-recorded output rest_api - tests for Scylla REST API Port 9000 scylla-gdb - tests for scylla-gdb.py helper script nodetool - tests for C++ implementation of nodetool
If you can use an existing folder, consider adding your test to it. New folders should be used for new large categories/subsystems, or when the test environment is significantly different from some existing suite, e.g. you plan to start scylladb with different configuration, and you intend to add many tests and would like them to reuse an existing Scylla cluster (clusters can be reused for tests within the same folder).
To add a new folder, create a new directory, and then
copy & edit its suite.ini.