New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mocking map invocation via chained call stopped working #565
Comments
Does this still happen if you declare your mock as a relaxed mock, i.e. |
@Raibaz It still fails. Updated the example in original message. |
I have a same problem when i use Do someone find a solution? |
This looks like a bug in the |
Thank you @Raibaz. Can you me say how i fix it? |
Hello guys. Any updates about this issue? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. If you are sure that this issue is important and should not be marked as |
Hi! Anyone have a solution for this issue? |
…-stubbing Fix stubbing by chained calls on collections (#565)
Mockk version: 1.10.5
Kotlin version: 1.4.21
OS: MacOS Big Sur 11.2
JVM: adopt-openjdk-11 version 11.0.10
Java class under test:
Test:
Expected (as in version 1.9.3)
bar.attributes
should return aMap
Actual
NullPointerException
becausebar.attributes
is nullThe text was updated successfully, but these errors were encountered: