Currently driver creates network layout (node IP addresses and ports) from `system.local`, `system.peers`, `system.client_routes` and then runs on assumption that this network layout is correct. It does not check if it is. If, for example it happens so that node ip/port (say on proxy) will not match what driver calculated it will go unnoticed. The goal of this feature is to provide driver host-id on SUPPORTED frame, so that it would know which node it connected to and could make decision wether keep connection or drop it. - add `SCYLLA_HOST_ID` to the CQL `SUPPORTED` response - add a regression test that hooks the Python driver handshake and verifies the reported host id - `python3.12 -m py_compile test/cqlpy/test_protocol_exceptions.py` - syntax-only compile of `transport/server.cc` with the repo toolchain flags inside `dbuild` Refs #27452 Refs https://scylladb.atlassian.net/browse/DRIVER-610 Closes scylladb/scylladb#29809
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.