asserting-bounds-and-dimensions

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Asserting Bounds and Dimensions — Layout Math in Dp, Not Pixels

断言边界与尺寸——使用 Dp 而非像素进行布局计算

Layout assertions belong in dp, run with a half-dp tolerance, and most of the interesting checks (padding, gap, alignment) are subtractions between two
getUnclippedBoundsInRoot()
rectangles. This skill picks the right size/position assertion, explains clipped vs unclipped, and shows the canonical "compute padding from two rects" pattern lifted directly from
material3/ButtonTest.kt
.
布局断言应以 dp 为单位,使用半个 dp 的容差执行,大多数有意义的检查(padding、间距、对齐)都是对两个
getUnclippedBoundsInRoot()
矩形进行差值计算。此 skill 用于选择合适的尺寸或位置断言,解释已裁剪与未裁剪边界的区别,并展示直接取自
material3/ButtonTest.kt
的“根据两个未裁剪矩形计算 padding”标准模式。

When to use this skill

何时使用此 skill

  • The developer wants to verify a Button is 48 dp tall, a Spacer is 16 dp wide, an Icon is at position
    (24.dp, 12.dp)
    .
  • The developer asks how to assert the padding between two composables.
  • The developer asks about minimum touch target sizes (
    ChipDefaults.MinHeight + 1.dp
    ).
  • The developer is comparing layout values in pixels and wants the dp-typed equivalent.
  • The developer mentions
    assertWidthIsEqualTo
    ,
    getUnclippedBoundsInRoot
    ,
    DpRect
    ,
    getAlignmentLinePosition
    ,
    getFirstLinkBounds
    .
  • 开发者希望验证 Button 的高度为 48 dp、Spacer 的宽度为 16 dp,或 Icon 的位置为
    (24.dp, 12.dp)
    。
  • 开发者询问如何断言两个 composable 之间的 padding。
  • 开发者询问最小触摸目标尺寸(
    ChipDefaults.MinHeight + 1.dp
    )。
  • 开发者正在比较以 pixels 表示的布局值,并希望获得等效的 dp 类型断言。
  • 开发者提到
    assertWidthIsEqualTo
    、
    getUnclippedBoundsInRoot
    、
    DpRect
    、
    getAlignmentLinePosition
    或
    getFirstLinkBounds
    。

When NOT to use this skill

何时不应使用此 skill

  • The check is about state (enabled, on, selected) — see
    ./asserting-node-state-and-text/SKILL.md
    .
  • The check is "is the node on screen at all" —
    assertIsDisplayed()
    is enough; bounds math adds friction without value.
  • The composable's bounds depend on an animation in flight — pause the clock first; see
    ../../synchronization/testing-animations-deterministically/SKILL.md
    .
  • The bounds are relative to a screenshot — use a screenshot test instead.
  • 检查内容涉及状态(enabled、on、selected)——参见
    ./asserting-node-state-and-text/SKILL.md
    。
  • 检查内容是“节点是否完全位于屏幕上”——使用
    assertIsDisplayed()
    即可;边界计算只会徒增复杂度。
  • composable 的边界取决于正在执行的动画——请先暂停测试时钟;参见
    ../../synchronization/testing-animations-deterministically/SKILL.md
    。
  • 边界是相对于截图而言的——请改用截图测试。

Prerequisites

前置条件

  • A working
    ComposeTestRule
    /
    ComposeUiTest
    . See
    ../../setup/configuring-test-dependencies/SKILL.md
    .
  • The target composable has finished measuring and placing. If it animates in, advance the test clock first — see
    ../../synchronization/controlling-the-test-clock/SKILL.md
    .
  • For touch-target assertions, the target node has a click action so
    touchBoundsInRoot
    is meaningful.
  • 可正常工作的
    ComposeTestRule
    /
    ComposeUiTest
    。参见
    ../../setup/configuring-test-dependencies/SKILL.md
    。
  • 目标 composable 已完成测量和放置。如果它通过动画进入,请先推进测试时钟——参见
    ../../synchronization/controlling-the-test-clock/SKILL.md
    。
  • 对于触摸目标断言,目标节点包含 click action,这样
    touchBoundsInRoot
    才有意义。

