7a1ec3aa41
All current unit tests for scrub in validate mode generate random SSTables on the fly. Add some more tests with frozen Cassandra SSTables from the source tree to verify compatibility with Cassandra. Use some of the existing 3.x Cassandra SSTables to test the valid case, and use the same schema to generate some corrupted SSTables for the invalid case. Overall, the new tests cover the following scenarios: * valid compressed/uncompressed * compressed/uncompressed with invalid checksums * compressed/uncompressed with invalid digest For the compressed SSTable with invalid checksums, a small chunk length was used (4KiB) to have more chunks with less disk space. For uncompressed SSTables the chunk length is not configurable. Finally, since the SSTables live in the source tree, the quarantine mechanism was disabled. Signed-off-by: Nikos Dragazis <nikolaos.dragazis@scylladb.com>
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.