2ef0db0a6b
I want to add an upgrade test under the topology suite. To work, it will have to know the path to the tested Scylla executable, so that it can switch the nodes to it. The path could be passed by various means and I'm not sure which what method is appropriate. In some other places (e.g. the cql suite) we pass the path via the `SCYLLA` environment variable and this patch follows that example. `PythonTestSuite` (parent class of `TopologySuite`) already has that variable set in `self.scylla_env`, and passes it around. However, `TopologySuite` uses its own `run()`, and so it implicitly overrides the decision to pass `self.scylla_env` down. This patch changes that, and after the patch we apply the `self.scylla_env` to the environment for topology tests. This might has some unforeseen side effects for coverage measurement, because AFAICS the (only) other variable in `self.scylla_env` is `LLVM_PROFILE_FILE`. But topology tests don't run Scylla executables themselves (they only send command to the cluster manager started externally), so I figure there should be no change.
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.