Workflow

工作流

  • 1. Pick the assertion by question type. All APIs live in
    commonMain/.../BoundsAssertions.kt
    .
    QuestionAPIFile:line
    Is the layout exactly W dp wide?
    assertWidthIsEqualTo(expectedWidth: Dp)
    BoundsAssertions.kt:44-46
    Is the layout exactly H dp tall?
    assertHeightIsEqualTo(expectedHeight: Dp)
    BoundsAssertions.kt:53-55
    At least W wide?
    assertWidthIsAtLeast(expectedMinWidth: Dp)
    BoundsAssertions.kt:85-87
    At least H tall?
    assertHeightIsAtLeast(expectedMinHeight: Dp)
    BoundsAssertions.kt:95-99
    Touch-target width?
    assertTouchWidthIsEqualTo(expectedWidth: Dp)
    BoundsAssertions.kt:62-66
    Touch-target height?
    assertTouchHeightIsEqualTo(expectedHeight: Dp)
    BoundsAssertions.kt:73-77
    Exact position in root?
    assertPositionInRootIsEqualTo(left: Dp, top: Dp)
    BoundsAssertions.kt:109-117
    Top position only?
    assertTopPositionInRootIsEqualTo(top: Dp)
    BoundsAssertions.kt:126-130
    Left position only?
    assertLeftPositionInRootIsEqualTo(left: Dp)
    BoundsAssertions.kt:139-143
    Read full unclipped bounds
    getUnclippedBoundsInRoot(): DpRect
    BoundsAssertions.kt:148-152
    Read clipped bounds
    getBoundsInRoot(): DpRect
    BoundsAssertions.kt:158-165
    Alignment line in dp
    getAlignmentLinePosition(line: AlignmentLine): Dp
    BoundsAssertions.kt:171-180
    Bounds of a
    LinkAnnotation
    in a Text
    getFirstLinkBounds(predicate)
    BoundsAssertions.kt:196-248
    Compare any two
    Dp
    values
    Dp.assertIsEqualTo(expected, subject, tolerance = Dp(.5f))
    BoundsAssertions.kt:319-324
  • 2. Use unclipped bounds for layout math; clipped bounds for "what the user sees".
    getUnclippedBoundsInRoot()
    returns the laid-out rectangle ignoring viewport clipping (
    BoundsAssertions.kt:148-152
    →
    unclippedBoundsInRoot
    private,
    BoundsAssertions.kt:284-291
    ).
    getBoundsInRoot()
    clips to the viewport (
    BoundsAssertions.kt:158-165
    ). Padding/spacing math uses unclipped; partial-visibility checks use clipped.
  • 3. Tolerance is half a dp by default.
    Dp.assertIsEqualTo(expected, subject, tolerance = Dp(.5f))
    (
    BoundsAssertions.kt:319
    ) accepts deviations up to 0.5 dp because layout rounding introduces sub-dp drift. Override only when stricter precision is justified by an explicit measurement contract.
  • 4. Compute padding by subtracting two unclipped rects, then call
    Dp.assertIsEqualTo
    .
    This is the canonical material3 pattern (
    material3/.../ButtonTest.kt:213-225
    ):
    kotlin
    val buttonBounds = rule.onNodeWithTag(ButtonTestTag).getUnclippedBoundsInRoot()
    val textBounds   = rule.onNodeWithTag(TextTestTag).getUnclippedBoundsInRoot()
    
    (textBounds.left - buttonBounds.left).assertIsEqualTo(
        24.dp,
        "padding between the start of the button and the start of the text.",
    )
    
    (buttonBounds.right - textBounds.right).assertIsEqualTo(
        24.dp,
        "padding between the end of the text and the end of the button.",
    )
    buttonBounds.height.assertIsEqualTo(ButtonDefaults.MinHeight, "height of button.")
    The
    subject
    string lands in the failure message:
    "Actual padding between the start of the button and the start of the text. is 22.dp, expected 24.dp (tolerance: .5.dp)"
    .
  • 5. For minimum-size contracts, use
    assertHeightIsAtLeast
    /
    assertWidthIsAtLeast
    .
    Useful when a composable should never be smaller than a constant, even at large font scale. Example from
    material/ChipTest.kt:226-233
    :
    kotlin
    rule.setMaterialContent { Chip(onClick = {}) { Text(text = "Test chip", fontSize = 50.sp) } }
    rule.onNode(hasClickAction()).assertHeightIsAtLeast(ChipDefaults.MinHeight + 1.dp)
  • 6. Use touch bounds when verifying tap-target accessibility.
    assertTouchWidthIsEqualTo
    /
    assertTouchHeightIsEqualTo
    reads
    node.touchBoundsInRoot
    (
    BoundsAssertions.kt:270-282
    ), which can extend past the visual bounds when the composable applies
    Modifier.minimumInteractiveComponentSize()
    or similar. Visual bounds use
    getUnclippedBoundsInRoot
    ; touch bounds answer "where will a click land".
  • 1. 根据问题类型选择断言。 所有 API 均位于
    commonMain/.../BoundsAssertions.kt
    。
    问题API文件:行号
    布局宽度是否恰好为 W dp?
    assertWidthIsEqualTo(expectedWidth: Dp)
    BoundsAssertions.kt:44-46
    布局高度是否恰好为 H dp?
    assertHeightIsEqualTo(expectedHeight: Dp)
    BoundsAssertions.kt:53-55
    宽度是否至少为 W?
    assertWidthIsAtLeast(expectedMinWidth: Dp)
    BoundsAssertions.kt:85-87
    高度是否至少为 H?
    assertHeightIsAtLeast(expectedMinHeight: Dp)
    BoundsAssertions.kt:95-99
    触摸目标宽度是多少?
    assertTouchWidthIsEqualTo(expectedWidth: Dp)
    BoundsAssertions.kt:62-66
    触摸目标高度是多少?
    assertTouchHeightIsEqualTo(expectedHeight: Dp)
    BoundsAssertions.kt:73-77
    根坐标中的精确位置是多少?
    assertPositionInRootIsEqualTo(left: Dp, top: Dp)
    BoundsAssertions.kt:109-117
    仅顶部位置是多少?
    assertTopPositionInRootIsEqualTo(top: Dp)
    BoundsAssertions.kt:126-130
    仅左侧位置是多少?
    assertLeftPositionInRootIsEqualTo(left: Dp)
    BoundsAssertions.kt:139-143
    读取完整的未裁剪边界
    getUnclippedBoundsInRoot(): DpRect
    BoundsAssertions.kt:148-152
    读取已裁剪边界
    getBoundsInRoot(): DpRect
    BoundsAssertions.kt:158-165
    以 dp 表示的对齐线位置
    getAlignmentLinePosition(line: AlignmentLine): Dp
    BoundsAssertions.kt:171-180
    Text 中
    LinkAnnotation
    的边界
    getFirstLinkBounds(predicate)
    BoundsAssertions.kt:196-248
    比较任意两个
    Dp
    值
    Dp.assertIsEqualTo(expected, subject, tolerance = Dp(.5f))
    BoundsAssertions.kt:319-324
  • 2. 布局计算使用未裁剪边界;“用户看到的内容”使用已裁剪边界。
    getUnclippedBoundsInRoot()
    返回忽略视口裁剪的已布局矩形(
    BoundsAssertions.kt:148-152
    → 私有
    unclippedBoundsInRoot
    ,
    BoundsAssertions.kt:284-291
    )。
    getBoundsInRoot()
    会裁剪到视口范围内(
    BoundsAssertions.kt:158-165
    )。padding 和间距计算使用未裁剪边界;部分可见性检查使用已裁剪边界。
  • 3. 默认容差为半个 dp。
    Dp.assertIsEqualTo(expected, subject, tolerance = Dp(.5f))
    (
    BoundsAssertions.kt:319
    )允许最多 0.5 dp 的偏差,因为布局舍入可能产生小于 dp 的偏移。只有在明确的测量契约证明需要更高精度时,才应覆盖默认容差。
  • 4. 通过减去两个未裁剪矩形来计算 padding,然后调用
    Dp.assertIsEqualTo
    。
    这是标准的 material3 模式(
    material3/.../ButtonTest.kt:213-225
    ):
    kotlin
    val buttonBounds = rule.onNodeWithTag(ButtonTestTag).getUnclippedBoundsInRoot()
    val textBounds   = rule.onNodeWithTag(TextTestTag).getUnclippedBoundsInRoot()
    
    (textBounds.left - buttonBounds.left).assertIsEqualTo(
        24.dp,
        "padding between the start of the button and the start of the text.",
    )
    
    (buttonBounds.right - textBounds.right).assertIsEqualTo(
        24.dp,
        "padding between the end of the text and the end of the button.",
    )
    buttonBounds.height.assertIsEqualTo(ButtonDefaults.MinHeight, "height of button.")
    subject
    字符串会出现在失败消息中:
    "Actual padding between the start of the button and the start of the text. is 22.dp, expected 24.dp (tolerance: .5.dp)"
    。
  • 5. 对于最小尺寸契约,使用
    assertHeightIsAtLeast
    /
    assertWidthIsAtLeast
    。
    当 composable 在字体缩放较大时也不得小于某个常量时,此方式非常有用。示例来自
    material/ChipTest.kt:226-233
    :
    kotlin
    rule.setMaterialContent { Chip(onClick = {}) { Text(text = "Test chip", fontSize = 50.sp) } }
    rule.onNode(hasClickAction()).assertHeightIsAtLeast(ChipDefaults.MinHeight + 1.dp)
  • 6. 验证点击目标无障碍时,使用触控边界。
    assertTouchWidthIsEqualTo
    /
    assertTouchHeightIsEqualTo
    读取
    node.touchBoundsInRoot
    (
    BoundsAssertions.kt:270-282
    )。当 composable 应用
    Modifier.minimumInteractiveComponentSize()
    或类似修饰器时,触控边界可能超出视觉边界。视觉边界使用
    getUnclippedBoundsInRoot
    ;触控边界用于回答“点击实际会落在哪里”。

