2048ac88f1
Previous way of execution repeat was to launch pytest for each repeat. That was resource consuming, since each time pytest was doing discovery of the tests. Now all repeats are done inside one pytest process. Backport for 2025.3 is needed, since this functionality is framework only, and 2025.3 affected with this slow repeats as well. Fixes: https://github.com/scylladb/scylladb/issues/25391 - (cherry picked from commitcc75197efd) - (cherry picked from commit557293995b) - (cherry picked from commit853bdec3ec) - (cherry picked from commitd0e4045103) Parent PR: #25073 Closes scylladb/scylladb#25392 * github.com:scylladb/scylladb: test.py: add repeats in pytest test.py: add directories and filename to the log files test.py: rename log sink file for boost tests test.py: better error handling in boost facade
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.