This is an automated email from the ASF dual-hosted git repository.
edimitrova pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra-dtest.git
The following commit(s) were added to refs/heads/trunk by this push:
new a082ee1 Remove references to run_dtests.py in the README Authored by
Matt Fleming; reviewed by Michael Semb Wever and Ekaterina Dimitrova for
CASSANDRA-16623
a082ee1 is described below
commit a082ee1cac951e0d41503cae54454e81198d37ef
Author: Matt Fleming <[email protected]>
AuthorDate: Wed Apr 21 14:32:22 2021 +0100
Remove references to run_dtests.py in the README
Authored by Matt Fleming; reviewed by Michael Semb Wever and Ekaterina
Dimitrova for CASSANDRA-16623
---
README.md | 14 +++-----------
1 file changed, 3 insertions(+), 11 deletions(-)
diff --git a/README.md b/README.md
index 4c6fe7d..b7efc05 100644
--- a/README.md
+++ b/README.md
@@ -52,12 +52,9 @@ path to success as it provides common base setup across
various configurations.
Usage
-----
-The tests are executed by the pytest framework. For convenience, a wrapper
``run_dtests.py``
-is included with the intent to make starting execution of the dtests with sane
defaults as easy
-as possible. Most users will most likely find that invoking the tests directly
using ``pytest``
-ultimately works the best and provides the most flexibility.
-
-Pytest has a great [Usage and
Invocations](https://docs.pytest.org/en/latest/usage.html) document which is a
great place to start for basic invocation options when using pytest.
+The tests are executed by the pytest framework which includes a helpful [Usage
and
+Invocations](https://docs.pytest.org/en/latest/usage.html) document which is a
great place to start
+for basic invocation options when using pytest.
At minimum,
@@ -84,11 +81,6 @@ environment variable (that still will have precedence if
given though).
Existing tests are probably the best place to start to look at how to write
tests.
-The ``run_dtests.py`` included script is simply a wrapper to make starting the
dtests
-with sane defaults as simple as possible. If you just want to run the tests
and do nothing more,
-this is most likely the most easy place to start; however, anyone attempting
to do active development
- and testing will find invoking pytest directly to be likely the best option.
-
Each test spawns a new fresh cluster and tears it down after the test. If a
test fails, the logs for the node are saved in a `logs/<timestamp>` directory
for analysis (it's not perfect but has been good enough so far, I'm open to
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
