298a0ec4de
test/cqlpy/README.md explains how to run the cqlpy tests against Cassandra, and mentions that if you don't have "nodetool" in your path you need to set the NODETOOL variable. However, when giving a simple example how to use the run-cassandra script, we forgot to remind the user to set NODETOOL in addition to CASSANDRA, causing confusion for users who didn't know why tests were failing. So this patch fixes the section in test/cqlpy/README.md with the run-cassandra example to also set the NODETOOL environment variable, not just CASSANDRA. Signed-off-by: Nadav Har'El <nyh@scylladb.com> Closes scylladb/scylladb#25051
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.