aca5284b13
Add missing tests for per-table Alternator latency metrics to ensure recent per-table latency accounting is actually validated. Changes in this patch: Refactor latency assertion helper into check_sets_latency_by_metric(), parameterized by metric name. Keep existing behavior by implementing check_sets_latency() as a wrapper over scylla_alternator_op_latency. Add test_item_latency_per_table() to verify scylla_alternator_table_op_latency_count increases for: PutItem, GetItem, DeleteItem, UpdateItem, BatchWriteItem, and BatchGetItem. This closes a test gap where only global latency metrics were checked, while per-table latency metrics were not covered. Signed-off-by: Amnon Heiman <amnon@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++ 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.