Patterns

模式

Pattern: dp typed assertions over pixel reads

模式:优先使用 dp 类型断言,而非读取像素

kotlin
// WRONG
@Test
fun submit_isMin48dpTall() {
    rule.setContent { CheckoutScreen() }
    val node = rule.onNodeWithTag(SubmitTag).fetchSemanticsNode()
    val heightPx = node.size.height
    assert(heightPx >= 48 * Resources.getSystem().displayMetrics.density)
}
// WRONG because: pixel-typed and density-dependent. Reads outside the framework's tolerance
// model. Failure prints raw integers, no node dump, no subject label.
kotlin
// RIGHT
@Test
fun submit_isMin48dpTall() {
    rule.setContent { CheckoutScreen() }
    rule.onNodeWithTag(SubmitTag).assertHeightIsAtLeast(48.dp)
}
kotlin
// WRONG
@Test
fun submit_isMin48dpTall() {
    rule.setContent { CheckoutScreen() }
    val node = rule.onNodeWithTag(SubmitTag).fetchSemanticsNode()
    val heightPx = node.size.height
    assert(heightPx >= 48 * Resources.getSystem().displayMetrics.density)
}
// WRONG because: pixel-typed and density-dependent. Reads outside the framework's tolerance
// model. Failure prints raw integers, no node dump, no subject label.
kotlin
// RIGHT
@Test
fun submit_isMin48dpTall() {
    rule.setContent { CheckoutScreen() }
    rule.onNodeWithTag(SubmitTag).assertHeightIsAtLeast(48.dp)
}

