edc15a3cf5
We already have a rather rudimentary test for system.clients listing CQL connections. However, as written the test will pass if system.clients is empty :-) So let's strengthen the test to verify that there must be at least one CQL connection listed in system.clients. Indeed, the test runs the "SELECT FROM system.clients" over one CQL connection, so surely that connection must be present. This patch doesn't strengthen this test in any other way - it still has just one connection, not many, it still doesn't validate the values of most of the columns, and it is still written to assume the Scylla server is running on localhost and not running any other workload in parallel. Signed-off-by: Nadav Har'El <nyh@scylladb.com>
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.