Alan Conway commented on PROTON-215:

The approach is slightly different to that described in the first comment. The 
data is split up into separate files containing fragments of AMQP-encoded data, 
with a unit test for each fragment in each binding. This has the advantage that 
if there is a failure on one fragment, you can still verify the others 
independently, you can skip tests individually etc. With a single message 
containing all types, there's just one test and any failure means the whole 
interop test fails. This has already been useful as a couple of encode bugs 
were found and fixed in the process of creating the tests. There is also a file 
& test for a full encoded message so the message encoding is tested, we 
probably will wan to extend the tests to cover messages with various headers 
> 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
>            Assignee: Alan Conway
>              Labels: test
> 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

Reply via email to