12516b0861
Currently all scylla-tools assume that the operation/command is in argv[1]. This is not very flexible, because most programs allow global options (that are not dependent on the current operation/command) to be passed before the operation name on the command line. Notably C*'s nodetool is one such program and indeed scripts and tests using nodetool do utilize this. This patch makes this more flexible. Instead of looking at argv[1], do an initial option parsing with boost::program_options to locate the operation parameter. This initial parser knows about the global options, and the operation positional argument. It allows for unrecognized positional and non-positional arguments, but only after the command. With this, any combination of global options + operation is allowed, in any order.
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++ cql-pytest - 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.