alorma
02/24/2021, 2:42 PMcom.infojobs.app.base.datasource.cachedb.DateConverterTest > should convert Instant objects FAILED
org.opentest4j.AssertionFailedError: ▼ Expect that 2021-02-24T14:04:22.023Z:
✗ is equal to 2021-02-24T14:04:22.023564Z
found 2021-02-24T14:04:22.023Z
Wouldn't be better to show like this:
com.infojobs.app.base.datasource.cachedb.DateConverterTest > should convert Instant objects FAILED
org.opentest4j.AssertionFailedError:
▼ Expect that 2021-02-24T14:04:22.023Z:
✗ is equal to 2021-02-24T14:04:22.023564Z
found 2021-02-24T14:04:22.023Z
????robfletcher
02/24/2021, 3:52 PMchristophsturm
02/24/2021, 5:07 PMalorma
02/24/2021, 5:09 PM/n
to the start of strikt errorchristophsturm
02/24/2021, 5:09 PMalorma
02/24/2021, 5:13 PMrobfletcher
02/24/2021, 5:37 PMchristophsturm
02/26/2021, 3:18 PMalorma
02/26/2021, 4:54 PMrobfletcher
02/26/2021, 4:55 PMisEqualTo
being used. If you’re using another assertion, e.g. hasLength
the assertion output wouldn’t include the actual value of the string, so it’s useful to have it in the “expect that…” partchristophsturm
02/26/2021, 8:18 PMalorma
04/16/2021, 9:00 AMrobfletcher
04/16/2021, 2:09 PMchristophsturm
04/26/2021, 7:02 AM