Stubbing a method on a spyk object calls the original method immediately.

[pikaboo]

Expected Behavior.

When stubbing a method on a spyk the method is invoked only when it is invoked from outside, by another object that is using the spy

Current Behavior

When the method is stubbed, it is immediately invoked, and it invokes the original one not the stubbed one, and even worse this behaviour is unexpected, meaning sometimes it does behave as expected and most of the time it does not.

Failure Information (for bugs)

for example the method

   class SomeClass() {
       fun login(listener: (Boolean) -> Unit ) {
            do some async logic and then call the listener with the result
      }
   }


   val spy = spyk(SomeClass())  {

          val completion = slot<(Boolean) -> Unit>()
         //this immediately calls the original login method
         every { login(capture(completion)) } answers {
              completion.captured.invoke(true)
         }
     }

Context

Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.

• MockK version: 1.10.0
• OS: Android 29
• Kotlin version: 1.3.61
• JDK version: 8
• JUnit version: 4.12
• Type of test: instrumented

[stale[bot]]

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 stale just ask to put an important label.

[pikaboo]

issue not stale

[mishael-w]

I've encountered that issue, my situation was as follows: mockk version mockk:1.10.0 had two test functions using exact same code, something like: ` @Test fun func1(){ val parser = MyParser() val mock = spyk(parser, recordPrivateCalls = true) every { mock invoke "getDivider" withArguments listOf(any()) } returns 0L // Some code parser.parse() }

@Test fun func2(){ val parser = MyParser() val mock = spyk(parser, recordPrivateCalls = true) every { mock invoke "getDivider" withArguments listOf(any()) } returns 0L // Some other code parser.parse() }`

surprisingly func1 executed the actual 'getDivider' method while func2 mocked the result without running the actual code

[pikaboo]

Do you run those tests one after the other or one by one ?

[mishael-w]

I ran those tests separately

[stale[bot]]

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 stale just ask to put an important label.

[pikaboo]

issue note stale

[stale[bot]]

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 stale just ask to put an important label.

[daespark]

Running into the same issue.

[daespark]

This is also true for Kotlin classes that have @JvmStatic functions. pretty sucky because we can't really do

mockkStatic(NavHostFragment::class)
every { NavHostFragment.findNavController(ofType(Fragment::class)) } returns mockNavController

this invokes the NavHostFragment::findNavController and we end up getting exception on the latest Navigation Api

[fblampe]

I'm having the same issue when trying to stub a @JvmStatic function on a Kotlin singleton object with mockkObject. This is really confusing, because it already takes quite a while to actually find that the method is called when it should be stubbed, and then you're still no bit closer to work around this while still being able to stub the functionality you need.

Mockk 1.12.2 Kotlin 1.5.20

[aburmeis]

Same problem with Spring and springmockk @SpykBean:

@SpykBean
private lateinit var service: MyService

@Test
fun `capturing a parameter of a secured function call`() {
        val pageable = slot<Pageable>()
        verify { service.securedCall(capture(pageable)) }
}

ends up in a Spring Security Exception as the verify does a real function call. (Kotlin 1.9.10, Mockk 1.13.8)

[RotBolt]

Is there any update on this?