org.junit.ComparisonFailure: expected:<2016-07-05T1[3]:02:08.3220000> but was:<2016-07-05T1[7]:02:08.3220000>

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via GitHub by tabladrum
, 1 year ago
expected:<2016-07-05T1[3]:02:08.3220000> but was:<2016-07-05T1[7]:02:08.3220000>
via GitHub by wildfly-ci
, 1 year ago
expected:<[1]> but was:<[0]>
via GitHub by wildfly-ci
, 1 year ago
expected:<[1]> but was:<[0]>
via GitHub by wildfly-ci
, 1 year ago
expected:<[1]> but was:<[0]>
org.junit.ComparisonFailure: expected:<2016-07-05T1[3]:02:08.3220000> but was:<2016-07-05T1[7]:02:08.3220000>
at org.junit.Assert.assertEquals(Assert.java:115)
at org.junit.Assert.assertEquals(Assert.java:144)
at com.capitalone.dashboard.client.story.StoryDataClientImplTests.testUpdateStoryInformation_WithEpic(StoryDataClientImplTests.java:223)

Users with the same issue

82 times, 2 weeks ago
Samebug visitor profile picture
Unknown user
Once, 3 weeks ago
Samebug visitor profile picture
Unknown user
Once, 3 weeks ago
Once, 4 weeks ago
38 times, 1 month ago
309 more bugmates

Know the solutions? Share your knowledge to help other developers to debug faster.