b97ded5c4a
A user asked on the ScyllaDB forum several questions on whether tombstone_gc works on materialized views. This patch includes two tests that confirm the following: 1. The tombstone_gc may be set on a view - either during its creation with CREATE MATERIALIZED VIEW or later with ALTER MATERIALIZED VIEW. 2. The tombstone_gc setting is correctly shown - for both base tables and views - by the "DESC" statement. 3. The tombstone_gc setting is NOT inherited from a base table to a new view - if you want this option on a view, you need to set it separately. Unfortunately, this test could not be a single-node cql-pytest because we forbid tombstone_gc=repair when RF=1, and since recently, we forbid setting RF>1 on a single-node setup. So the new tests are written in the test/topology framework - which may run multiple tests against a single three-node cluster run multiple tests against it. To write tests over a shared cluster, we need functions which create temporary keyspaces, tables and views, which are deleted automatically as soon as a test ends. The test/topology framework was lacking such functions, so this tests includes them - currently inside the test file, but if other people find them useful they can be moved to a more central location. The new functions, net_test_keyspace(), new_test_table() and new_materialized_view() are inspired by the identically-named functions in test/cql-pytest/util.py, but the implementation is different: Importantly, the new functions here are *async* context managers, used via "async with", to fit with the rest of the asynchronous code used in the topology test framework. Signed-off-by: Nadav Har'El <nyh@scylladb.com> Closes scylladb/scylladb#17345
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.