85da03c88d
Add additional BatchWriteItem tests (some failing): - `test_streams_batchwrite_no_clustering_deletes_non_existing_items` `test_streams_batchwrite_no_clustering_deletes_existing_items` - those tests pass, we add it here for completness, as non clustering tables trigger different paths. - `test_streams_batchwrite_into_the_same_partition_deletes_existing_items` - failing test, that checks combinations of puts and deletes in a single batch write (so for example 3 items, 2 puts and 1 delete). - `test_streams_batchwrite_into_the_same_partition_will_report_wrong_stream_data` - failing simple test. Tests fail, because current implementation, when writing cdc log entries will squash all changes done to the same partition together. The data is still there, but when GetRecords is called and we parse cdc log entries, we don't correctly recover it (see issue #28439 for more details).
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.