265660d22f
The test cluster/test_alternator::test_localnodes_joining_nodes takes a whopping 2 minutes and 9 seconds to run before this patch. After this patch, it takes just 7 seconds. The slowness of this test was caused by booting a second node that hangs during boot for 2 minutes, deliberately. We never intended for this boot to finish (the whole point of this test is to run before it finishes), but unfortunately had to wait for it to avoid all sort of nasty problems with unwaited futures. As comments already explained in the code, the solution to this problem is to *kill* the server at the end of the test - after we kill it, we can wait for it - this wait will very quickly notice that the server addition failed, and not need to wait 2 minutes. But until the previous patch, we had no API to find the server which is starting (not yet running), or to kill it. After the previous patch, we do have such an API, and can now use it, and see this test finish in 7 seconds instead of 2 minutes and 9 seconds.
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.