Marnie McCormack wrote:
Hi Rafi,
Do the python and ruby tests include the kind of simple interop stuff that
Rupert's been working on for the other implementations ?
Are you referring to the kinds of tests described here?
http://cwiki.apache.org/confluence/display/qpid/Interop+Testing+Specification
I'm afraid I haven't been following that discussion closely. Based on my
quick read it looks like they do test the kinds of things outlined on
that page, e.g. basic publish and consume. Most of the tests, however,
are focused on detailed broker behavior, not interop between different
kinds of clients.
Alan or Gordon may be able to answer your question better.
--Rafael
Thanks & Regards,
Marnie
On 5/25/07, Rafael Schloming <[EMAIL PROTECTED]> wrote:
Kevin Smith wrote:
> Robert Godfrey wrote:
>> Anyone want to volunteer to take on the Python or Ruby?
>>
>> -- Rob
>
> I might, depending on what's involved. Could someone spell out what
> needs to be done here?
Code-wise there isn't really anything required for M2 on python or ruby.
When the question arose back when on whether or not to include ruby I
added some basic test coverage for ruby and fixed a number of issues
that came up.
Integration-wise we of course need to make sure the ruby and python
tests pass against the java and cpp brokers. I just checked the python
tests against the java broker and they all pass. There is one failure in
the ruby suite. I haven't looked at it in detail. Both test suites
should of course be run against the cpp broker as well.
--Rafael
