How about this. If everyone is happy that '/trunk/qpidtests' is a suitable location for version independent functional tests, lets move them there. Lets start doing this once M2 is released. That way we can make sure we capture all the wonderful tests that are being contributed at the moment. It will also mean that we might have some breathing room to help out with that effort.
On 27/09/2007, Rupert Smith <[EMAIL PROTECTED]> wrote: > > If you are going to move tests, that are suitable for running through JMS > + Qpid extensions, that is functional tests not pure unit ones, a much > better idea would be to move them to the branch independent test module, as > discussed, and as you move them, to check and merge the three possible > sources of change: M2/M2.1/trunk. > > Such fun. > > On 27/09/2007, Rupert Smith <[EMAIL PROTECTED]> wrote: > > > > On 27/09/2007, Rajith Attapattu <[EMAIL PROTECTED]> wrote: > > > > > > So we can move the current tests under client and broker over here as > > > this > > > what it does currently. > > > I hardly see a difference between the tests in client/broker and the > > > systests. > > > > > > > Sure, but moving stuff around, is a problem WRT merging. Merging is > > getting hard, so don't take a trunk only view of this. I want to be able to > > run kdiff against M2 and trunk and have it tell me accross the entire > > project what has changed. If you move stuff, I will not be able to do this. > > > >
