03e0dd0841
We can run Alternator's tests against DynamoDB with `test/alternator/run --aws`, and our intention is that all except a few specially marked should pass on DynamoDB - indicating that the test itself is correct and checks compatibility with DynamoDB and not with some misunderstood spec. Before this patch series, almost two dozen Alternator's tests failed on DynamoDB. This series fixes most of them. Refs #26079 (it fixes almost all the problems but probably not all of them so let's keep the issue open for a while longer) Closes scylladb/scylladb#27995 * github.com:scylladb/scylladb: test/alternator: fix some expected error messages to fit DynamoDB test/alternator: fix compressed request test on non-us-east1 test/alternator: fix test's expected error message on DynamoDB test/alternator: mark Alternator-only test scylla_only test/alternator: fix test on DynamoDB test/alternator: increase wait_for_gsi() timeout test/alternator: fix test passing a spurious parameter
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.