Feature Request: compose/click module could use a TestTag semantic property as a fallback to set clickable element name

[Mateusz-Stasielowicz]

A proposal to use the SemanticsProperties.TestTag as a fallback in compose/click module to discover clicked node name and send it as app.widget.name.

Currently only SemanticsActions.OnClick and SemanticsProperties.ContentDescription are discovered on clickable composable element to get the name of clicked widget.

In many cases the TestTag is used on the clickable elements for further testing purposes and it would be nice to have this also as an option in open-telemetry to not duplicate multiple semantic properties with the same value.

code snippet

val testTagSemanticsConfiguration = getOrNull(SemanticsProperties.TestTag)
if (testTagSemanticsConfiguration.isNullOrBlank().not()) {
    return testTagSemanticsConfiguration
}

[breedx-splk]

Thanks @Mateusz-Stasielowicz. Just to be clear -- you want this as a fallback and not the primary, correct? In other words, continue using the existingSemanticsProperties.OnClick and SemanticsProperties.ContentDescription, but also check for the SemanticsProperties.TestTag before resorting to the class name? Do I have that right?

[Mateusz-Stasielowicz]

Thanks @Mateusz-Stasielowicz. Just to be clear -- you want this as a fallback and not the primary, correct? In other words, continue using the existingSemanticsProperties.OnClick and SemanticsProperties.ContentDescription, but also check for the SemanticsProperties.TestTag before resorting to the class name? Do I have that right?

Yes that was the first idea. I will revisit the requirement on my side. Need to check if the TestTag could the primary option.
I proposed to use the TestTag as a fallback to keep the backward compatibility, but as current state of the opentelemetry-android is alpha, it could be also used as the primary one.