Pattern: padding by subtracting two unclipped rects

模式:通过减去两个未裁剪矩形计算 padding

kotlin
@Test
fun button_text_has24dpPadding() {
    rule.setContent {
        Button(onClick = {}, modifier = Modifier.testTag(ButtonTestTag)) {
            Text("Submit", modifier = Modifier.testTag(TextTestTag).semantics(mergeDescendants = true) {})
        }
    }

    val buttonBounds = rule.onNodeWithTag(ButtonTestTag).getUnclippedBoundsInRoot()
    val textBounds   = rule.onNodeWithTag(TextTestTag).getUnclippedBoundsInRoot()

    (textBounds.left - buttonBounds.left).assertIsEqualTo(24.dp, "start padding")
    (buttonBounds.right - textBounds.right).assertIsEqualTo(24.dp, "end padding")
}
The merge bypass on the inner
Text
is the same trick used by
material3/ButtonTest.kt:202-226
to keep the inner Text addressable from the merged tree.
kotlin
@Test
fun button_text_has24dpPadding() {
    rule.setContent {
        Button(onClick = {}, modifier = Modifier.testTag(ButtonTestTag)) {
            Text("Submit", modifier = Modifier.testTag(TextTestTag).semantics(mergeDescendants = true) {})
        }
    }

    val buttonBounds = rule.onNodeWithTag(ButtonTestTag).getUnclippedBoundsInRoot()
    val textBounds   = rule.onNodeWithTag(TextTestTag).getUnclippedBoundsInRoot()

    (textBounds.left - buttonBounds.left).assertIsEqualTo(24.dp, "start padding")
    (buttonBounds.right - textBounds.right).assertIsEqualTo(24.dp, "end padding")
}
对内部
Text
使用 merge bypass,与
material3/ButtonTest.kt:202-226
中采用的技巧相同,可确保内部 Text 在合并后的树中仍可被寻址。

