JUnits reporting failures locally, errors on build

Jon Norman (16●3●3) | asked Mar 06 '12, 9:42 a.m.

I am running a small suite of JUnit tests in an automated build system. The JUnits are currently very simple one-line tests such as assertEquals(true, false). Just to check the JUnit logging functionality.

When I run these tests locally, I get reports of failing test cases, as I expect. When these same tests are run on the build server (using ant <junit> ) instead of failures I get errors. The error message I get is:

java.lang.AssertionError&#58; expected&#58;&lt;false&gt; but was&#58;&lt;true&gt;

	at com.ibm.dfdl.api.parser.tests.ParserTests.testToFail&#40;ParserTests.java&#58;30&#41;

The test case in question:


@Test

public void testToFail&#40;&#41;&#123;

	Assert.assertEquals&#40;false, true&#41;;

&#125;

The version of JUnit being used in the ant scripts is 4.3.1
Has anyone come across this kind of thing before? I can't think of what may be causing it.
Cheers,
Jon

One answer

Most liked answers ↑|Newest answers|Oldest answers

permanent link

Jon Norman (16●3●3) | answered Mar 07 '12, 9:39 a.m.

I have fixed the problem to a degree. Using a JUnit4TestAdapter caused the failures to be seen as errors. Looking at the JUnit ant page gave me a clue that this was the problem:

This task has been tested with JUnit 3.0 up to JUnit 3.8.2; it won't work with versions prior to JUnit 3.0. It also works with JUnit 4.0, including "pure" JUnit 4 tests using only annotations and no JUnit4TestAdapter.

The failures are now reported as errors as desired.

Your answer

Register or log in to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.

It's all about the answers!

Related questions

JUnits reporting failures locally, errors on build

One answer

Your answer