Before this patch, if an ARN that is passed to Alternator requests like TagResource is well-formatted but points to non-existent table, Alternator returns the unhelpful error: (AccessDeniedException) when calling the TagResource operation: Incorrect resource identifier This patch modifies this error to be: (ResourceNotFoundException) when calling the TagResource operation: ResourceArn 'arn:scylla:alternator:alternator_alternator_Test_ 1758532308880:scylla:table/alternator_Test_1758532308880x' not found This is the same error type (ResourceNotFoundException) that DynamoDB returns in that case - and a more helpful error message. This patch also includes a regression test that checks the error type in this case. The new test fails on Alternator before this patch, and passes afterwards (and also passes on DyanamoDB). Signed-off-by: Nadav Har'El <nyh@scylladb.com> Closes scylladb/scylladb#26179
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.