Hello,
--- Brian Agnew <[EMAIL PROTECTED]> wrote:
> I was thinkking on a similar line, but thought of the following:
>
> Use custom Javadoc tags for each method, indicating testability, parameters,
> expected results, messages etc. We then have a custom Javadoc doclet. When we
> want a TestCase we run Javadoc with the custom doclet over the code and
> create
> the test cases automatically.
>
> This can be made part of the build. The test parameters etc. are tied
> directly
> to the code, so it's pretty obvious what's going on.
>
> Brian
Using custom javadoc tags seems a great idea. Because that would give a great
control to the programmer over the code he writes the same way he writes doc.
for his code.
But one thing I would feel with regard to both what Brian and Dharminder's
comments is that while these enterprising questions are most welcome, this
question would better be posted to the JUnit mailing list we could discuss it
more about it there. Because Cactus is built on top of JUnit, I feel this
Javadoc integration has to be done on JUnit. Am I going somewhere wrong here?
Thanks.
Karthik Kumar.
__________________________________________________
Do You Yahoo!?
Listen to your Yahoo! Mail messages from any phone.
http://phone.yahoo.com
