You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In XF Automation ID was mapped to ContentDescription in Android(View).
This changed in MAUI where the changed it to map to resource-id :( (which made a lof of people unhappy)
see: dotnet/maui#4714 (comment)
Anyway Cells still use the "old" Xamarin approach which makes it hard to use e.g. accesibiltyIDs vs. IDs in Appium.
Also not only is automationId on another attribute it gets prefixed with some identifier.
so.
content-desc="Wzd_Next"
becomes
resource-id="com.mycompany.myproject.myappapp:id/Wzd_Next
Steps to Reproduce
Add an AutomationID
Run App
Test with Appium
Expected Behavior
AutomationId gets mapped like other elements in MAUI to resource-id
Actual Behavior
gets mapped to ContentDescription
Platforms
[x ] Android
iOS (not tested)
Basic Information
Workaround
In Appium, using old locators for SettingsView and new locators for other elements
The text was updated successfully, but these errors were encountered:
Description
In XF Automation ID was mapped to ContentDescription in Android(View).
This changed in MAUI where the changed it to map to resource-id :( (which made a lof of people unhappy)
see:
dotnet/maui#4714 (comment)
Anyway Cells still use the "old" Xamarin approach which makes it hard to use e.g. accesibiltyIDs vs. IDs in Appium.
Also not only is automationId on another attribute it gets prefixed with some identifier.
so.
content-desc="Wzd_Next"
becomes
resource-id="com.mycompany.myproject.myappapp:id/Wzd_Next
Steps to Reproduce
Expected Behavior
AutomationId gets mapped like other elements in MAUI to resource-id
Actual Behavior
gets mapped to ContentDescription
Platforms
Basic Information
Workaround
In Appium, using old locators for SettingsView and new locators for other elements
The text was updated successfully, but these errors were encountered: