Skip to content

Commit 47dc236

Browse files
Drive-by change: correct a path in RUNNING_TESTS.md
1 parent 305af33 commit 47dc236

File tree

1 file changed

+10
-3
lines changed

1 file changed

+10
-3
lines changed

RUNNING_TESTS.md

Lines changed: 10 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ For details on running specific tests, see below.
4141

4242
## Running a Specific Test Suite
4343

44-
To run a specific test suite you should execute one of the following in the
44+
To run a specific test suite, execute one of the following in the
4545
top-level directory of the source tree:
4646

4747
* To run the client unit tests:
@@ -59,7 +59,14 @@ top-level directory of the source tree:
5959
* To run a single test:
6060

6161
```
62-
./mvnw -Ddeps.dir=$(pwd)/deps/deps verify -Dit.test=DeadLetterExchange
62+
./mvnw -Ddeps.dir=$(pwd)/deps verify -Dit.test=DeadLetterExchange
63+
```
64+
65+
When running from the repository cloned as part of the [RabbitMQ public umbrella](https://github.com/rabbitmq/rabbitmq-public-umbrella),
66+
the `deps.dir` property path may have to change, e.g.
67+
68+
```
69+
./mvnw -Ddeps.dir=$(pwd)/.. verify -Dit.test=ConnectionRecovery
6370
```
6471

6572
For example, to run the client tests:
@@ -175,4 +182,4 @@ mvn verify -P '!setup-test-cluster'
175182
```
176183

177184
Note that by doing so some tests will fail as they require `rabbitmqctl` to
178-
control the running nodes.
185+
control the running nodes.

0 commit comments

Comments
 (0)