MojoFailureException AssertError using maven install

Question

I wrote a unit test that passes when I run it in Eclipse, but fails when I do "maven install".

I use JUnit 4, Mockito 1.9.5, Maven 3.0.4, JRE 1.7._51, Sunfire 2.15.

The assert that seemingly fails is:

assert string1.equals(string2);

Do you want to compare the content of the strings or ensure that they are the same in the String pool? — Spindizzy, Feb 10 '14 at 20:22
Without further source code, I would simply say the strings are not equal. — Spindizzy, Feb 10 '14 at 20:27
Sorry guys, I found the issue... The reason it passed in Eclipse was because I was using "assert". Using "assertEquals" or "assertTrue" solved the problem. — Daniil Shevelev, Feb 10 '14 at 20:37
I am going to remove all the code and error message because it is meaningless. — Daniil Shevelev, Feb 10 '14 at 20:38
Please change 'assert string1.equals(string2)' into 'assertEquals(string1, string2)'. That should give you more hints why the test fails. — Spindizzy, Feb 10 '14 at 20:39
`assert` will works too, but you need to enable assertions with -ea, and is not recommended for unit testing — MariuszS, Feb 10 '14 at 20:39

score 1 · Answer 1 · edited May 23 '17 at 12:20

1

Answer

Java keyword assert must be activated to work.

They can be activated at run-time by way of the -ea option on the java command, but are not turned on by default.

For string comparision use equals

assert string1.equals(string2)

assertEquals(string1, string2)

For best results use AssertJ - Fluent assertions for java

assertThat(string1).isEqualTo(string2);

edited May 23 '17 at 12:20

Community

answered Feb 10 '14 at 20:21

MariuszS

1

Thanks! I forgot about this... But the test still fails using maven install. – Daniil Shevelev Feb 10 '14 at 20:24
post maven version, surefire version and test code, then we can help you :) – MariuszS Feb 10 '14 at 20:24