THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
| Profile Name | Description |
|---|---|
| java-mms.0-10 | Test profile to use AMQP 0-10, the Memory Message Store and the Java Broker for system testing |
| java-mms.0-9-1 | Test profile to use AMQP 0-9-1, the Memory Message Store and the Java Broker for system testing |
| java-mms.0-9 | Test profile to use AMQP 0-9, the Memory Message Store and the Java Broker for system testing |
| java-bdb.0-10 | Test profile to use AMQP 0-10, the BDB Message Store and the Java Broker for system testing |
| java-bdb.0-9-1 | Test profile to use AMQP 0-9-1, the BDB Message Store and the Java Broker for system testing |
| java-bdb.0-9 | Test profile to use AMQP 0-9, the BDB Message Store and the Java Broker for system testing |
| java-dby-mem.0-10 | Test profile to use AMQP 0-10, the Derby In-Memory Message Store and the Java Broker for system testing |
| java-dby-mem.0-9-1 | Test profile to use AMQP 0-9-1, the Derby In-Memory Message Store and the Java Broker for system testing |
| java-dby-mem.0-9 | Test profile to use AMQP 0-9, the Derby In-Memory Message Store and the Java Broker for system testing |
| java-dby.0-10 | Test profile to use AMQP 0-10, the Derby Message Store and the Java Broker for system testing |
| java-dby.0-9-1 | Test profile to use AMQP 0-9-1, the Derby Message Store and the Java Broker for system testing |
| java-dby.0-9 | Test profile to use AMQP 0-9, the Derby Message Store and the Java Broker for system testing |
| java-json.0-9-1 | Test profile to use AMQP 0-9-1, the Json Configuration Store Derby Message Store and the Java Broker for system testing |
| java-json.0-10 | Test profile to use AMQP 0-10, the Json Configuration Store Derby Message Store and the Java Broker for system testing |
| cpp | Test profile to use AMQP 0-10 and the C++ for system testing |
| apache-release | Release profile for performing Apache software releases |
| dependency-check | Dependency check to validate project licensing ahead of release |
| joramtests | Profile used to execute the Joram JMS test suite (more below). |
Configuring Eclipse
In order to allow your maven project to be viewed/edited in Eclipse IDE use the following commands to generate the IDE config files (*.classpath, .settings etc):
...
| Location | Description | Notes | |
|---|---|---|---|
| */target/ | Packaged build artifacts | JAR, WAS, ZIP etc as well as any release specific artifacts specified in assembly files i.e. release tars | |
| */target/surefire-reports/ | Output from surefire plugin test runs | Logs from unit/system test and Surefile summary | Logs files generated by the tests (named TEST-<test-class>-<test-method>.txt). Surefire summary has an .xml extension.Test config XML files and test result output TXT files |
| */target/qpid-broker/${project.version}/qbtc-test-outputconfig/ | System test broker output | Broker configuration used by the System tests | Broker configuration used by the System Legacy broker output for the system tests |
| */taget/site/ | Maven site output | Maven reports generated in HTML format i.e. test reports, code coverage etc | |
| */target/staging/ | The staged maven site | Local attempt to generate the full maven site |
...
Execute the unit tests and then produce the code coverage report
mvn test jacoco:report
Joram JMS Testsuite
The Joram JMS Testsuite is integrated into the Maven build but is disabled by default. It allows the Joram JMS test suite to executed, using the specified Qpid JMS client, against the Java Broker. The Java Broker must be running already.
The following clients are supported:
- qpid-jms-client - Qpid Client AMQP 1.0
- qpid-amqp-1-0-client-jms - the proof of concept Qpid Client AMQP 1.0 (development ceased 0.32)
- jms-client for AMQP protocols 0-8..0-10
To use the test suite, first configure the Java Broker to permit HTTP basic-authentication, then run the following command:
mvn -f joramtests/pom.xml integration-test -Djoramtests=<jms client identifier>where <jms client identifier> is one of: qpid-jms-client, qpid-amqp-1-0-client-jms, jms-client-0-9, jms-client-0-10.
The Maven failsafe plugin will run the tests. Unit output is produced in joram-tests/target/failsafe-reports and the log from the client is written to joramtests/target/joramtest.log.
To run a particular test use the failsafe plugin property -Dit.test:
mvn -f joramtests/pom.xml integration-test -Djoramtests=qpid-amqp-1-0-client-jms -Dit.test=ConnectionTest