Some tests use ant buildfiles for their work some other are coded directly against the java implementation.
I had written the tests [1] for <modified> selector directly against the api of that class. E.g. in doDelayUpdateTest(int) I use several Mock-objects. Jan [1] http://cvs.apache.org/viewcvs.cgi/ant/src/testcases/org/apache/tools/ant/typ es/selectors/ModifiedSelectorTest.java?view=markup > -----Ursprüngliche Nachricht----- > Von: Russell Gold [mailto:[EMAIL PROTECTED] > Gesendet am: Dienstag, 16. November 2004 18:34 > An: Ant Developers List > Betreff: task testing style? > > The tests I have looked at in ant appear mostly to use a semi- > functional test style: they use xml to define a task, run it, and then > check some results (which may simply be the lack of an error). I am > used to a more unit testing style, in which external classes or > subsystems are stubbed out. For example, for my dependencies task, I > want to confirm that a dependency is downloaded only if it is not > already present, which I do by mocking the fetch mechanism. Is this > approach being used somewhere in ant? Has there been any discussion of > the two approaches to testing? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
