Android测试包全量运行时MockK失效问题求助

我给ViewModel编写了测试用例，单独运行该用例或整个测试类均能成功，但全量运行androidTest包时，会抛出io.mockk.MockKException异常。

可正常运行的测试代码 #

@RunWith(AndroidJUnit4::class)
class MyViewModelTest{

    @Test
    fun test_one(){
        getInstrumentation().runOnMainSync(Runnable {
            val context = ApplicationProvider.getApplicationContext<Context>()
            mockkStatic(MyManager::class)
            val myInterface = mockk<MyInterface>()
            every { MyManager.getCommunicator() } returns myInterface
            every { myInterface.context } returns context
            every { myInterface.getLongFromGTM(any()) } returns 0
            val viewModel = MyViewModel(context as Application)
            viewModel.model = MyDataModel()
            viewModel.model.isRepeatEligible = true
            val res = viewModel.isRepeatEligible()
            Truth.assertThat(res).isTrue()
        })
    }

}

全量运行时的报错信息 #

报错内容为：io.mockk.MockKException: no answer found for: MyInterface(#1).context

相关类代码 #

1. MyManager.java #

public class MyManager {
    private static MyInterface myCommunicator;
    
    public static MyInterface getCommunicator() {
        if (myCommunicator == null) {
            synchronized (MyManager.class) {
                if (myCommunicator == null) {
                    Class<?> cls = Class.forName("mypackage.communicator.MyCommunicator");
                    myCommunicator = (MyInterface) cls.newInstance();
                }
            }
        }
        return myCommunicator;
    }    
}

2. MyViewModel.kt #

class MyViewModel(application: Application) : BaseViewModel(application) {
    var model = MyDataModel()    
    private val timerDelay: Long by lazy {
        myCommunicator.getLongFromGTM("key_p2m_timer_delay")
    }
    val timerDuration: Long by lazy {
        myCommunicator.getLongFromGTM("key_p2m_timer_duration")
    }

    fun isRepeatEligible(): Boolean {
        model.apply {
            return isRepeatEligible && !isLinkBased && !isAlreadyPresent
        }
}
}

这个问题的核心是静态Mock的全局状态污染：单独运行测试时，mockkStatic(MyManager::class)的Mock状态不会影响其他测试；但全量运行时，所有测试用例共用同一个JVM进程，Mock状态未被正确清理，导致后续测试中MyManager.getCommunicator()返回的Mock对象缺少对应应答配置。

具体修复步骤： #

1. 添加测试后Mock清理逻辑
   在测试类中新增@After方法，确保每次测试结束后清除静态Mock的全局状态：

   @After
   fun tearDown() {
       unmockkStatic(MyManager::class)
   }
   

   这样能保证每个测试用例的Mock环境完全独立，不会被之前的测试残留状态干扰。

2. 统一Mock操作的上下文
   将mockkStatic及应答配置全部放在runOnMainSync代码块内部，确保所有Mock操作都在主线程上下文执行，避免线程差异导致的状态不一致：

   @Test
   fun test_one(){
       getInstrumentation().runOnMainSync(Runnable {
           val context = ApplicationProvider.getApplicationContext<Context>()
           // 把mockkStatic移到主线程块内
           mockkStatic(MyManager::class)
           val myInterface = mockk<MyInterface>()
           every { MyManager.getCommunicator() } returns myInterface
           every { myInterface.context } returns context
           every { myInterface.getLongFromGTM(any()) } returns 0
           
           val viewModel = MyViewModel(context as Application)
           viewModel.model = MyDataModel()
           viewModel.model.isRepeatEligible = true
           val res = viewModel.isRepeatEligible()
           Truth.assertThat(res).isTrue()
       })
   }
   

3. 检查其他测试类的Mock逻辑
   如果其他测试类也对MyManager做了静态Mock，同样需要添加@After清理逻辑，否则全量运行时仍会出现Mock状态冲突。

原理说明 #

MockK的静态Mock是基于类的全局状态修改，全量测试时所有测试用例在同一进程执行，若不手动清理，之前测试的Mock配置会保留到下一个测试。当后续测试未给myInterface.context配置应答时，就会抛出no answer found异常。

内容的提问来源于stack exchange，提问作者Roop Kishore