Pattern:
assertPositionInRootIsEqualTo
for absolute placement

模式:使用
assertPositionInRootIsEqualTo
进行绝对定位

kotlin
// "the close button sits at (320.dp, 0.dp) in the root"
rule.onNodeWithTag(CloseButtonTag)
    .assertPositionInRootIsEqualTo(expectedLeft = 320.dp, expectedTop = 0.dp)
If only one axis matters, use
assertLeftPositionInRootIsEqualTo
/
assertTopPositionInRootIsEqualTo
to avoid coupling the test to layout decisions on the other axis.
kotlin
// "the close button sits at (320.dp, 0.dp) in the root"
rule.onNodeWithTag(CloseButtonTag)
    .assertPositionInRootIsEqualTo(expectedLeft = 320.dp, expectedTop = 0.dp)
如果只关心一个轴,应使用
assertLeftPositionInRootIsEqualTo
/
assertTopPositionInRootIsEqualTo
,避免测试与另一个轴上的布局决策耦合。

Pattern: alignment line for baseline math

模式:使用 alignment line 进行基线计算

kotlin
val baselineDp = rule.onNodeWithTag(LabelTag)
    .getAlignmentLinePosition(FirstBaseline)
require(!baselineDp.isUnspecified) { "Label has no first baseline" }
baselineDp.assertIsEqualTo(20.dp, "first baseline of label")
getAlignmentLinePosition
returns
Dp.Unspecified
when the alignment line is not provided (
BoundsAssertions.kt:172-179
). Always check
isUnspecified
before comparing.
kotlin
val baselineDp = rule.onNodeWithTag(LabelTag)
    .getAlignmentLinePosition(FirstBaseline)
require(!baselineDp.isUnspecified) { "Label has no first baseline" }
baselineDp.assertIsEqualTo(20.dp, "first baseline of label")
未提供 alignment line 时,
getAlignmentLinePosition
会返回
Dp.Unspecified
(
BoundsAssertions.kt:172-179
)。比较之前务必检查
isUnspecified
。

Pattern: tolerance override for sub-dp precision

模式:为亚 dp 精度覆盖容差

kotlin
// Most tests want the default ½ dp tolerance:
rule.onNodeWithTag(IconTag).getUnclippedBoundsInRoot().width.assertIsEqualTo(24.dp, "icon width")

