Arnaud, This is the right thing to do, just a shame I didn't do it that way first time around.
My only thought is, that maybe there has to be way of setting up Qpid extended JMS tests, that is, for the use of immediate/mandatory flags etc. Although, these are not really needed for perftesting. One approach might be to pull Qpid specific stuff out into a seperate class, if needed, so that the main thing is pure JMS. Also, is it really worth testing the low-level API separately to the JMS? Unless the JMS layer is doing something really time-consuming, I imagine they will be very close. Did you just copy perftests on M2 onto trunk? I hope this does not conflict when we recover those lost merges? Also, one other thing that comes to mind, is that perftests on M2 are using junit-toolkit-0.6-SNAPSHOT latestm, whereas trunk was pinned to an earlier version. You may now wish to unpin trunk, to keep up with the toolkit latest. Rupert On 23/08/07, Robert Greig <[EMAIL PROTECTED]> wrote: > > On 23/08/07, Arnaud Simon <[EMAIL PROTECTED]> wrote: > > > I am now > > updating them for using a pure JMS approach unless somebody does not > > agree (please shout if so). > > This would be great. The old topic test (which sadly appears to have > been lost?) used to support this and we did in fact run that test > again several different providers. > > RG >
