c052f2ad1d
This test will soon need to be changed to use tombstone-gc=repair. This cannot work as of now, as the test uses a single-node cluster. The options are the following: * Make it use more than one nodes * Make repair work with single node clusters * Rewrite in C++ where repair can be done synthetically We chose the last option, it is the simplest one both in terms of code and runtime footprint. The new test is in test/boost/row_cache_test.cc Two changes were done during the migration * Change the name to test_populating_reader_tombstone_gc_with_data_in_memtable to better express which cache component this test is targetting; * Use NullCompactionStrategy on the table instead of disabling auto-compaction.
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.