fa86405b1f
Now that the previous patch made it possible to write to system tables in Alternator tests, this patch introduces utility functions for changing the configuration - scylla_config_write() in addition to the scylla_config_read() we already had, and scylla_config_temporary() to temporarily change a configurable parameter and then restore it to its old value. This patch adds a silly test that temporarily modifies the query_tombstone_page_limit configuration parameter. Later we can add more tests that use the new test functions for more "serious" testing of real features. In particular, we don't have an Alternator test for the max_concurrent_requests_per_shard configuration - and I want to write one. Signed-off-by: Nadav Har'El <nyh@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.