5659f23b2a
The mock server currently provides its own router to the aiohttp.web app. The ability to provide custom routers however is deprecated and can be removed at any point. So refactor the mock server to use the built-in router. This requires some changes, because the built-in router does not allow adding/removing routes once the server starts. However the mock server only learns of the used routes when the tests run. This unfortunately means that we have to statically register all possible routes the tests will use. Fortunately, aiohttp has variable route support (templated routes) and with this, we can get away with just 9 statically registered routes, which is not too bad. A (desired) side-effect of this refactoring is that now requests to different routes do not have to arrive in order. This constraint of the previous implementation proved to be not useful, and even made writing certain tests awkward.
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.