The test in question uses several helpers from the backup sute, but it doesn't really need them -- the operations it want to perform can be performed with standard pylib methods. "While at it" also collect some dangling effectively unused local variables from this test (these were apparently left from backup tests this one was copied-and-reworked from) Enhancing tests, not backporting Closes scylladb/scylladb#29130 * github.com:scylladb/scylladb: test/refresh: Simplify refresh invocation test/refresh: Remove r_servers alias for servers test/refresh: Replace check_mutation_replicas with a plain CQL SELECT test/refresh: Inline keyspace/table/data setup in test_refresh_deletes_uploaded_sstables test/refresh: Prepare indentation for new_test_keyspace in test_refresh_deletes_uploaded_sstables test/refresh: Decouple test_refresh_deletes_uploaded_sstables from backup tests test/refresh: Remove unused wait_for_cql_and_get_hosts import
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.