ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 35073] New: - JUnit test runner outputs to stdout on failures, instead of relying on formatter
Date Wed, 25 May 2005 22:24:33 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=35073>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=35073

           Summary: JUnit test runner outputs to stdout on failures, instead
                    of relying on formatter
           Product: Ant
           Version: 1.6.4
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Optional Tasks
        AssignedTo: dev@ant.apache.org
        ReportedBy: apache.org@alias.byzantine.no


On test failures, the JUnit test runner outputs lines such as this:

TEST com.example.Foo FAILED

It does this regardless of which formatter has been set. There's no way to
disable the behaviour.

This means that when you make an effort to plug in a formatter which produces
good-looking output, you also get the "TEST" stuff cluttering your output.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Mime
View raw message