Dan Caseley
Dan Caseley
I _think_ it's a flake. I've re-run them to find out.
> OK, @Fishbowler I've got the tests passing: [mobile-dev-inc/demo_app#6](https://github.com/mobile-dev-inc/demo_app/pull/6) I know it's a bit mad, but the tests that prove Maestro but _rely_ on Demo App go into Maestro, in...
I retract my point. It was about where tests go, but I see you've done a different approach for both repos, and is consistent.
Have you taken a look at this bit of the docs? https://docs.maestro.dev/platform-support/react-native#interacting-with-nested-components-on-ios
Given this issue has gone quiet, I'm gonna assume it was solved. Shout up if I'm wrong.
Rebased.
You've mentioned missing the "changes accepting flow". What have you got in mind for the workflow for a failure where the new "look" is as-intended?
I switched all of my tests from Rhino to GraalJS. No issues encountered, no changes needed. :+1:
Is there a reason to limit it to id than reuse the existing complex element selector logic that exists for other commands?