Android 使用 TestCoroutineDispatcher(已弃用)替代方案测试 Kotlin 协程

Android testing of Kotlin coroutines with TestCoroutineDispatcher (deprecated) alternative

我正在研究我的 Android 应用程序中的协程测试并遵循此代码实验室 Advanced Android in Kotlin 05.3: Testing Coroutines and Jetpack integrations

此 Codelab 包含以下代码片段

@ExperimentalCoroutinesApi
val testDispatcher: TestCoroutineDispatcher = TestCoroutineDispatcher()

@ExperimentalCoroutinesApi
@Before
fun setupDispatcher() {
    Dispatchers.setMain(testDispatcher)
}

@ExperimentalCoroutinesApi
@After
fun tearDownDispatcher() {
    Dispatchers.resetMain()
    testDispatcher.cleanupTestCoroutines()
}

但是 TestCoroutineDispatcher 被标记为已弃用并带有以下评论:-

/**
 * [CoroutineDispatcher] that performs both immediate and lazy execution of coroutines in tests
 * and uses a [TestCoroutineScheduler] to control its virtual clock.
 *
 * By default, [TestCoroutineDispatcher] is immediate. That means any tasks scheduled to be run without delay are
 * immediately executed. If they were scheduled with a delay, the virtual clock-time must be advanced via one of the
 * methods on the dispatcher's [scheduler].
 *
 * When switched to lazy execution using [pauseDispatcher] any coroutines started via [launch] or [async] will
 * not execute until a call to [DelayController.runCurrent] or the virtual clock-time has been advanced via one of the
 * methods on [DelayController].
 *
 * @see DelayController
 */
@Deprecated("The execution order of `TestCoroutineDispatcher` can be confusing, and the mechanism of " +
    "pausing is typically misunderstood. Please use `StandardTestDispatcher` or `UnconfinedTestDispatcher` instead.",
    level = DeprecationLevel.WARNING)
// Since 1.6.0, ERROR in 1.7.0 and removed as experimental in 1.8.0
public class TestCoroutineDispatcher(public override val scheduler: TestCoroutineScheduler = TestCoroutineScheduler()):
    TestDispatcher(), Delay, SchedulerAsDelayController
{...}

不清楚我应该如何使用 TestCoroutineDispatcher() 的建议替代方案是 StandardTestDispatcherUnconfinedTestDispatcher 直接替代 TestCoroutineDispatcher()?

我错过了什么?

似乎可以使用更优雅的解决方案,如 runTest(),因为 1.6.0

摘自此 SO

有关如何使用该模块的详细信息,请参阅 documentation