Skip to content

Commit 2c26a56

Browse files
author
Emile Joubert
committed
Updated Java README-TESTS
1 parent 1b59876 commit 2c26a56

File tree

1 file changed

+16
-6
lines changed

1 file changed

+16
-6
lines changed

README-TESTS

Lines changed: 16 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -32,12 +32,22 @@ one of the following in the top-level directory of the source tree:
3232
ant test-ssl
3333

3434
Note that to run the SSL tests, the RabbitMQ server should be
35-
configured to use SSL as per the SSL with RabbitMQ guide.
36-
37-
The server tests are meant to test a RabbitMQ broker. Broadly, they
38-
require a running RabbitMQ broker on the default host/port, the source
39-
code for rabbitmq-server in ../rabbitmq-server, and a test directory
40-
../rabbitmq-test. Running them manually is a tricky business.
35+
configured to use SSL as per the SSL with RabbitMQ guide. The
36+
SSL_CERTS_DIR environment variable must point to a certificate
37+
folder containing a /client/ subfolder with a client certificate
38+
and the PASSWORD variable must point to the key password. The
39+
broker must be configured to validate client certificates.
40+
41+
The server and functional tests are meant to test a RabbitMQ broker.
42+
Broadly, they require a running RabbitMQ broker on the default
43+
host/port, the source code for rabbitmq-server in ../rabbitmq-server,
44+
and a test directory ../rabbitmq-test. These folders must each
45+
contain an appropriate Makefile. The test source can be scanned for
46+
instances of "Host.executeCommand" to find required Makefile targets.
47+
48+
Clustering tests require brokers on ports 5672 and 5673. Tests that
49+
require a clustered environment will be skipped if the second broker
50+
is absent.
4151

4252
For example, to run the client tests:
4353

0 commit comments

Comments
 (0)