Post

I've completely reworked the core of Ennio. It's now much easier to get started. running e2e tests in react native has to be faster 🧵

Enzo Manuel Mangano

@reactiive.io

2 June

1. I introduced Ennio a few weeks ago (still experimental). The long-term goal is to run e2e tests in a very fast and reliable way. The focus is on RN/Expo apps, but theoretically, it should now work with any iOS project (sim only).

Enzo Manuel Mangano

@reactiive.io

2 June

2. It's no longer a native package, but a dev dependency (still requires idb right now, but no prebuilds). You can install it and test it in less than 10 seconds.

Enzo Manuel Mangano

@reactiive.io

3. I had to rethink the initial architecture a lot. Now it doesn't make assumptions. The search no longer happens via the Fabric tree - it's based on a native UIView traversal. This works perfectly in React Native because, of course, any React Native component is a real native component.

2/6/26, 6:26 pm0 reposts0 likes

Enzo Manuel Mangano

@reactiive.io

2 June

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.

Enzo Manuel Mangano

@reactiive.io

2 June

5. plan_md - simplify package installation ✅ - remove idb dependency - ensure it’s stable for production-grade open source apps - provide an easy way to run it in ci - provide a simple interface to run agentic testing on top of it (?)

Enzo Manuel Mangano

@reactiive.io

2 June

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