The code responds ealry with READY message, but lack some necessary set up, namely: * update_scheduling_group(): without it, the connection runs under the default scheduling group instead of the one mapped to the user's service level. * on_connection_ready(): without it, the connection never releases its slot in the uninitialized-connections concurrency semaphore (acquired at connection creation), leaking one unit per cert-authenticated connection for the lifetime of the connection. * _authenticating = false / _ready = true: without them, system.clients reports connection_stage = AUTHENTICATING forever instead of READY (not critical, but not nice either) The PR fixes it and adds a regression test, that (for sanity) also covers AllowAll and Password authrticators Fixes SCYLLADB-1226 Present since 2025.1, probably worth backporting Closes scylladb/scylladb#29220 * github.com:scylladb/scylladb: transport: fix process_startup cert-auth path missing connection-ready setup transport: test that connection_stage is READY after auth via all process_startup paths
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.