b9b778054a
* Add `--max-failures` flag to test.py, which will stop the execution after number of failures * Helps with "fails-fast" approach and can be used to improve CI speed, especially the 100times run * Adds the number of cancelled tests to both summary and junit xml. I did not include them in boost, since it does not contain any statistics. * Removes unnecessary list creation in test.py * Completely unrelated change, but it is small enough that I feel it can be included as part of this one. If this is an issue I can create separate PR for it * Add `Test.started` property * Helps with determining the current status of the Test and differentiating cancelled/not started tests. * Add `Test.failed` and `Test.did_not_run` read-only computed properties * Helper methods to determine status, instead of using `Test.success`, which does not tell the entire story * Fix `ScyllaClusterManager.stop()` method, so it doesn't fail when ran multiple times * This happens when tasks are cancelled, not sure yet why, it almost certainly non-wanted behaviour but this behaviour was already there and with this fix it no longer causes errors I will use backport/None for now as it is a new feature. Fixes https://github.com/scylladb/qa-tasks/issues/1714 Closes scylladb/scylladb#21098 * github.com:scylladb/scylladb: test.py: Add option to fail after number of failures test.py: Add started, failed and did_not_run properties to Test test.py: Remove unnecessary list creation test: lib: Fix ScyllaClusterManager.stop()
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.