a41140f569
In other words, print more user-friendly messages, and avoid crashing. Specifically: * Don't crash when attempting to load schema tables from configured data-dir, while configuration does not have any configured data-directories. * Detect the case where schema mutations have no rows for the current table -- the keyspace exists, but the table doesn't. * Add negative tests for schema-loading. Fixes: https://github.com/scylladb/scylladb/issues/16459 Closes scylladb/scylladb#16494 * github.com:scylladb/scylladb: test/cql-pytest: test_tools.py: add test for failed schema loadig tools/scylla-sstable: use at() instead of operator [] when obtaining data dirs tools/schema_loader: also check for empty table/column mutations tools/schema_loader: log more details when loading schema from schema tables
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++ cql-pytest - 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.