For the changes to go through the left_token_ring state when REMOVENODE_WITH_LEFT_TOKEN_RING feature is enabled, we need to allow removing nodes to not have any tokens (similarly to decommissioning nodes, which use the same sequence of states). This means the tests also need to change to allow for this new behavior - it can temporarily happen that a removing node has no tokens but is still part of Raft group 0 (so there may be a temporary mismatch between the token ring and group 0 membership). Therefore, the `check_token_ring_and_group0_consistency` function is replaced by `wait_for_token_ring_and_group0_consistency`, which waits up to 30 seconds for consistency to be reached.
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.