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

Samebug tips

  1. ,
    Expert tip

    Check your pattern declaration or check your assert declaration.

Solutions on the web

via GitHub by elharo
, 1 year ago
expected: java.lang.Integer<1> but was: java.lang.String<1>
via GitHub by Frank-Bradley
, 2 years ago
i: 1 expected: but was:
via Google Groups by Rajini Sivaram, 3 weeks ago
expected:<5> but was:<1>
via Google Groups by Michael Portuesi, 10 months ago
@Implementation method mismatch: public void > com.xtremelabs.robolectric.shadows.ShadowCameraSize.__constructor__(int,int ) > doesn't match a real method expected:<0> but was:<1>
via osdir.com by Unknown author, 2 years ago
There should be one document because overwrite=true expected:<1> but was:<0> at __randomizedtesting.SeedInfo.seed([573006190B77DDC9:DF6439C3A58BB031]:0)
via mail-archive.com by Unknown author, 2 years ago
Some writers didn't complete in expected runtime! Current writer state:[Circular Writer: directory: /test-0 target length: 50 current item: 24 done: false ] expected:<0> but was:<1>
java.lang.AssertionError: expected: java.lang.Integer<1> but was: java.lang.String<1>	at org.junit.Assert.fail(Assert.java:88)	at org.junit.Assert.failNotEquals(Assert.java:834)	at org.junit.Assert.assertEquals(Assert.java:118)	at org.junit.Assert.assertEquals(Assert.java:144)	at com.google.cloud.tools.eclipse.appengine.facets.MavenAppEngineFacetUtilTest.testGetAppEnginePomProperties(MavenAppEngineFacetUtilTest.java:37)