For a single injection, all created injection handlers share all received messages. In particular, it means that one received message unblocks all handlers waiting for the first message. This behavior is often desired, for example, if multiple fibers execute the injected code and we want to unblock them all with a single message. However, there is a problem if we want to block every execution of the injected code. Apart from the first created handler, all handlers will be instantly unblocked by messages from the past that have already unblocked the first handler. In one of the following commits, we add a test that needs to block the CDC generation publisher's loop twice. Since it looks like there are no good workarounds for this arguably general problem, we extend injections with handlers in a way that solves it. We introduce the new `share_messages` parameter. Depending on its value, handlers will share messages or not. The details are described in the new comments in `error_injection.hh`. We also add some basic unit tests for the new funcionality.
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.