acd643bd75
In the current scenario, 'test_replace_with_encryption' only confirms the replacement with inter-dc encryption for normal nodes. This commit increases the coverage of test by parametrizing the test to confirm behavior for zero token node replacement as well. This test also implicitly provides coverage for bootstrap with encryption of zero token nodes. This PR increases coverage for existing code. Hence we need to backport it. Since only 6.2 version has zero token node support, hence we only backport it to 6.2 Fixes: scylladb/scylladb#21096 Closes scylladb/scylladb#21609
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.