e7d4e080e9
After fixing scylladb/scylladb#15924 in one of the previous patches, we reenable background writes in `test_topology_ops`. We also start background writes a bit later after adding all nodes. Without this change and with tablets, the test fails with: ``` > await cql.run_async(f"CREATE TABLE tbl (pk int PRIMARY KEY, v int)") E cassandra.protocol.ConfigurationException: <Error from server: code=2300 [Query invalid because of configuration issue] message="Datacenter datacenter1 doesn't have enough nodes for replication_factor=3"> ``` The change above makes the test a bit weaker, but we don't have to worry about it. If adding nodes is bugged, other tests should detect it. Unfortunately, the test still doesn't pass with tablets and background writes because of scylladb/scylladb#17025, so we keep background writes disabled with tablets and leave FIXME. Fixes scylladb/scylladb#15962
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.