Re: junit Questions

[Scott Goldstein]

I've done some research on writing my own JUnit formatter in order to print all
of the results at the end of the batch test.  It appears that each .class or
.java file in a batch test is treated as a single JUnitTest instance.  Each
JUnitTest instance represent a test suite.  After a test suite ends, the
Formatter.endTestSuite() method is called to print the results.

I could write a formatter that continues to maintain the results of all test
suites (i.e. the entire batch test) in memory and print it all out at the very
end.  Unfortunately, I don't see any way to signal the formatter that the
JUnitTask has ended.  Is there a way to do this?

Thank you for the help.

Scott

Erik Hatcher wrote:

 - Original Message -
 From: Scott Goldstein [EMAIL PROTECTED]
  I have two questions regarding the junit tasks.
 
  1.  When running a batch test, is it at all possible to print all of the
  results at the end of the test.  I'm interested in printing the number of
  successful tests and what errors/failures occurred.java (i.e. something
  similar to the results displayed when using junit.textui.TestRunner).




--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]

Re: junit Questions

[Erik Hatcher]

- Original Message -
From: Scott Goldstein [EMAIL PROTECTED]
 I have two questions regarding the junit tasks.

 1.  When running a batch test, is it at all possible to print all of the
 results at the end of the test.  I'm interested in printing the number of
 successful tests and what errors/failures occurred.java (i.e. something
 similar to the results displayed when using junit.textui.TestRunner).

How about using junitreport to generate an HTML report?  That gives a
summary page with the stats you are looking for.

 2.  I'm come across a number of occassions in version 1.4 when the junit
task
 froze.  The place it froze was not consistent.  Has anyone else
experienced
 this?  Is there an error log somewhere that I could look at?

Best thing to do when experiencing weird stuff with Ant is to use the -debug
switch and see if there is anything displayed in that output that can give
clues.  Are your tests doing anything out of the ordinary?

Erik



--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]