// Stricter tolerance when measuring a hand-aligned constant:
val width = rule.onNodeWithTag(IconTag).getUnclippedBoundsInRoot().width
width.assertIsEqualTo(expected = 24.dp, subject = "icon width", tolerance = 0.1.dp)
kotlin
// Most tests want the default ½ dp tolerance:
rule.onNodeWithTag(IconTag).getUnclippedBoundsInRoot().width.assertIsEqualTo(24.dp, "icon width")

// Stricter tolerance when measuring a hand-aligned constant:
val width = rule.onNodeWithTag(IconTag).getUnclippedBoundsInRoot().width
width.assertIsEqualTo(expected = 24.dp, subject = "icon width", tolerance = 0.1.dp)

Pattern: clipped vs unclipped — partial visibility

模式:已裁剪与未裁剪——部分可见性

kotlin
val unclipped = rule.onNodeWithTag(BannerTag).getUnclippedBoundsInRoot()
val clipped   = rule.onNodeWithTag(BannerTag).getBoundsInRoot()

// Banner laid out 200 dp tall but only 80 dp visible (rest clipped by parent):
unclipped.height.assertIsEqualTo(200.dp, "banner intrinsic height")
clipped.height.assertIsEqualTo(80.dp, "banner visible height")
For "is any of it visible", prefer
assertIsDisplayed()
— see
./asserting-node-state-and-text/SKILL.md
.
kotlin
val unclipped = rule.onNodeWithTag(BannerTag).getUnclippedBoundsInRoot()
val clipped   = rule.onNodeWithTag(BannerTag).getBoundsInRoot()

// Banner laid out 200 dp tall but only 80 dp visible (rest clipped by parent):
unclipped.height.assertIsEqualTo(200.dp, "banner intrinsic height")
clipped.height.assertIsEqualTo(80.dp, "banner visible height")
如果只需判断“是否有任何部分可见”,优先使用
assertIsDisplayed()
——参见
./asserting-node-state-and-text/SKILL.md
。

Mandatory rules

强制规则

  • MUST assert in dp using the typed
    assertWidthIsEqualTo
    /
    assertHeightIsEqualTo
    /
    assertPositionInRootIsEqualTo
    . MUST NOT read
    fetchSemanticsNode().size.width
    and compare pixels.
  • MUST use
    getUnclippedBoundsInRoot()
    for padding / gap / alignment math; MUST use
    getBoundsInRoot()
    only when the contract is "what the user sees after clipping".
  • MUST pass a meaningful
    subject
    string to
    Dp.assertIsEqualTo
    so the failure message identifies which measurement failed.
  • MUST prefer
    assertHeightIsAtLeast(MinHeight + 1.dp)
    over
    assertHeightIsEqualTo(MinHeight + N.dp)
    when the goal is "the layout grows past the minimum at large font scales".
  • MUST NOT assume zero tolerance. Layout rounding produces sub-dp drift; rely on the half-dp default and override only when justified.
  • PREFERRED: when an animation is in flight, pause
    mainClock.autoAdvance = false
    and step deterministically before reading bounds. Skydoves hot take #3.
  • 必须使用类型化的
    assertWidthIsEqualTo
    /
    assertHeightIsEqualTo
    /
    assertPositionInRootIsEqualTo
    以 dp 进行断言。不得读取
    fetchSemanticsNode().size.width
    后比较像素值。
  • 必须使用
    getUnclippedBoundsInRoot()
    进行 padding、间距或对齐计算;只有在契约要求表示“用户裁剪后看到的内容”时,才使用
    getBoundsInRoot()
    。
  • 必须向
    Dp.assertIsEqualTo
    传入有意义的
    subject
    字符串,使失败消息能够指出具体失败的测量项。
  • 当目标是“在大字体缩放下,布局会增长到最小尺寸之上”时,必须优先使用
    assertHeightIsAtLeast(MinHeight + 1.dp)
    ,而不是
    assertHeightIsEqualTo(MinHeight + N.dp)
    。
  • 不得假定容差为零。布局舍入会产生小于 dp 的偏移;应依赖默认的半个 dp 容差,仅在有充分依据时覆盖。
  • 优先做法: 动画正在执行时,将
    mainClock.autoAdvance = false
    并以确定性方式逐步推进,然后再读取边界。Skydoves 的尖锐观点 #3。

