d365d9b2ad
It may happen that the ports we randomly choose for LDAP are busy, and that'd fail the test suite, so once we randomly select ports, now we'll see if they're busy or not, and if they're busy, we'll select next ones, until we finally have some free ports for LDAP. Tested with: `./test.py ldap/ldap_connection_test --repeat 1000 -j 10`: before the fix, this command fails after ~112 runs, and of course it passes with the fix. Fixes: scylladb/scylla-enterprise#5120 Fixes: scylladb/scylladb#23149 Fixes: scylladb/scylladb#23242 Closes scylladb/scylladb#23275
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.