db21aabfb9
Problem When skip marker validation raised pytest.UsageError during collection, xdist workers could crash and the controller failed with INTERNALERROR instead of reporting a normal test failure. What changed - Kept strict validation semantics, but changed xdist worker error handling. - Detect worker context via config.workerinput and stash marker-validation errors during collection. - Fail the affected item in pytest_runtest_setup with pytest.fail(..., pytrace=False). - Non-xdist behavior stays strict: validation still raises UsageError during collection. Usage examples Invalid skip_bug payloads now produce clear per-test setup failures under xdist instead of crashing worker processes.
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.