e4bc97349c
Issue #8203 describes a bug in a long scan which returns a lot of empty pages (e.g., because most of the results are filtered out). We have two cql-pytest test cases that reproduced this bug - one for a whole-table scan and one for a single-partition scan. It turned out that the bug was not in the Scylla server, but actually in the Python driver which incorrectly stopped the iteration after an empty page even though this page did contain the "more pages" flag. This driver bug was already fixed in the Datastax driver (see6ed53d9f70, and in the Scylla fork of the driver:1d9077d3f4So in this patch we drop the XFAIL, and if the driver is not new enough to contain this fix - the test is skipped. Since our Jenkins machines have the latest Scylla fork of the driver and it already contains this fix, these tests will not be skipped - and will run and should pass. Developers who run these tests on their development machine will see these tests either passing or skipped - depending on which version of the driver they have installed. Closes #8203 Signed-off-by: Nadav Har'El <nyh@scylladb.com> Message-Id: <20211011113848.698935-1-nyh@scylladb.com>
Single-node functional tests for Scylla's CQL features.
These tests use the Python CQL library and the pytest frameworks. By using an actual CQL library for the tests, they can be run against any implementation of CQL - both Scylla and Cassandra. Most tests - except in rare cases - should pass on both, to ensure that Scylla is compatible with Cassandra in most features.
To run all tests against an already-running local installation of Scylla
or Cassandra on localhost, just run pytest. The "--host" and "--port"
can be used to give a different location for the running Scylla or Cassanra.
The "--ssl" option can be used to use an encrypted (TLSv1.2) connection.
More conveniently, we have two scripts - "run" and "run-cassandra" - which do all the work necessary to start Scylla or Cassandra (respectively), and run the tests on them. The Scylla or Cassandra process is run in a temporary directory which is automatically deleted when the test ends.
"run" automatically picks the most recently compiled version of Scylla in
build/*/scylla - but this choice of Scylla executable can be overridden with
the SCYLLA environment variable. "run-cassandra" defaults to running the
command cassandra from the user's path, but this can be overriden by setting
the CASSANDRA environment variable to the path of the cassandra script,
e.g., export CASSANDRA=$HOME/apache-cassandra-3.11.10/bin/cassandra.
A few of the tests also require the nodetool when running on Cassandra -
this tool is again expected to be in the user's path, or be overridden with
the NODETOOL environment variable. Nodetool is not needed to test
Scylla.
Additional options can be passed to "pytest" or to "run" / "run-cassandra" to control which tests to run:
- To run all tests in a single file, do
pytest test_table.py. - To run a single specific test, do
pytest test_table.py::test_create_table_unsupported_names. - To run the same test or tests 100 times, add the
--count=100option. This is faster than runningrun100 times, because Scylla is only run once, and also counts for you how many of the runs failed. Forpytestto support the--countoption, you need to install a pytest extension:pip install pytest-repeat
Additional useful pytest options, especially useful for debugging tests:
- -v: show the names of each individual test running instead of just dots.
- -s: show the full output of running tests (by default, pytest captures the test's output and only displays it if a test fails)