cc308bd0cc
We have a test, test/alternator/test_gsi.py::test_update_gsi_pk which created a GSI whose *partition key* was a regular column in the base table, and exercised various elaborate updates requiring adding, updating and deleting of rows from the materialized view. In this patch, we add another similar test case, just for a *clustering key*. Both these tests are important regression tests - when we later reimplement GSI we'll want to verify that none of the complex update scenarios got broken (and indeed, some broken code did break these tests). 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++ 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.