Repository navigation
app_wait_for: an example for selected (mobiumdev/mobium#229) - #12
Merged
Merged
Conversation
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.
mobiumdev/mobium#229 added
selectedandunselectedtoapp_wait_for's conditions: what the platform marks selected, such as a tab, a segment or an option drawn as a button. This adds a fourthapp_wait_forscenario, "Wait for a tab to be selected" (mobium wait label=Cart --for selected), with its translation in each of the five clients.It isn't on
capture.py's list. Neither the Android 15 emulator's Settings nor MobiumApp has an element marked selected, so it has no recorded output, like the other uncaptured examples.npm run genandnpm run checkpass against Mobium9337299: 111 scenarios with 0 problems, and every client compiles or type-checks.