98a8ae0552
This patch adds extensive functional tests for the DynamoDB multi-item transactions feature - the TransactWriteItems and TransactGetItems requests. We add 43 test functions, spanning more than 1000 lines of code, covering the different parameters and corner cases of these requests. Because we don't support the transaction feature in Alternator yet (this is issue #5064), all of these tests fail on Alternator but all of them were tested to pass on DynamoDB. So all new tests are marked "xfail". These tests will be handy for whoever will implement this feature as an acceptance test, and can also be useful for whoever will just want to understand this feature better - the tests are short and simple and heavily commented. Note that these tests only check the correct functionality of individual calls of these requests - these tests cannot and do not check the consistency or isolation guarantees of concurrent invocations of several requests. Such tests would require a different test framework, such as the one requested in issue #6350, and are therefore not part of this patch. Note that this patch includes ONLY tests, and does not mean that an implementation of the feature will soon follow. In fact, nobody is currently working on implementing this feature. Signed-off-by: Nadav Har'El <nyh@scylladb.com> Closes scylladb/scylladb#22239
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.