Trying to resend, since bounced. --DD
On 9/14/06, Dominique Devienne <[EMAIL PROTECTED]> wrote:
> DD opined he would
> prefer INcluding **/*-test.xml , **/*Test.xml , or
> some other known pattern to excluding support files.
> My rationale is that I expect the majority of files
> under src/tests/antunit to be antunit test files; thus
> the few exceptions = exclusions.
Well, I'm an OptIn proponent, rather than an OptOut kinda guy ;-)
Using a test suffix is consistent with the JUnit convention,
and to me simply expresses *better* what these XML files are,
i.e. they are tests. I can refer in a post to taskdef-test.xml,
thus unambiguously expressing that I'm talking about the AntUnit
test for <taskdef>.
This to me is more important that saving a few keystroke
on all the test files added. One can agree that these XML files
will be in a dir specific to AntUnit test, that most files will have
to be called tests, etc...
In fine, either convention is fine with me, but I personally think that
using a test suffix is the better alternative. --DD
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
