12d5e758ed
Move the keyspace+table setup logic for test_incremental_repair_race_window_promotes_unrepaired_data into a dedicated helper function _setup_table_for_race_window(). The helper creates a fresh keyspace (unique name via create_new_test_keyspace), the table, configures STCS min_threshold=2, inserts baseline keys, runs repair 1, inserts keys for repair 2, and flushes. This is a pure refactor with no behavioral change: the test function now calls the helper once instead of inlining the setup. The extraction enables a subsequent commit to call the helper again on retry when a leadership transfer is detected.
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.