29b42e47e5
The guardrail tests check that certain guardrails enable and disable certain warnings. These tests currently check for the *number* of warnings returned by a request, assuming that without the guardrail there would be no warning. But in the following patch we plan to add an additional warning on keyspace creation (that warns about tablets missing some features). So the tests should check for whether or not a *specific* warning is returned - not the count. I only modified tests which the change in the next patch will break. Tests which use SimpleStrategy and will not get the extra warning, are unmodified and continue to use the old approach of counting warnings. Signed-off-by: Nadav Har'El <nyh@scylladb.com>
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.