From fd1379711540c7b44234319a1418b6908607133f Mon Sep 17 00:00:00 2001 From: Ekaterina Dimitrova Date: Fri, 21 Jan 2022 17:46:41 -0500 Subject: [PATCH] Update instructions for testing with your own CCM branch --- .../source/modules/ROOT/pages/development/testing.adoc | 3 +++ 1 file changed, 3 insertions(+) diff --git a/site-content/source/modules/ROOT/pages/development/testing.adoc b/site-content/source/modules/ROOT/pages/development/testing.adoc index 6e04d5343..3eb553782 100644 --- a/site-content/source/modules/ROOT/pages/development/testing.adoc +++ b/site-content/source/modules/ROOT/pages/development/testing.adoc @@ -36,6 +36,9 @@ test Cassandra via https://github.com/riptano/ccm[CCM] verifying operation results, logs, and cluster state. Python Distributed tests are Cassandra version agnostic. They include upgrade tests. +In case you want to run DTests with your own version of CCM, please refer to requirements.txt in +https://github.com/apache/cassandra-dtest[apache/cassandra-dtest] how to do it. + The recipes for running those tests can be found in the cassandra-builds repository https://github.com/apache/cassandra-builds/tree/trunk/build-scripts[here]. Running full test suites locally takes hours, if not days. Beyond running specific tests you know are applicable, or are failing, to the work at hand, it is recommended to rely upon the project's https://cassandra.apache.org/_/development/ci.html[Continuous Integration systems]. If you are not a committer, and don't have access to a premium CircleCI plan, ask one of the committers to test your patch on the project's https://ci-cassandra.apache.org/[ci-cassandra.apache.org].