|tagger||Kim van der Riet <firstname.lastname@example.org>||Fri Jun 29 12:57:15 2018 -0400|
Proposed release: 0.2.0-rc1
|author||Kim van der Riet <email@example.com>||Fri Jun 29 12:08:27 2018 -0400|
|committer||Kim van der Riet <firstname.lastname@example.org>||Fri Jun 29 12:08:27 2018 -0400|
QPIDIT-125: Changed version number in the pom.xml file
This directory contains the Qpid Proton Client API test suite.
All files in this directory are under the Apache License - see LICENSE for details.
Source code may be obtained from Apache git server https://git-wip-us.apache.org/repos/asf/qpid-interop-test.git
A quickstart guide for building and using this test suite is contained in QUICKSTART. Detailed documentation for adding tests and using them are contained in the docs directory.
Issues are tracked in the Apache JIRA at https://issues.apache.org/jira/browse/QPIDIT
Support may be obtained from the qpid-users mailing list email@example.com.
See the QUICKSTART file for building, installing and running instructions.
A detailed description of this process is contained in the docs directory. The very short version of this is as follows:
Write a pair of client programs using the client API under test. The first is a sender which reads the following from the command-line:
<broker address> <amqp type> <JSON string: test values> ...
and is responsible for sending messages containing the test values each in a single message in the appropriate AMQP type format.
The second client program is a receiver, and must read the following from the command-line
<broker address> <amqp type> <JSON string: num messages>
and is responsible for receiving messages from the broker and printing the bodies of the received messages appropriately decoded for type . The printed output will be a JSON string containing the identical structure to that sent to the send shim, but containing the received values.
Add a subclass for this client in
src/py/qpid-interop-test/types/simple_type_test.py derived from class
Shim and which overrides
ENV (as needed),
RECEIVE must point to the two clients written in step 1 above.
Add an instance of your new shim class to
SHIM_MAP keyed against its name.