c569cdf534
The tests for `validate_checksums()` already cover the case of a truncated SSTable. However, the test performs the truncation after the SSTable has been loaded, which means that the SSTable object has cached the old file size by the time we validate its checksums. This is a valid case, but not the most common one. Add a new test that loads the SSTable after the truncation. Do not use the same SSTable as for the other tests, since this has been loaded already. Additionally, let both tests check SSTables with different types of truncations: minor truncations affecting only the last chunk, and major truncations spanning across multiple chunks. 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++ 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.