[
https://issues.apache.org/jira/browse/QPID-7665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy closed QPID-7665.
----------------------------
Resolution: Fixed
The implementation looks good to me. We will add more tests for AMQP 1.0 later
and consider separation of AMQP 1.0 implementation from broker-core but those
are the tasks for other JIRAs. Thus, closing this JIRA
> Protocol system test suite for AMQP 1.0
> ---------------------------------------
>
> Key: QPID-7665
> URL: https://issues.apache.org/jira/browse/QPID-7665
> Project: Qpid
> Issue Type: Improvement
> Components: Java Tests
> Reporter: Keith Wall
> Fix For: qpid-java-broker-7.0.0
>
>
> We need a 'protocol system test suite' - one that allows us to send AMQP 1.0
> frames to the Broker and make assertions about the response frames. This
> will be used to ensure that the Broker conforms to AMQP 1.0. I envisage a
> series of small test cases, each dedicated to one aspect of AMQP 1.0
> conformance.
> It would also be nice if we had a way to link test cases back to the spec, so
> we can automatically visualise coverage. Perhaps some kind of annotation?
> Whilst this work will focus on AMQP 1.0, if we had the same ability for the
> older protocols, this would allow us to prune many overall elaborate system
> tests.
> We need a test framework which would allow creation of tests which would be
> sending the AMQP performatives over TCP and receiving and asserting broker
> responses.
> The framework should satisfy the following requirements:
> * It should allow running tests against other AMQP brokers
> * The framework should encapsulate starting/stopping of broker and queue
> creation/deletion under special interface(s) which can be implemented by the
> Broker developers in order to run tests against different Broker
> implementations
> * Tests should be able to start and stop broker if required or configured
> * Tests should be able to generate AMQP performatives and assert received
> peer's AMQP performatives
> * The framework should allow using other transport than TCP if required
> * The framework should be based on AMQP 1.0 implementation of Java Broker
> (The AMQP 1.0 implementation of Java Broker can be refactored into a module
> not depending from broker-core. The module should provide a low-level AMQP
> API allowing to create and parse AMQP frames and expose AMQP API for
> Connections, Sessions, Links, etc ).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
