ee0e7a7adf
This patch adds test/cql-pytest tests which verify that all CQL operations that shouldn't be allowed on a materialized view, actually aren't: * All operations writing to a table - INSERT, UPDATE, BATCH, DELETE, and TRUNCATE - should be rejected when asked to operate on a view. * All operations with "TABLE" in their name (DROP TABLE, ALTER TABLE, DESC TABLE) should be rejected on a view - the ".. MATERIALIZED VIEW" operation should be used instead. * A materialized view cannot get materialized views or indexes of its own. All tests pass on Cassandra (Cassandra 4 or above is needed for the "DESC" test), and all but one pass on Scylla - Scylla does allow "DESC TABLE" on a materialized view, unlike Cassandra. I opened an issue to track that difference: Refs #21026 Signed-off-by: Nadav Har'El <nyh@scylladb.com> Closes scylladb/scylladb#21028
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.