Open varun-batta-vc opened 3 years ago
There is a PR with a fix for this: https://github.com/facebook/react-native/pull/29610
Any update for IOS on this ?
Facing the same issue 0.64.2
⚠️ NOTE:
This problem is not actual starting from react-native@0.65.x
, CHANGELOG:
Display the testID as the resource-id for black-box testing frameworks ( #381fb3 by @jdeff)
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as a "Discussion" or add it to the "Backlog" and I will leave it open. Thank you for your contributions.
We have the same issue and we are also trying to figure out the relation between those 3 props. It's hard to give a how to write end-2-end guide without knowing how they are related and impact each other.
Have you succeed ? This should be flagged as major bug btw.
Same Problem.
Same problem... very frustrating
This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 7 days.
Pls don't close until it is fixed. Thanks 🙌
Description
When inspecting a react-native app on Android via Appium, testing identifiers like
testID
oraccessibilityLabel
sometimes appear and sometimes don't. There is no major difference in how nested the elements are for when they appear and when they don't - they just sometimes don't. This is not an issue on iOS, everything works fine there.Whether, as has been mentioned in various places, I put
testID
,testID
&accessibilityLabel
or justaccessibilityLabel
the issue is there. Whether or not I add the prop ofaccessible={true}
or not, the issue is there.React Native version:
expect(await driver.hasElementByAccessibilityId('container')).toBe(true); expect(await driver.hasElementByAccessibilityId('testText')).toBe(true);