1807300 - Support UI testing composables by using testTag

Status: NEW

(Firefox for Android :: UI Tests, task, P3)

Description

[Chris Peterson [:cpeterson]]

From github: https://github.com/mozilla-mobile/fenix/issues/26826.

After discussing with the QA team it was apparent that testing is currently hindered by the inability / inefficiency of identifying composables on the screen.
testTags are the approach recommended by the Compose team to help with that - https://developer.android.com/jetpack/compose/testing and we are already using them in A-C - https://searchfox.org/mozilla-mobile/search?q=testTag&path=&case=true&regexp=false

I propose starting to add (even retroactively for the scenarios raised by QA) testTags to the composables used on Fenix with the following naming scheme:

<feature>.<composable>(.<optional other sub composables>)

Compose v1.2 will also allow better interoperability with UIAutomator by allowing the testTags to be used in already common calls in the form of

findObject(By.res(<testTag>)).

An update to this newer version is prepared in https://github.com/mozilla-mobile/fenix/pull/26763.

┆Issue is synchronized with this Jira Task

Change performed by the Move to Bugzilla add-on.

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

The severity field is not set for this bug.
:rpapa, could you have a look please?

For more information, please visit auto_nag documentation.