a651f7eef0
Add a `storage` fixture to test/cluster/conftest.py that parametrizes tests over local filesystem, S3 (MinIO), and GCS backends. When S3 is selected the fixture reuses the global MinIO instance started by test.py (via environment variables) or falls back to a per-test MinioWrapper. For GCS it starts a local fake-gcs-server container. Add make_cfg() and make_ks_opts() helpers to test/cluster/util.py for building server config and keyspace CQL options with optional object storage — reusable by any tablet test that needs storage parametrization. Parametrize test_file_streaming_respects_encryption with the new fixture so it runs on all three backends. The local variant is the original test, the S3/GCS variants exercise the load_metadata fix (SCYLLADB-1704).
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.