I think my take, is to make sure everyone understands what is already there, and is re-awarenessed about some stuff that has already been discussed. Particularly point 3, as how to automate this stuff, at least the interop test part of it, has already been discussed and recorded in the interop test spec. It has never been acted upon though. Worth reading and thinking about what is there.
Also, element 5 from Arnauds list: 5) make sure that the sys tests are run with the build Already done. I don't want unnecessary duplication of test code, or duplication of effort (there is already plenty in the tests, I think there are at least a few in-vm base classes already, for example). Another thing that might help. Rob, is it ok to put our test instructions page onto the Apache Wiki, after carefully reading through it to make sure we don't leak anything that should not be on Apache? On 27/09/2007, Carl Trieloff <[EMAIL PROTECTED]> wrote: > > > Long thread, -- what are the goals / what is my take away from the thread. > > 1.) to be able to run all the applicable tests from Java against both > brokers > 2.) to be able to run then against M2 and 0-10 implementations > 3.) to be able to automate the running of the above two points. > 4.) to isolate the tests that are Java Broker specific (unit) so the > above can be achieved. > > Something like we have achieved in python would be my ideal. The more > tests we cross run, the more issues we will find before our users find > them! > > I think the question/ core of the discussion is what are the pragmatic > steps to > achieve this? > > Carl. > > >
