I have a JUnit test that is as follows:
@Test
public void testToDatabaseString() {
DateConvertor convertor = new DateConvertor();
Date date = convertor.convert("20/07/1984:00:00:00:00");
String convertedDate = convertor.toDatabaseString(date);
assertEquals("to_date('20/07/1984:00:00:00:00', 'DD/MM/YYYY HH24:MI:SS')",convertedDate);
}
The test fails stating:
org.junit.ComparisonFailure: expected:<to_date('20/07/1984[00:]00:00:00', 'DD/MM/YY...> but was:<to_date('20/07/1984[ ]00:00:00', 'DD/MM/YY...>
Of particular interest is why the expected value is:
to_date('20/07/1984[00:]00:00:00',
etc...
when my string literal in the test is clearly:
"to_date('20/07/1984:00:00:00:00',
etc...
Can anyone explain this? Why does it add "[00:]"
? Appreciate the help.
The square brackets are emphasising the difference between the expected string and the actual string.
JUnit put the square brackets around the :00
to emphasise that that is what's in the expected string and not in the actual string. There are square brackets around the space in the actual string for the same reason.
JUnit is just putting the characters in your string that weren't equal in brackets to make it easier to read. Your assert looks for 4 sets of ":00" and your variable only had 3 sets.
As noted in this SO question (Java: Is assertEquals(String, String) reliable?), assertEquals just calls the .equals method on the objects that you pass it.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With