[
https://issues.apache.org/jira/browse/PROTON-215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13570605#comment-13570605
]
Ken Giusti commented on PROTON-215:
-----------------------------------
As described by Rafi on the proton mailing list:
"What's important is to test that each binding correctly renders to/from AMQP
encoded messages. If we can do this rigorously then we know they will
interoperate with each other.
I believe we can achieve this by defining a specifically formatted message that
includes every single AMQP data type. Each binding should then load a number of
alternative AMQP-encoded representations of this message from a file and check
using assertions written in the host language of the binding that each
property/object/etc is correctly rendered. We should also define tests for each
binding that authors that specifically formatted message
using that binding and verifies that the encoded representation is included as
one of the alternatives. I think this scheme provides the same coverage
as over-the-wire N-way interop tests (when it comes to data-type coverage at
least), however it is more complete as we can include representations of
this message as generated by non-proton based clients, and by virtue of not
running over the wire it would be simpler/easier to run as part of the
standard test suite, which is where this kind of test really should live rather
than being part of a performance suite that takes longer and gets
run less frequently."
> Add tests to verify AMQP 1.0 type support for all language bindings
> -------------------------------------------------------------------
>
> Key: PROTON-215
> URL: https://issues.apache.org/jira/browse/PROTON-215
> Project: Qpid Proton
> Issue Type: Test
> Components: proton-c
> Affects Versions: 0.3
> Reporter: Ken Giusti
>
> For each language binding, we need to verify that the language can encode to
> and decode from the AMQP 1.0 types.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
