Post
4. Why? The prev idea is still my favorite but has a lot of edge cases (e.g. what about all the components that are undetected by a Fabric tree traversal?). Removing the newArch assumption also simplifies maintenance a ton and (potentially) opens the door to all native apps.
0 reposts0 likes
6. This is an experimental project that aims to be ~4x faster than maestro given the same .yaml suite on React Native/Expo apps. The project is open source: github.com/enzomanuelm...
github.comGitHub - enzomanuelmangano/ennio: maestro-compatible e2e test runner for React Nativemaestro-compatible e2e test runner for React Native - enzomanuelmangano/ennio