DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20194>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20194 PlainJUnitResultFormatter produces poor output Summary: PlainJUnitResultFormatter produces poor output Product: Ant Version: 1.5.3 Platform: Sun OS/Version: Solaris Status: NEW Severity: Normal Priority: Other Component: Optional Tasks AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] The results of a failing JUnit test run from ANT are poor. The Ant JUnit task formatter produces the following: Testcase: testAccessibleComponent3 took 0.474 sec FAILED TerminalAccessibleComponent.getAccessibleAt() NYI junit.framework.AssertionFailedError: TerminalAccessibleComponent.getAccessibleAt() NYI at bean.accessibility.Base.testAccessibleComponent3(Base.java:116) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at support.EnhancedTestCase.runTest(EnhancedTestCase.java:25) Testcase: testAccessibleComponent3Testcase: testChildren1 took 0.025 sec It is the last line of this that is problematic. Basically, when a test fails, there is a missing newline from the end of its output. The result is that the start of the output of the next test is put on the same line. This results in output that is *very* hard to read.
