org.mockito.exceptions.misusing.WrongTypeOfReturnValue

NestedWhen$Product$$EnhancerByMockitoWithCGLIB$$6ecf83da cannot be returned by getBar() getBar() should return Bar *** This exception *might* occur in wrongly written multi-threaded tests. Please refer to Mockito FAQ on limitations of concurrency testing.

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web21

  • via Google Groups by ludyte, 6 months ago
    NestedWhen$Product$$EnhancerByMockitoWithCGLIB$$6ecf83da cannot be returned by getBar() getBar() should return Bar *** This exception *might* occur in wrongly written multi-threaded tests. Please refer to Mockito FAQ on limitations of concurrency testing.
  • via Stack Overflow by Selvin
    , 4 months ago
    String cannot be returned by getDeclaringType() getDeclaringType() should return Class *** This exception *might* occur in wrongly written multi-threaded tests. Please refer to Mockito FAQ on limitations of concurrency testing.
  • via GitHub by joshvfleming
    , 8 months ago
    exception *might* occur in wrongly written multi-threaded tests. Please refer to Mockito FAQ on limitations of concurrency testing. 2. A spy is stubbed using when(spy.foo()).then() syntax. It is safer to stub spies - - with doReturn|Throw() family of methods. More in javadocs for Mockito.spy() method.
  • Stack trace

    • org.mockito.exceptions.misusing.WrongTypeOfReturnValue: NestedWhen$Product$$EnhancerByMockitoWithCGLIB$$6ecf83da cannot be returned by getBar() getBar() should return Bar *** This exception *might* occur in wrongly written multi-threaded tests. Please refer to Mockito FAQ on limitations of concurrency testing. at NestedWhen.nestedWhenTest(NestedWhen.java:36) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.