java.lang.AssertionError: Expected: is "20091021121000 -0700" but: was "20091021121000 +0200"

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 Spring JIRA by Sam Brannen, 1 year ago
Expected: is "20091021121000 -0700" but: was "20091021121000 +0200"
via Spring JIRA by Sam Brannen, 1 year ago
Expected: is "20091021121000 -0700" but: was "20091021121000 +0200"
via GitHub by fernandobrito
, 2 years ago
Expected: a collection with size <2> but: collection size was <1>
via GitHub by sjka
, 1 year ago
Expected: is "1.1.2" but: was "1.1.1"
via GitHub by sjka
, 10 months ago
Expected: is <ON> but: was <OFF>
via GitHub by sjka
, 1 year ago
Expected: is not null but: was null
java.lang.AssertionError: Expected: is "20091021121000 -0700" but: was "20091021121000 +0200"
at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
at org.junit.Assert.assertThat(Assert.java:962)
at org.junit.Assert.assertThat(Assert.java:924)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:46)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:43)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:270)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:62)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:52)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
at org.junit.runners.ParentRunner.run(ParentRunner.java:307)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)

Users with the same issue

4 times, 1 month ago
5 times, 6 months ago
3 times, 1 year ago
2 times, 2 months ago
Once, 3 months ago
19 more bugmates

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