473bb44722
Update `test_connections_parameters_auto_update` to also check that the scheduling group of given connections is appropriately changed when a different service level is assigned to the user that the connection uses for authentication. Apart from that, more tests are added: - Check for the logic that forbids setting shares for a service level until all nodes in the cluster are upgraded - Test for handling the case when there are more scheduling groups than it is allowed (it might happen after upgrade from a non-workload-prio version) - Regression test for a bug where less scheduling groups could have been created than allowed due to some metrics not being renamed on scheduling group name change.
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.