Repository navigation
Conversation
…alert Measured on a Wear OS 5.1 emulator (API 35, round 454x454) for the docs evaluation's question about Wear OS. The Android backends drive it, and three things were wrong on its first screens: - CHALLENGES 315: a Wear chip is a Button whose text repeats its title's TextView, so text="Security" matched two and every row was refused. On Android, a non-target inside a target text= also matched is its title. - CHALLENGES 316: a toggle chip holds its switch and the switch's container, checkable and not clickable, so map listed each switch three times. A checkable part of a clickable checkable control is not a target. - CHALLENGES 317: Wear's own dialog was no dialog to app_alert. It is known by its layout's ids, and accept and dismiss press its marked positive and negative buttons. docs/checks/wear-os.sh drives Wear's Settings by locator; it passed on the headed emulator every run and fails at its first tap with main's binary. README, SETUP and ROADMAP say what was measured and what is left: a real watch, and the crown.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Measured on a Wear OS 5.1 emulator (API 35, round 454×454) for the docs evaluation's question about Wear OS. The Android backends drive it; three things were wrong on its first screens:
text="Security"matched two and every row was refused. On Android, a non-target inside a target thattext=also matched is its title.maplisted each switch three times. A checkable part of a clickable, checkable control is not a target.app_alert. It is known by its layout's ids, andaccept/dismisspress its marked ✓ and ✕.docs/checks/wear-os.shdrives Wear's Settings by locator: passed every run on the headed emulator (~20s), and fails at its first tap withmain's binary. Four new tests on hierarchies captured from the watch, each failing on the old code. README "Platforms", SETUP and ROADMAP say what was measured and what is left: a real watch, and the crown.