Vincent Massol wrote:
> Hi,
>
> Do you know who is deciding what tool will be used to build that struts test
> suite ? I am very eager to use J2EEUnit of course ... ! Has anyone begun
> implementing that test suite already ? Or do we have to wait for someone to
> say ok. Has there been a vote yet ? How can I help ? Is the decision taken
> on the tool ? How can I help ? Is the decision linked to the ongoing
> discussion on the library-dev mailing list ?
>
Rob Leland has volunteered to take the lead on this, but I don't know if
anything specific has happened yet.
I'm personally in favor of using J2EEUnit (and JUnit, as appropriate) for Struts
unit tests. Waiting for the shared infrastructure discussions to complete would
needlessly slow us down, although it is likely we will need to adapt to whatever
comes out of that effort (including the migration of a few pieces of Struts
technology that are easily shareable into the shared library environment
instead).
For those of us not as familiar with testing frameworks, it would be helpful to
describe how adding the test suite might affect the organization of the Struts
source code, what kinds of tests you feel we should start with, and how they
would be run. Then, it's just a matter of getting started. (Once you've got
some code ready to contribute, I can check it in ... but from there on it's best
to nominate those writing tests as committers so they can update the code base
directly.)
Although Struts features for 1.0 are frozen (I just licked the last bug reported
in the bug tracking system, so the beta will be cut today :-), I would very much
like to have at least an initial testing infrastructure and some basic tests
implemented in time for the final release.
>
> So many questions ....
> Thanks.
>
> Vincent Massol
> (Author of J2EEUnit)
Craig