Verification

验证

  • No
    node.size.width
    /
    node.size.height
    reads remain. All dimension checks use the typed
    assert*IsEqualTo
    /
    Dp.assertIsEqualTo
    .
  • Padding / gap math uses
    getUnclippedBoundsInRoot
    ; clipped reads only appear with a comment explaining why.
  • Every
    Dp.assertIsEqualTo(...)
    passes a non-empty
    subject
    string.
  • Touch-target assertions use
    assertTouchWidthIsEqualTo
    /
    assertTouchHeightIsEqualTo
    rather than visual bounds when verifying accessibility constraints.
  • ./gradlew :app:connectedDebugAndroidTest
    passes; failure messages identify the specific failed measurement by
    subject
    .
  • 不再存在
    node.size.width
    /
    node.size.height
    读取。所有尺寸检查均使用类型化的
    assert*IsEqualTo
    /
    Dp.assertIsEqualTo
    。
  • Padding 和间距计算使用
    getUnclippedBoundsInRoot
    ;只有在注释说明原因时,才会出现已裁剪边界读取。
  • 每个
    Dp.assertIsEqualTo(...)
    都传入非空的
    subject
    字符串。
  • 验证无障碍约束时,触摸目标断言使用
    assertTouchWidthIsEqualTo
    /
    assertTouchHeightIsEqualTo
    ,而不是视觉边界。
  • ./gradlew :app:connectedDebugAndroidTest
    通过;失败消息通过
    subject
    标识具体失败的测量项。

References

参考资料

  • Compose testing overview: https://developer.android.com/develop/ui/compose/testing
  • Compose testing cheat sheet: https://developer.android.com/develop/ui/compose/testing-cheatsheet
  • Layout in Compose: https://developer.android.com/develop/ui/compose/layouts
  • compose/ui/ui-test/src/commonMain/kotlin/androidx/compose/ui/test/BoundsAssertions.kt
    —
    assertWidthIsEqualTo
    ,
    assertHeightIsAtLeast
    ,
    assertPositionInRootIsEqualTo
    ,
    getUnclippedBoundsInRoot
    ,
    getBoundsInRoot
    ,
    getAlignmentLinePosition
    ,
    getFirstLinkBounds
    ,
    Dp.assertIsEqualTo
    (default tolerance ½ dp).
  • compose/material3/material3/src/androidDeviceTest/kotlin/androidx/compose/material3/ButtonTest.kt:202-226
    — canonical "subtract two unclipped rects" padding test.
  • compose/material/material/src/androidDeviceTest/kotlin/androidx/compose/material/ChipTest.kt:226-233
    —
    assertHeightIsAtLeast(MinHeight + 1.dp)
    for minimum-touch contracts.
  • Compose 测试概览:https://developer.android.com/develop/ui/compose/testing
  • Compose 测试速查表:https://developer.android.com/develop/ui/compose/testing-cheatsheet
  • Compose 中的布局:https://developer.android.com/develop/ui/compose/layouts
  • compose/ui/ui-test/src/commonMain/kotlin/androidx/compose/ui/test/BoundsAssertions.kt
    ——
    assertWidthIsEqualTo
    、
    assertHeightIsAtLeast
    、
    assertPositionInRootIsEqualTo
    、
    getUnclippedBoundsInRoot
    、
    getBoundsInRoot
    、
    getAlignmentLinePosition
    、
    getFirstLinkBounds
    、
    Dp.assertIsEqualTo
    (默认容差为 ½ dp)。
  • compose/material3/material3/src/androidDeviceTest/kotlin/androidx/compose/material3/ButtonTest.kt:202-226
    ——标准的“减去两个未裁剪矩形”padding 测试。
  • compose/material/material/src/androidDeviceTest/kotlin/androidx/compose/material/ChipTest.kt:226-233
    ——用于最小触摸目标契约的
    assertHeightIsAtLeast(MinHeight + 1.dp)
    。