qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-7665) Protocol system test suite for AMQP 1.0
Date Mon, 17 Apr 2017 11:54:41 GMT

    [ https://issues.apache.org/jira/browse/QPID-7665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15971003#comment-15971003

ASF subversion and git services commented on QPID-7665:

Commit 1791686 from [~lorenz.quack] in branch 'java/trunk'
[ https://svn.apache.org/r1791686 ]

QPID-7665: [Java Broker] ensure netty is shutting down properly and remove some debug logging

> 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
> * 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

To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org

View raw message