As a starting point and for 0_10 testing purpose I was thinking about changing the (pure JMS) tests from the client module so that to run them either against an in_VM broker or against a remote broker (we can set some maven parameters). The default behavior will obviously be to use an in-VM broker. I am also adding some 0_10 specific test that will just not run against an 8_0 (in-VM or remote) broker.
Note that some of those tests (the one I am adding for example) are jms specific. We may want to move them in /trunk/qpidtests later on. Or maybe a better idea is to move them in /trunk/qpidtests right now. What do you think? Arnaud On Wed, 2007-09-26 at 19:36 +0100, Robert Greig wrote: > On 26/09/2007, Rupert Smith <[EMAIL PROTECTED]> wrote: > > Would anyone object if test framework under systests + integration tests + > > perftests + 'Immediate/MandatoryMessageTest', were merged with Arnauds pure > > JMS changes, and put under: > > > > /trunk/qpidtests ? > > > > This code will have no Qpid dependencies, except that there will need to be > > an interface created for an extension point for AMQP specific stuff (like > > immediate/mandatory flags). One nicety of this, is that the entire test > > framework will also be able to be run over other JMS products, for > > comparative testing. > > From that description it sounds like a good idea. > > RG
