163c6f71d6
Replace move_to_shard()/move_to_host() with as_bounce()/target_shard()/ target_host() to clarify the interface after bounce was extended to support cross-node bouncing. - Add virtual as_bounce() returning const bounce* to the base class (nullptr by default, overridden in bounce to return this), replacing the virtual move_to_shard() which conflated bounce detection with shard access - Rename move_to_shard() -> target_shard() (now non-virtual, returns unsigned directly) and move_to_host() -> target_host() on bounce - Replace dynamic_pointer_cast with static_pointer_cast at call sites that already checked as_bounce() - Move forward declarations of message types before the virtual methods so as_bounce() can reference bounce Fixes: SCYLLADB-1066 Closes scylladb/scylladb#29367
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.