Stefan Bodewig wrote:
If there is enough interest we could certainly still create a 1.6
compatible branch.
From this posting I got a reply from Paul King, who explained that
similar asserts are being used in WebTest project and that he would
be interested to learn the outcome of this discussion.
Paul is subscribed here as well, haven't seen him chime in, yet.
It is mostly a question of how much ongoing work it would take when we
add new features to AntUnit. Which parts of AntUnit would you use?
Only the assertions or the tasks and listeners as well?
I am listening but still pondering what the best path is before
making further suggestions. WebTest has a focus on Acceptance
Testing and has more extensive reporting than e.g. JUnit.
AntUnit currently has sufficient listener capability and
infrastructure to align it closely with JUnit-style tests.
WebTest's steps are just Ant Tasks with a context. So it would
not be impossible to make WebTest's verification steps AntUnit
assertions with a context. It would be an interesting way to
move forward but maybe it isn't critical at the moment.
See the thread 'Property expansion notification interesting?'
over the last few weeks to see one of the things we would need
to solve first.
I'll keep pondering,
Paul.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
