ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 43892] - org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner returns incorrect error code
Date Wed, 26 Dec 2007 15:32:57 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=43892>.
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=43892





------- Additional Comments From mfv123@hotmail.com  2007-12-26 07:32 -------
We're experiencing this as well. Our issue is not with the haltonerror or
haltonfailure attributes since we use the errorproperty and  failureproperty
attributes. If either get set, we fail the build after creating a <junitreport>.

In the system output and in the junit report Ant is reporting failures and
errors as Errors (Ant 1.7.0 with JUnit 4.4).

For the following sample test class, Ant reports 3 tests, 0 Failures, 2 Errors
rather than the expected 1 Failure, 1 Error.

public class SampleTest
{
    public static junit.framework.Test suite() { return new
JUnit4TestAdapter(SampleTest.class); }

    @Test
    public void willPass() { assertTrue(true); }

    @Test
    public void willFail() { assertTrue(false); }

    @Test
    public void willError() { throw new RuntimeException("oops"); }
}

-- 
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.

Mime
View raw message