----- Original Message ----- From: "Matt Seibert" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, May 23, 2002 12:48 PM Subject: AXIS Test Restructuring
> Prompted by a note from Steve Loughran this morning, and being budged by > some of my teammates, I am putting in that I am willing to chip in on the > restructuring. > > Steve, > > I have been working for about two weeks on the re-structuring of the test/ > and samples/ compilation / execution process, being able to componentize > and instantiate any given test singularly, and making the system easier to > maintain and, hopefully, a little better organized. > > I would like to speak with you about how I foresee the build/execution of > the test and samples structures changing in correlation to how you think > the overall build process should be changing. I would very much like for > you to review my proposed changes, as well as see what your proposals are, > so as to produce the best possible output. > > Please feel free to ping me back. I am new to the axis community, and am > not quite sure how we all go about sharing information...... I am new to axis too, but worked on other apache projects. we can discuss stuff on the dev mail list as it stores the discussion and lets other people get involved; it "eliminates surprises" So, write up your proposed changes and see where you think we should go. Me, I think that as well as cleaning up the build process, we need to work on the test suite so it runs more like a big fat junit test; you run all the tests and get back an XML file of what worked, what didnt...to date the way we go right now the first failure seems to stops the run. I dont know quite how to do that (yet), though I have some definate ideas, which revolve around how ant's unit tests run build files inside junit, but with a bit more template driven generation of build files, and maybe even the junit test cases to call them. -steve
