f4059c2ee9
Migrate all tests from scylla-dtest/wide_rows_test.py to the in-tree test/cluster/dtest framework. This covers 31 test methods parametrized over 4 compaction strategies (LCS, STCS, TWCS, ICS) for 124 total tests. Includes single-node tests for large partition, row, and cell detection, TTL expiration, collection element thresholds, column index stress, and threshold changes. Also includes multi-node tests for node stop/start with repair and materialized view validation. Functional changes required by the different infrastructure: - Replace node.status with node.is_running() (ScyllaNode has no status attr) - Replace flush()+wait_for_compactions() with compact() (Scylla nodetool compact handles flush and waiting internally) - Remove redundant flush() before compact()/nodetool compact - Replace import of wait_for_view from tools.tables_view_manager with an inline synchronous implementation (the original is async) - Remove dtest_full, dtest_debug, next_gating markers (not used in the target framework) - Remove commented-out dead code
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.