60e04e2c59
Memtables are fickle, they can be flushed when there is memory pressure, if there is too much commitlog or if there is too much data in them. The tests in test_select_from_mutation_fragments.py currently assume data written is in the memtable. This is tru most of the time but we have seen some odd test failures that couldn't be understood. To make the tests more robust, flush the data to the disk and read it from the sstables. This means that some range scans need to filter to read from just a single mutation source, but this does not influence the tests.
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.