I'm not really sure what you want to achieve, but if I really understand correctly, you need to parse your .java file and get the comments from each TestCase class and test* methods.
If you achieve to do this and you export the result as a structured XML, you can then merge your XML with the merged XML report...and process your XML with a modified stylesheet that will extract the comments. I'm not sure this is really needed though. Most of the time i'm using a self descriptive name for my test methods which are long enough to describe the intent of the test. For example: testMethodWithNameExceedingMaxSize() or such. Otherwise you end up with too much works for your tests. tests need to be small and easily understandable. It's already difficult enough not to be lazy and do tests and document tests and code. :) -- Stephane Bailliez Software Engineer, Paris - France iMediation - http://www.imediation.com Disclaimer: All the opinions expressed above are mine and not those from my company. > -----Original Message----- > From: Peter Shillan [mailto:[EMAIL PROTECTED]] > Sent: Monday, November 12, 2001 5:51 PM > To: [EMAIL PROTECTED] > Subject: JUnit/JUnitReport Question > > > Hi there, > > I have a question about JUnit/JUnitReport tasks. I was to include my > class and test method comments at the relevant place in the > JUnitReport > HTML files as if I can do this, I can read the intent of the test and > see why it failed etc. all in one place. > > As a first step, I copied the stylesheets into my own directory and > pointed to them. I don't think changing the stylesheets is the answer > though (though it would have to be done too). > > Any ideas? > > Peter. > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
