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 QOS.ch JIRA by Ceki Gülcü, 1 year ago
via QOS.ch JIRA by Ceki Gulcu, 2 years ago
via GitHub by hyleung
, 2 years ago
expected:<4> but was:<3>
via GitHub by akarnokd
, 2 years ago
via GitHub by oscerd
, 2 years ago
expected: but was:
via GitHub by Frank-Bradley
, 2 years ago
expected: but was:
java.lang.AssertionError: expected:<17> but was:<3>	at org.junit.Assert.fail(Assert.java:93)	at org.junit.Assert.failNotEquals(Assert.java:647)	at org.junit.Assert.assertEquals(Assert.java:128)	at org.junit.Assert.assertEquals(Assert.java:472)	at org.junit.Assert.assertEquals(Assert.java:456)	at org.slf4j.impl.MultithreadedInitializationTest.multiThreadedInitialization(MultithreadedInitializationTest.java:91)	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)	at java.lang.reflect.Method.invoke(Method.java:616)