Setting accessibilityLabel to testID in production is not a good idea

[LeoNatan]

accessibilityLabel is used by the iOS system to help handicapped users. For instance, Voice Over uses this.

If you set some testing value to this, your handicapped users will suffer.

[LeoNatan]

Differentiate accessibilityIdentifier and accessibilityLabel.

[isnifer]

@LeoNatan look into the code. I'm using testID for iOS.

[LeoNatan]

On Android it’s exactly the same problem:
https://developer.android.com/training/accessibility/accessible-app.html

[LeoNatan]

Google TalkBack uses that to read the content description to the user. Exactly the same as Voice Over on iOS.

[isnifer]

@LeoNatan sadly, but Appium does not work otherwise

[LeoNatan]

Then fix Appium. Disabled users should not suffer because some test framework is buggy. Sorry

[isnifer]

@LeoNatan yes, of course

[isnifer]

@LeoNatan we are using Appium until Detox doesn't work with it like with iOS :)

[LeoNatan]

It is being worked on actively.

[simonracz]

Just a side note: Detox Android works with test id already.

Appium can't see test ids, because they are transferred to view tags on Android. (You probably know about this.)
View tags are not accessible for UIAutomator, on which Appium depends on.

[isnifer]

@simonracz yes, I know. Thank you.
If I understand correctly I need only testID for both platforms if I will use detox only, yes?

[LeoNatan]

Yes, that is the best way to test. byText is not optimal because if you localization, it will fail your test.

[isnifer]

@LeoNatan good to know. So, for now, we are using Appium only to check Auth via Twitter and FB, also to test Apple Pay, cause EarlGrey can't do that.