d3a9654fcc
This test runs all its cases in seastar thread, but still uses .then() continuations in some of them. This PR converts all continuations into plain .get()-s. Closes scylladb/scylladb#20457 * github.com:scylladb/scylladb: test: Restore indentation after previous changes test: Threadify tombstone_in_tombstone2() test: Threadify range_tombstone_reading() test: Threadify tombstone_in_tombstone() test: Threadify broken_ranges_collection() test: Threadify compact_storage_dense_read() test: Threadify compact_storage_simple_dense_read() test: Threadify compact_storage_sparse_read() test: Simplify test_range_reads() counting test: Simplify test_range_reads() inner loop test: Threadify test_range_reads() itself test: Threadify test_range_reads() callers test: Threadify generate_clustered() itself test: Threadify generate_clustered() callers test: Threadify test_no_clustered test test: Threadify nonexistent_key test
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.