fbbe2bdce8
Spreading db::config around and making all services depend on it is not nice. Most other service that need configuration provide their own config that's populated from db::config in main.cc/cql_test_env.cc and use it, not the global config. This PR does the same for repair_service. Enhancing components dependencies, not backporting Closes scylladb/scylladb#29153 * github.com:scylladb/scylladb: repair: Remove db/config.hh from repair/*.cc files repair: Move repair_multishard_reader options onto repair_service::config repair: Move critical_disk_utilization_level onto repair_service::config repair: Move repair_partition_count_estimation_ratio onto repair_service::config repair: Move repair_hints_batchlog_flush_cache_time_in_ms onto repair_service::config repair: Move enable_small_table_optimization_for_rbno onto repair_service::config repair: Introduce repair_service::config
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.