structuring-a-compose-test
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseStructuring a Compose Test — The androidx-Canonical Class Skeleton
组织 Compose 测试——androidx 标准类骨架
Compose tests fail or rot because their structure is wrong, not because the assertions are wrong. State that lives inside cannot be driven from the test thread; called inside becomes a hidden race; combining with creates two competing test environments. This skill encodes the exact class skeleton used by and so the developer's tests behave the same way.
setContent { }setContent@Before@get:RulerunComposeUiTest { }androidx.compose.material3androidx.compose.foundationCompose 测试失败或逐渐失效,通常是因为其结构有误,而不是断言有误。位于 内部的状态无法从测试线程驱动;在 中调用 会形成隐蔽的竞态;将 与 混用会创建两个相互竞争的测试环境。本 skill 固化了 和 所使用的精确类骨架,使开发者的测试行为保持一致。
setContent { }@BeforesetContent@get:RulerunComposeUiTest { }androidx.compose.material3androidx.compose.foundationWhen to use this skill
何时使用此 skill
- The developer is creating a new and asks where to put state, the rule, and
*Test.kt.setContent - A test compiles but cannot mutate state mid-test ("how do I flip the checkbox after the first assertion?").
- The developer pasted into
setContentand the test is now flaky or will not start.@Before - A reviewer flags a test for declaring state inside .
setContent { } - The developer mixed and
@get:Rule createComposeRule()and gets confusing failures.runComposeUiTest { }
- 开发者正在创建新的 ,并询问状态、rule 和
*Test.kt应放在哪里。setContent - 测试可以编译,但无法在测试中途修改状态(“第一次断言后如何切换复选框?”)。
- 开发者将 放入
setContent,导致测试变得不稳定或无法启动。@Before - 审查者指出测试在 内部声明了状态。
setContent { } - 开发者混用 和
@get:Rule createComposeRule(),得到令人困惑的失败结果。runComposeUiTest { }
When NOT to use this skill
何时不应使用此 skill
- The developer is choosing which entry point to use (rule vs. ); use
runComposeUiTest.../../setup/choosing-test-rule-vs-runtest/SKILL.md - The build cannot resolve ; use
createComposeRule.../../setup/configuring-test-dependencies/SKILL.md - The decision is host (Robolectric) vs. device (instrumentation); use .
../../setup/setting-up-host-vs-device-tests/SKILL.md - The test is specifically for a /
LazyColumn; layerLazyRowon top of this skeleton.../testing-lazy-lists/SKILL.md
- 开发者正在选择使用哪个入口(rule 与 );请使用
runComposeUiTest。../../setup/choosing-test-rule-vs-runtest/SKILL.md - 构建无法解析 ;请使用
createComposeRule。../../setup/configuring-test-dependencies/SKILL.md - 正在决定使用 host(Robolectric)还是 device(instrumentation);请使用 。
../../setup/setting-up-host-vs-device-tests/SKILL.md - 测试专门针对 /
LazyColumn;请在此骨架上叠加LazyRow。../testing-lazy-lists/SKILL.md
Prerequisites
前置条件
- on
androidx.compose.ui:ui-test-junit4,androidTestImplementationonandroidx.compose.ui:ui-test-manifest. SeedebugImplementation.../../setup/configuring-test-dependencies/SKILL.md - Default activity is (provided by
androidx.activity.ComponentActivity). For a custom Activity theui-test-manifestsource set MUST declare it inandroidTest.AndroidManifest.xml - Kotlin source set: (instrumentation) or
src/androidTest/kotlin/...(Robolectric host).src/test/kotlin/...
- 位于
androidx.compose.ui:ui-test-junit4,androidTestImplementation位于androidx.compose.ui:ui-test-manifest。请参阅debugImplementation。../../setup/configuring-test-dependencies/SKILL.md - 默认 Activity 为 (由
androidx.activity.ComponentActivity提供)。对于自定义 Activity,ui-test-manifestsource set 必须将其声明在androidTest中。AndroidManifest.xml - Kotlin source set:(instrumentation)或
src/androidTest/kotlin/...(Robolectric host)。src/test/kotlin/...
Workflow
工作流
-
1. Mirror the production package. Placein the same package as
MyButtonTest.kt. The class name isMyButton.kt(<ProductionFile>Test,SwitchTest.kt).LazyListTest.kt -
2. Annotate the class.is the default budget. Use
@MediumTestonly for tests that intentionally take seconds (long-clicks via@LargeTest, multi-second animations).performTouchInput { longClick() }is non-negotiable for instrumentation.@RunWith(AndroidJUnit4::class) -
3. Declare exactly one rule. Prefer the v2 entry point — it defaults the composition dispatcher to, matching
StandardTestDispatcher.kotlinx.coroutines.test.runTest
kotlin
import androidx.compose.ui.test.junit4.v2.createComposeRule
import kotlinx.coroutines.test.StandardTestDispatcher
@MediumTest
@RunWith(AndroidJUnit4::class)
class MyButtonTest {
@get:Rule val rule = createComposeRule(StandardTestDispatcher())
}For a custom Activity (e.g. , a screen-under-test Activity), use the reified v2 helper:
FragmentActivitykotlin
import androidx.compose.ui.test.junit4.v2.createAndroidComposeRule
@get:Rule val rule = createAndroidComposeRule<FragmentActivity>(StandardTestDispatcher())Cited from .
compose/foundation/foundation/src/androidDeviceTest/kotlin/androidx/compose/foundation/textfield/TextFieldFocusCustomDialogTest.kt:60-
4. Hoist state ABOVE. Anything the test wants to mutate or read must be a property declared in the test method, then captured by reference inside the composable.
setContent -
5. CallINSIDE the
setContent { }method, not in@Test. Each test owns its own composition. Tests with shared@BeforeinsetContentcannot vary content between cases and lose the per-test state setup the framework expects.@Before -
6. Follow Test → Find → Assert → Act → Re-assert. The canonical shape from(the
compose/material3/material3/src/androidDeviceTest/kotlin/androidx/compose/material3/SwitchTest.kt:240-262test):switch_stateChange_movesThumb
kotlin
@Test
fun switch_stateChange_movesThumb() {
var checked by mutableStateOf(false) // STATE (hoisted)
rule.setMaterialContent(lightColorScheme()) { // SET CONTENT (in test body)
val spacer = @Composable { Spacer(Modifier.size(16.dp).testTag("spacer")) }
Switch(
modifier = Modifier.testTag(defaultSwitchTag),
checked = checked,
thumbContent = spacer,
onCheckedChange = { checked = it },
)
}
rule.onNodeWithTag("spacer", useUnmergedTree = true) // FIND + ASSERT
.assertLeftPositionInRootIsEqualTo(8.dp)
rule.runOnIdle { checked = true } // ACT (mutate from outside)
rule.onNodeWithTag("spacer", useUnmergedTree = true) // RE-ASSERT
.assertLeftPositionInRootIsEqualTo(28.dp)
rule.runOnIdle { checked = false }
rule.onNodeWithTag("spacer", useUnmergedTree = true).assertLeftPositionInRootIsEqualTo(8.dp)
}- 7. Read state from outside via . The block runs after
rule.runOnIdle { … }, so observed values reflect the latest composition.waitForIdle()
kotlin
val (index, offset) = rule.runOnIdle {
state.firstVisibleItemIndex to state.firstVisibleItemScrollOffset
}Cited from .
compose/foundation/foundation/integration-tests/lazy-tests/src/androidTest/kotlin/androidx/compose/foundation/lazy/list/LazyListTest.kt:903-904- 8. Write state from outside via . Direct assignment from the test thread races the recomposer.
rule.runOnIdle { … }
kotlin
rule.runOnIdle { count = 5 }-
1. 与生产代码包保持一致。 将放在与
MyButtonTest.kt相同的包中。类名应为MyButton.kt(<ProductionFile>Test、SwitchTest.kt)。LazyListTest.kt -
2. 为类添加注解。是默认的耗时等级。仅当测试有意耗时数秒时才使用
@MediumTest,例如长按(@LargeTest)或持续数秒的动画。对于 instrumentation,performTouchInput { longClick() }是必需的。@RunWith(AndroidJUnit4::class) -
3. 恰好声明一个 rule。 优先使用 v2 入口——它默认将 composition dispatcher 设置为,与
StandardTestDispatcher保持一致。kotlinx.coroutines.test.runTest
kotlin
import androidx.compose.ui.test.junit4.v2.createComposeRule
import kotlinx.coroutines.test.StandardTestDispatcher
@MediumTest
@RunWith(AndroidJUnit4::class)
class MyButtonTest {
@get:Rule val rule = createComposeRule(StandardTestDispatcher())
}对于自定义 Activity(例如 或被测屏幕对应的 Activity),请使用带 reified 类型的 v2 helper:
FragmentActivitykotlin
import androidx.compose.ui.test.junit4.v2.createAndroidComposeRule
@get:Rule val rule = createAndroidComposeRule<FragmentActivity>(StandardTestDispatcher())引用自 。
compose/foundation/foundation/src/androidDeviceTest/kotlin/androidx/compose/foundation/textfield/TextFieldFocusCustomDialogTest.kt:60-
4. 将状态提升到之上。 测试希望修改或读取的所有内容都必须是测试方法中声明的 property,然后在 composable 内部按引用捕获。
setContent -
5. 在方法内部调用
@Test,而不要在setContent { }中调用。 每个测试都应拥有自己的 composition。在@Before中共享@Before会导致测试无法在不同用例之间改变内容,也会失去框架所要求的每测试状态准备过程。setContent -
6. 遵循 Test → Find → Assert → Act → Re-assert。 标准结构来自(即
compose/material3/material3/src/androidDeviceTest/kotlin/androidx/compose/material3/SwitchTest.kt:240-262测试):switch_stateChange_movesThumb
kotlin
@Test
fun switch_stateChange_movesThumb() {
var checked by mutableStateOf(false) // STATE (hoisted)
rule.setMaterialContent(lightColorScheme()) { // SET CONTENT (in test body)
val spacer = @Composable { Spacer(Modifier.size(16.dp).testTag("spacer")) }
Switch(
modifier = Modifier.testTag(defaultSwitchTag),
checked = checked,
thumbContent = spacer,
onCheckedChange = { checked = it },
)
}
rule.onNodeWithTag("spacer", useUnmergedTree = true) // FIND + ASSERT
.assertLeftPositionInRootIsEqualTo(8.dp)
rule.runOnIdle { checked = true } // ACT (mutate from outside)
rule.onNodeWithTag("spacer", useUnmergedTree = true) // RE-ASSERT
.assertLeftPositionInRootIsEqualTo(28.dp)
rule.runOnIdle { checked = false }
rule.onNodeWithTag("spacer", useUnmergedTree = true).assertLeftPositionInRootIsEqualTo(8.dp)
}- 7. 通过 从外部读取状态。 该代码块在
rule.runOnIdle { … }之后运行,因此观察到的值会反映最新的 composition。waitForIdle()
kotlin
val (index, offset) = rule.runOnIdle {
state.firstVisibleItemIndex to state.firstVisibleItemScrollOffset
}引用自 。
compose/foundation/foundation/integration-tests/lazy-tests/src/androidTest/kotlin/androidx/compose/foundation/lazy/list/LazyListTest.kt:903-904- 8. 通过 从外部写入状态。 直接从测试线程赋值会与 recomposer 发生竞态。
rule.runOnIdle { … }
kotlin
rule.runOnIdle { count = 5 }Patterns
模式
Pattern: state hoisted inside vs. above setContent
setContent模式:在 setContent
内部与上方提升状态
setContentkotlin
// WRONG
@Test
fun toggle() {
rule.setContent {
var checked by remember { mutableStateOf(false) } // <-- trapped inside composition
Switch(checked = checked, onCheckedChange = { checked = it })
}
rule.runOnIdle { checked = true } // does not compile / has no reference
}
// WRONG because: the test thread has no reference to `checked`. The state cannot be driven
// from outside, and the test can only verify the very first frame.kotlin
// RIGHT
@Test
fun toggle() {
var checked by mutableStateOf(false) // <-- hoisted to test scope
rule.setContent {
Switch(checked = checked, onCheckedChange = { checked = it })
}
rule.onNodeWithTag("switch").assertIsOff()
rule.runOnIdle { checked = true } // mutate via runOnIdle
rule.onNodeWithTag("switch").assertIsOn()
}kotlin
// WRONG
@Test
fun toggle() {
rule.setContent {
var checked by remember { mutableStateOf(false) } // <-- trapped inside composition
Switch(checked = checked, onCheckedChange = { checked = it })
}
rule.runOnIdle { checked = true } // does not compile / has no reference
}
// WRONG because: the test thread has no reference to `checked`. The state cannot be driven
// from outside, and the test can only verify the very first frame.kotlin
// RIGHT
@Test
fun toggle() {
var checked by mutableStateOf(false) // <-- hoisted to test scope
rule.setContent {
Switch(checked = checked, onCheckedChange = { checked = it })
}
rule.onNodeWithTag("switch").assertIsOff()
rule.runOnIdle { checked = true } // mutate via runOnIdle
rule.onNodeWithTag("switch").assertIsOn()
}Pattern: setContent
in @Before
setContent@Before模式:在 @Before
中设置 setContent
@BeforesetContentkotlin
// WRONG
@Before
fun setUp() {
rule.setContent { MyScreen(state) } // <-- shared across all tests
}
@Test fun stateA() { /* mutate `state` here, but it was already composed without this case */ }kotlin
// RIGHT
@Test
fun stateA() {
val state = ScreenState(initial = "A")
rule.setContent { MyScreen(state) } // <-- per-test composition
rule.onNodeWithTag("title").assertTextEquals("A")
}kotlin
// WRONG
@Before
fun setUp() {
rule.setContent { MyScreen(state) } // <-- shared across all tests
}
@Test fun stateA() { /* mutate `state` here, but it was already composed without this case */ }kotlin
// RIGHT
@Test
fun stateA() {
val state = ScreenState(initial = "A")
rule.setContent { MyScreen(state) } // <-- per-test composition
rule.onNodeWithTag("title").assertTextEquals("A")
}Pattern: one rule per class — never mix with runComposeUiTest
runComposeUiTest模式:每个类一个 rule——绝不与 runComposeUiTest
混用
runComposeUiTestkotlin
// WRONG
class MyTest {
@get:Rule val rule = createComposeRule(StandardTestDispatcher())
@Test fun a() = runComposeUiTest { // <-- second test environment
setContent { /* … */ }
}
}
// WRONG because: createComposeRule and runComposeUiTest each manage an independent test
// environment (composition + MainTestClock + IdlingResourceRegistry). Mixing them produces
// undefined behavior. KDoc warns explicitly: see the ComposeUiTest.android.kt KDoc on
// runComposeUiTest, runAndroidComposeUiTest, runEmptyComposeUiTest, and the v2 variants.kotlin
// RIGHT — pick exactly one entry point per class
class MyRuleTest {
@get:Rule val rule = createComposeRule(StandardTestDispatcher())
@Test fun a() { rule.setContent { /* … */ } }
}
// or
class MyFunctionTest {
@Test fun a() = runComposeUiTest { setContent { /* … */ } }
}kotlin
// WRONG
class MyTest {
@get:Rule val rule = createComposeRule(StandardTestDispatcher())
@Test fun a() = runComposeUiTest { // <-- second test environment
setContent { /* … */ }
}
}
// WRONG because: createComposeRule and runComposeUiTest each manage an independent test
// environment (composition + MainTestClock + IdlingResourceRegistry). Mixing them produces
// undefined behavior. KDoc warns explicitly: see the ComposeUiTest.android.kt KDoc on
// runComposeUiTest, runAndroidComposeUiTest, runEmptyComposeUiTest, and the v2 variants.kotlin
// RIGHT — pick exactly one entry point per class
class MyRuleTest {
@get:Rule val rule = createComposeRule(StandardTestDispatcher())
@Test fun a() { rule.setContent { /* … */ } }
}
// or
class MyFunctionTest {
@Test fun a() = runComposeUiTest { setContent { /* … */ } }
}Pattern: custom Activity needs its own manifest entry
模式:自定义 Activity 需要独立的 manifest 条目
kotlin
// RIGHT — ComponentActivity comes free from ui-test-manifest
@get:Rule val rule = createComposeRule(StandardTestDispatcher())kotlin
// RIGHT — a custom Activity must be declared in src/androidTest/AndroidManifest.xml
@get:Rule val rule = createAndroidComposeRule<MyActivity>(StandardTestDispatcher())xml
<!-- src/androidTest/AndroidManifest.xml -->
<manifest xmlns:android="http://schemas.android.com/apk/res/android">
<application>
<activity android:name=".MyActivity" />
</application>
</manifest>kotlin
// RIGHT — ComponentActivity comes free from ui-test-manifest
@get:Rule val rule = createComposeRule(StandardTestDispatcher())kotlin
// RIGHT — a custom Activity must be declared in src/androidTest/AndroidManifest.xml
@get:Rule val rule = createAndroidComposeRule<MyActivity>(StandardTestDispatcher())xml
<!-- src/androidTest/AndroidManifest.xml -->
<manifest xmlns:android="http://schemas.android.com/apk/res/android">
<application>
<activity android:name=".MyActivity" />
</application>
</manifest>Pattern: MediumTest
vs LargeTest
MediumTestLargeTest模式:MediumTest
与 LargeTest
MediumTestLargeTestkotlin
@MediumTest // default — sub-second tests
class SwitchTest { /* … */ }
@LargeTest // long-clicks, multi-second animations
class CombinedClickableTest { /* … */ }@MediumTestSwitchTest.kt:76@LargeTestkotlin
@MediumTest // default — sub-second tests
class SwitchTest { /* … */ }
@LargeTest // long-clicks, multi-second animations
class CombinedClickableTest { /* … */ }@MediumTestSwitchTest.kt:76@LargeTestMandatory rules
强制规则
- MUST annotate the class with and a size annotation (
@RunWith(AndroidJUnit4::class)by default).@MediumTest - MUST declare exactly one rule per class — either ,
createComposeRule(...), orcreateAndroidComposeRule<A>(...). MUST NOT combine acreateEmptyComposeRule()rule with@get:Rulein the same class. KDoc cited atrunComposeUiTest { }.compose/ui/ui-test/src/androidMain/kotlin/androidx/compose/ui/test/ComposeUiTest.android.kt:158, 204, 247, 338 - MUST prefer the v2 entry points /
androidx.compose.ui.test.junit4.v2.createComposeRule. The v1 forms arecreateAndroidComposeRulebecause they use@Deprecated(level = WARNING)instead ofUnconfinedTestDispatcher(skydoves directive #6).StandardTestDispatcher - MUST hoist mutable state as above
var x by mutableStateOf(...)whenever the test must drive or observe it.setContent { } - MUST call inside the
rule.setContent { }method. MUST NOT call it in@Test.@Before - MUST mutate state from outside via (or
rule.runOnIdle { state = … }for cases where idling first is undesirable, e.g.rule.runOnUiThread { … }). See skydoves directive #5. Detail inmainClock.autoAdvance = false.../../synchronization/synchronizing-with-idle/SKILL.md - MUST read state from outside via . Direct reads from the test thread snapshot the wrong frame.
rule.runOnIdle { state.value } - PREFERRED: find by declared as a
Modifier.testTag(...)in production (skydoves directive #1). Text finders are i18n-fragile. Seeconst.../../finders/finding-nodes-by-tag-text-content/SKILL.md - PREFERRED: Test → Find → Assert → Act → Re-assert per logical state change. Multi-step tests stack additional Act → Re-assert pairs ().
SwitchTest.kt:140-147
- 必须使用 和一个耗时注解为类添加注解(默认使用
@RunWith(AndroidJUnit4::class))。@MediumTest - 必须在每个类中恰好声明一个 rule,即 、
createComposeRule(...)或createAndroidComposeRule<A>(...)之一。绝不能在同一类中组合使用createEmptyComposeRule()rule 和@get:Rule。KDoc 引用位置:runComposeUiTest { }。compose/ui/ui-test/src/androidMain/kotlin/androidx/compose/ui/test/ComposeUiTest.android.kt:158, 204, 247, 338 - 必须优先使用 v2 入口 /
androidx.compose.ui.test.junit4.v2.createComposeRule。v1 形式已被标记为createAndroidComposeRule,因为它们使用@Deprecated(level = WARNING)而不是UnconfinedTestDispatcher(skydoves directive #6)。StandardTestDispatcher - 必须在测试需要驱动或观察状态时,将可变状态声明为 并放置在
var x by mutableStateOf(...)之上。setContent { } - 必须在 方法内部调用
@Test。绝不能在rule.setContent { }中调用。@Before - 必须通过 从外部修改状态;对于不希望先等待空闲的场景,可以使用
rule.runOnIdle { state = … },例如rule.runOnUiThread { … }。请参阅 skydoves directive #5。详细信息见mainClock.autoAdvance = false。../../synchronization/synchronizing-with-idle/SKILL.md - 必须通过 从外部读取状态。直接从测试线程读取会得到错误的帧快照。
rule.runOnIdle { state.value } - **首选:**使用 查找节点,并将 tag 作为生产代码中的
Modifier.testTag(...)声明(skydoves directive #1)。基于文本的查找器容易受到国际化影响。请参阅const。../../finders/finding-nodes-by-tag-text-content/SKILL.md - **首选:**每次逻辑状态变更都遵循 Test → Find → Assert → Act → Re-assert。多步骤测试可以叠加额外的 Act → Re-assert 对()。
SwitchTest.kt:140-147
Verification
验证
- Class has +
@RunWith(AndroidJUnit4::class)(or@MediumTest).@LargeTest - Exactly one declared and it is a
@get:Rule/createComposeRule(...)/createAndroidComposeRule(...)instance.createEmptyComposeRule() - No invocation appears in the same class.
runComposeUiTest { } - appears inside
setContent { }methods only — not in@Test/@Before.@BeforeEach - Every state the test mutates is declared with above
var x by mutableStateOf(...), captured by reference inside the composable.setContent - All state mutations after go through
setContentorrule.runOnIdle { }.rule.runOnUiThread { } - All cross-frame state reads happen inside .
rule.runOnIdle { } - No appears in the test method (skydoves directive #7). See
Thread.sleep.../../synchronization/synchronizing-with-idle/SKILL.md - Custom Activities are declared in (not just the production
src/androidTest/AndroidManifest.xml).AndroidManifest.xml
- 类包含 +
@RunWith(AndroidJUnit4::class)(或@MediumTest)。@LargeTest - 恰好声明一个 ,且它是
@get:Rule/createComposeRule(...)/createAndroidComposeRule(...)实例。createEmptyComposeRule() - 同一类中未出现 调用。
runComposeUiTest { } - 仅出现在
setContent { }方法中——不得出现在@Test/@Before中。@BeforeEach - 测试修改的每项状态都通过 声明在
var x by mutableStateOf(...)之上,并在 composable 内部按引用捕获。setContent - 之后的所有状态修改都通过
setContent或rule.runOnIdle { }完成。rule.runOnUiThread { } - 所有跨帧状态读取都在 内完成。
rule.runOnIdle { } - 测试方法中未出现 (skydoves directive #7)。请参阅
Thread.sleep。../../synchronization/synchronizing-with-idle/SKILL.md - 自定义 Activity 已声明在 中,而不只是
src/androidTest/AndroidManifest.xml。production AndroidManifest.xml
References
参考资料
- Compose testing overview: https://developer.android.com/develop/ui/compose/testing
- Compose testing setup: https://developer.android.com/develop/ui/compose/testing#setup
- Compose testing cheat sheet: https://developer.android.com/develop/ui/compose/testing-cheatsheet
- Canonical class skeleton:
compose/material3/material3/src/androidDeviceTest/kotlin/androidx/compose/material3/SwitchTest.kt:76-263 - Custom Activity rule:
compose/foundation/foundation/src/androidDeviceTest/kotlin/androidx/compose/foundation/textfield/TextFieldFocusCustomDialogTest.kt:57-60 - v2 rule factory:
compose/ui/ui-test-junit4/src/androidMain/kotlin/androidx/compose/ui/test/junit4/v2/AndroidComposeTestRule.android.kt - "Do not mix rule and runComposeUiTest" KDoc:
compose/ui/ui-test/src/androidMain/kotlin/androidx/compose/ui/test/ComposeUiTest.android.kt:158, 204, 247, 338 - semantics:
runOnIdlecompose/ui/ui-test-junit4/src/jvmAndAndroidMain/kotlin/androidx/compose/ui/test/junit4/ComposeTestRule.jvmAndAndroid.kt
- Compose 测试概览:https://developer.android.com/develop/ui/compose/testing
- Compose 测试设置:https://developer.android.com/develop/ui/compose/testing#setup
- Compose 测试速查表:https://developer.android.com/develop/ui/compose/testing-cheatsheet
- 标准类骨架:
compose/material3/material3/src/androidDeviceTest/kotlin/androidx/compose/material3/SwitchTest.kt:76-263 - 自定义 Activity rule:
compose/foundation/foundation/src/androidDeviceTest/kotlin/androidx/compose/foundation/textfield/TextFieldFocusCustomDialogTest.kt:57-60 - v2 rule factory:
compose/ui/ui-test-junit4/src/androidMain/kotlin/androidx/compose/ui/test/junit4/v2/AndroidComposeTestRule.android.kt - “禁止混用 rule 与 ”的 KDoc:
runComposeUiTestcompose/ui/ui-test/src/androidMain/kotlin/androidx/compose/ui/test/ComposeUiTest.android.kt:158, 204, 247, 338 - 语义:
runOnIdlecompose/ui/ui-test-junit4/src/jvmAndAndroidMain/kotlin/androidx/compose/ui/test/junit4/ComposeTestRule.jvmAndAndroid.kt