On Tue, 26 Sep 2006, Matt Benson <[EMAIL PROTECTED]> wrote:
> When writing antunit tests, one cannot use the
> log-inspection assertions or the new au:logcontent
> resource outside the context of an AntUnit test. This
> is understandable/unavoidable,
Is it? We could add a task that registers a
Hopefully you get the idea.
Uh, not really ;-)
How crazy is this?
Not crazy to me, because I implemented this once in the past on top of
JUnit (if I half-undertood you). I had a custom TestRunner that
accepted an additional -m testMethod switch. It slowly died when the
new version of JUnit c
When writing antunit tests, one cannot use the
log-inspection assertions or the new au:logcontent
resource outside the context of an AntUnit test. This
is understandable/unavoidable, but it does mean that
there are some tests that cannot be developed with
'ant -f ...'. Obviously you could write n
