15e8ecb670
Currently, if the input mutation_partition requires schema upgrade, apply_monotonically always silently reverts to being non-preemptible, even if the caller passed is_preemptible::yes. To prevent that from happening, put the burden of upgrading the mutation_partition schem on the caller, which is today the apply() methods, which are synchronous anyhow. With that, we reduce the proliferation of the `apply_monotonically` overloads and keep only the low level one (which could potentially be private as well, as it's called only from within the mutation/ source files and from tests) Signed-off-by: Benny Halevy <bhalevy@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.