e2773b4a3a
test/cql-pytest/test_group_by.py has tests that verifies that requests like SELECT p,c1,c2,v FROM tbl WHERE p=0 GROUP BY p work as expected - the "GROUP BY p" means in this case that we should only return the first row in the p=0 partition. As a user discovered, it turns out that the almost identical request: SELECT * FROM tbl WHERE p=0 GROUP BY p Doesn't work the same - before the fix in the previous patch, it erroneously returned all rows in p=0, not just the first one. The test in this patch demonstrates this - it fails on Scylla 5.4, passes on Scylla 5.2 and on Cassandra - and passes when the fix from the previous patch is used. This patch includes another tiny test, to check the interaction of GROUP BY with filtering. This second test passes on Scylla - but I want it in anyway because it is yet another interaction that might break (the user that reported #16531 also had filtering, and I was worried it might have been related). Refs #16531 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++ 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.