bf0d1cf272
PRs included: * #22810 (encryption_at_rest_test/encryption: Add some verbosity etc to help diagnose test run issues) * #23778 (encryption_at_rest_test: Make fake_proxy read/write loop noexcept) Backporting them together because the latter needs the former to avoid conflicts, but the former cannot be backported individually due to not fixing an issue. * (cherry picked from commit83aa66da1a) * (cherry picked from commit5905c19ab4) * (cherry picked from commit00263aa57a) * (cherry picked from commit4a44651fce) Refs #22628. Fixes #23774. Closes scylladb/scylladb#25774 * github.com:scylladb/scylladb: encryption_at_rest_test: Make fake_proxy read/write loop noexcept gcp/aws kms: Promote service_error to recoverable + use malformed_response_error encryption_at_rest_test: Add verbosity + earlier stream close to proxy encryption: Add exception handler to context init (for tests)
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.