Skip to content

Update documents according to the change of test suite class name #951

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 5, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -105,7 +105,7 @@ Launch "essential" tests (takes about 10 minutes):
```
./mvnw verify -P '!setup-test-cluster' \
-Drabbitmqctl.bin=DOCKER:rabbitmq \
-Dit.test=ClientTests,FunctionalTests,ServerTests
-Dit.test=ClientTestSuite,FunctionalTestSuite,ServerTestSuite
```

Launch a single test:
Expand All @@ -125,7 +125,7 @@ system property must point to the `rabbitmqctl` program:
./mvnw verify -P '!setup-test-cluster' \
-Dtest-broker.A.nodename=rabbit@$(hostname) \
-Drabbitmqctl.bin=/path/to/rabbitmqctl \
-Dit.test=ClientTests,FunctionalTests,ServerTests
-Dit.test=ClientTestSuite,FunctionalTestSuite,ServerTestSuite
```

To launch a single test:
Expand Down
10 changes: 5 additions & 5 deletions RUNNING_TESTS.md
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ To run a subset of the test suite (do not forget to start a local RabbitMQ node)
./mvnw verify -P '!setup-test-cluster' \
-Dtest-broker.A.nodename=rabbit@$(hostname) \
-Drabbitmqctl.bin=/path/to/rabbitmqctl \
-Dit.test=ClientTests,FunctionalTests,ServerTests
-Dit.test=ClientTestSuite,FunctionalTestSuite,ServerTestSuite
```

The test suite subset does not include TLS tests, which is fine for most
Expand All @@ -50,7 +50,7 @@ To run the tests against the NIO connector, add `-P use-nio` to the command line
./mvnw verify -P '!setup-test-cluster',use-nio \
-Dtest-broker.A.nodename=rabbit@$(hostname) \
-Drabbitmqctl.bin=/path/to/rabbitmqctl \
-Dit.test=ClientTests,FunctionalTests,ServerTests
-Dit.test=ClientTestSuite,FunctionalTestSuite,ServerTestSuite
```

For details on running specific tests, see below.
Expand All @@ -67,7 +67,7 @@ top-level directory of the source tree:
./mvnw verify -P '!setup-test-cluster',use-nio \
-Dtest-broker.A.nodename=rabbit@$(hostname) \
-Drabbitmqctl.bin=/path/to/rabbitmqctl \
-Dit.test=ClientTests
-Dit.test=ClientTestSuite
```

* To run the functional tests:
Expand All @@ -76,7 +76,7 @@ top-level directory of the source tree:
./mvnw verify -P '!setup-test-cluster',use-nio \
-Dtest-broker.A.nodename=rabbit@$(hostname) \
-Drabbitmqctl.bin=/path/to/rabbitmqctl \
-Dit.test=FunctionalTests
-Dit.test=FunctionalTestSuite
```

* To run a single test:
Expand All @@ -103,7 +103,7 @@ Launch the tests:
```
./mvnw verify -P '!setup-test-cluster' \
-Drabbitmqctl.bin=DOCKER:rabbitmq \
-Dit.test=ClientTests,FunctionalTests,ServerTests
-Dit.test=ClientTestSuite,FunctionalTestSuite,ServerTestSuite
```

Note the `rabbitmqctl.bin` system property uses the syntax
Expand Down