061bd89957
Refactor how the tests check for expected requests which were never invoked. At the end of every test, the nodetool fixture requests all unconsumed expected requests from the rest_api_mock.py and checks that there is none. This mechanism has some interaction with requests which have a "multiple" set: rest_api_mock.py allows registering requests with different "multiple" requirements -- how many times a request is expected to be invoked: * ANY: [0, +inf) * ONE: 1 * MULTIPLE: [1, +inf) Requests are stored in a stack. When a request arrives, we pop off requests from the top until we find a perfect match. We pop off requests, iff: multiple == ANY || multiple == MULTIPLE and was hit at least once. This works as long as we don't have an multiple=ANY request at the bottom of the stack which is never invoked. Or a multiple=MULTIPLE one. This will get worse once we refactor requests to be not stored in a stack. So in this patch, we filter requests when collecting unexhausted ones, dropping those which would be qualified to be popped from the stack.
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.