Replies: 1 comment
-
|
I believe this query is better asked in an Appium support channel as WebdriverIO has no influence how the mobile device/emu/simulator renders the application. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
we are experiencing an issue with our Android app during automated testing with Appium (v2.19.0). Some text elements rendered using Material Design components appear in the accessibility/UI hierarchy (XML) with a significant delay after the screen is opened.
Specifically:
• When the screen is displayed, the element is not present in the initial UI hierarchy (no TextView node or text).
• Only after leaving the screen and coming back (or after a full redraw), the element finally appears in the hierarchy.
• Because of this, Appium cannot locate the element in time, and tests fail.
Example:
<android.view.View resource-id="wrap"> <android.widget.TextView text="Vyber pracoviště k přihlášení"> </android.view.View>This TextView sometimes appears late in the XML, even though it is already visible on the screen for the user.
This behavior causes automated tests to fail randomly because the element is missing from the DOM when Appium queries it.
We use the following setup:
• Framework: WebdriverIO (Mocha)
• Automation: Appium 2.19.0 with UiAutomator2
• Platform: Android Emulator
• Capabilities:
• appium:ignoreUnimportantViews = true
• appium:appWaitActivity = *
• appium:autoGrantPermissions = true
• appium:noReset = true
• appium:fullReset = false
Thank you for your help!
Beta Was this translation helpful? Give feedback.
All reactions