Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AutomationId is mapped wrong #39

Open
1 task
SigiNeumann opened this issue Jan 31, 2025 · 0 comments
Open
1 task

AutomationId is mapped wrong #39

SigiNeumann opened this issue Jan 31, 2025 · 0 comments

Comments

@SigiNeumann
Copy link

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

  1. Add an AutomationID
  2. Run App
  3. 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant