In commit8bf62a0we introduced a test/pytest.ini which affects every run of pytest in the project. One specific line in that file log_cli = true Overrides pytest's standard CLI output, which is traditionally short unless the "-v" (verbose) option is used, to be always long and spammy. There is absolutely no reason to do that - if the user wants to run "pytest -v", they can do that - it doesn't need to be the default. Moreover, as https://docs.pytest.org/en/stable/how-to/logging.html explains, the "log_cli = true" was added in pytest 3.4 to revert to pytest 3.3 behavior that "community feedback" showed was NOT LIKED. Why would we want to revert to behavior that wasn't liked? After this patch, which removes that line, the output of commands like cd test/cqlpy; pytest return to what they used to be before commit8bf62a0and what the pytest developers intended. Users who like verbose output can use "pytest -v". Fixes #21712 Signed-off-by: Nadav Har'El <nyh@scylladb.com> Closes scylladb/scylladb#21717
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.