🤯 Guess what the core React Native team at Meta is using for e2e testing of the React Native framework itself? Yup - Maestro 😍 Check out their test suite on GitHub: https://lnkd.in/gFhf2qui The best part? They already have test coverage that validates Maestro compatibility with the new React Native architecture! 🙌 🙌 🙌 https://lnkd.in/g4D3SzFT Why does this matter? - There are official tests in the React Native repository guaranteeing that Maestro works well with the core React Native framework components - today and in the future! - The core React Native team at Meta is using Maestro for e2e testing - you probably should be doing the same! 🧑💻 If you haven't already, it's time to check out Maestro for your e2e testing on Mobile and Web ↓
mobile.dev
Software Development
San Francisco, CA 4,233 followers
Maestro - E2E testing for Mobile & Web
About us
Maestro - E2E testing for Mobile & Web
- Website
-
https://maestro.dev/
External link for mobile.dev
- Industry
- Software Development
- Company size
- 2-10 employees
- Headquarters
- San Francisco, CA
- Type
- Privately Held
Locations
-
Primary
Get directions
San Francisco, CA, US
Employees at mobile.dev
Updates
-
Another great real-world story of Maestro adoption - this time within Eneco, one of the biggest energy suppliers from the Netherlands! Dive into the full conversation here: https://lnkd.in/gDSyBqGr Here's a clip from the conversation between our co-founder Jacob Krupski and Randy Sie - their Automation Lead who ran the evaluation, got leadership buy-in (including the CEO), and drove adoption of Maestro within Eneco:
-
mobile.dev reposted this
Shoutout to this guy and our crew at mobile.dev Test automation just keeps getting easier and easier with Maestro 🪄
-
-
We've heard that the bottleneck to get started with Maestro is often the environment setup - as opposed to the setup of the tool itself up. That's why we're starting a series of instructional YouTube videos that help with getting your testing environment set up. Starting with... How to install the iOS Simulator on Mac ▶️ Watch on YouTube: https://lnkd.in/g3DMsUqE Let us know what you think! Much more to come, so make sure to subscribe to our YouTube Channel: https://lnkd.in/gMf5YQcH
-
📣 Introducing: Maestro Webhooks 📣 Run Maestro tests in the cloud & sync results anywhere ⚡ Full announcement: https://lnkd.in/gmTQyynd Maestro Webhooks allows you to integrate Maestro test results with any tool or workflow: • Sync results to internal dashboards or issue trackers • Trigger notifications on failed test flows • Kick off CI/CD pipelines after an upload completes • Integrate test workflow with other internal systems Setting up a Maestro Webhook is simple: • Navigate to your settings in the Maestro Console (app.maestro.dev) • Enter the URL of your webhook endpoint • That’s it! Your endpoint will receive a POST request with the webhook payload every time a new upload completes Webhook Integration is available today for all users on a Maestro Cloud Plan New to Maestro? Get started with the simplest, most powerful, and most trusted E2E testing platform for Mobile and Web at maestro.dev
-
-
👀 We're Hiring! Sound like you or someone you know?
📣 We're actively looking for an Mobile platform engineer to join the team 📣 At mobile.dev, we're building the future of automated testing and QA. Maestro - our next-gen testing platform for Mobile and Web - has already been adopted at companies like Meta, Uber, Stripe, DoorDash, Block, and Disney - And it's a favorite among smaller teams and individual developers as well. Some recent highlights: • 7x+ revenue from last year already • Hit front page of Hacker News • +1K GitHub star growth in the last 3 weeks (7.5k total) We're building a best-in-class Mobile E2E testing framework and hosted Mobile device cloud platform. Both require deep Mobile tooling / platform expertise, so we're looking for a great Mobile platform engineer to join the team! Here's an idea of what we're looking for: • Experience working with private APIs on iOS • Built reliable iOS simulator infrastructure at scale • Worked with Virtualization.Framework directly or via eg. Tart / Orka / etc • Android tooling expertise (though iOS exp is more of a requirement) If this sounds like you please DM me here or email me at leland@mobile.dev If this sounds like someone you know - tag them in the comments below ⬇️ Full JD for reference: https://lnkd.in/gRWvWrGB
-
-
Maestro just got even easier 😍 📣 Starting today, you can chat with MaestroGPT to answer your Maestro questions or generate Maestro code: https://lnkd.in/gQ6Uf3YZ 📖 MaestroGPT has a full understanding of Maestro syntax and live access to Maestro documentation, ensuring its knowledge is always up-to-date 🧠 🚀 We're already working on enabling MaestroGPT to interact directly with your device and iterate on your Maestro flows. This will also lay the groundwork for Maestro MCP, a powerful Maestro MCP server currently under development! 💬 Log in to the Maestro Console (app.maestro.dev) to start chatting with MaestroGPT.
-
mobile.dev reposted this
Lead Software Engineer @ MyWheels | Mastering React Native for optimal product, UX, and DevX | Passionate about Open Source contributions
🚀 Super stoked to be featured in This Week In React! 🎉 My latest blog post, "How to build a solid test harness for Expo apps", was highlighted in the newsletter! Huge shoutout to Expo, Callstack and mobile.dev for making testing in React Native smoother than ever. Check it out here 👉 This Week In React #225 https://lnkd.in/dAVYhfFy If you're working with Expo and want to improve your testing workflow, give it a read and let me know your thoughts! #ReactNative #Expo #Testing #ThisWeekInReact
-
Testing mobile apps is a huge challenge, especially in highly regulated fields like healthcare. Doccla struggled with manual testing—until they found Maestro, the simple E2E automated testing platform that empowered their team to test *more* and ship *faster*. Dive into their journey and full interview: https://lnkd.in/g_TEEC7H Short clip from the discussion below ⬇️
-
mobile.dev reposted this
Lead Software Engineer @ MyWheels | Mastering React Native for optimal product, UX, and DevX | Passionate about Open Source contributions
I was flattered to be invited to write another blog article for Expo, and this time it’s about one of my biggest passions: testing in React Native and Expo apps! In this article, I dive deep into how to establish a solid test harness—one that gives you confidence to ship without fear, catch bugs before your users do, and iterate faster. This is a topic I care about deeply, and I’m super stoked and proud of how this one turned out! 🔗 Check out the full blog post: https://lnkd.in/gWrTv7tD I’d love to hear your thoughts! How do you test your React Native/Expo apps? Did you learn anything new from this post? Let’s exchange insights! 💬
🛡️ Do you treat testing as a tedious chore or a supportive friend? For React Native developers using Expo, a solid test harness can be the path not only to strong apps but also peace of mind. 🚗 Steve Galili sees testing as a safety net that catches bugs before your users do, allowing you to ship with confidence. He shares his whole philosophy in our latest blog post (link below). Check out some of the key takeaways: ✅ Testing Pyramid for Balance: Build a foundation of fast unit tests, add a layer of integration tests for modules working together, and cap it with a few E2E tests that simulate real user flows. This pyramid keeps your test suite fast, thorough, and reliable. ✅ Practical Expo Strategies: Leverage Jest and React Native Testing Library for component tests. Use tools like Maestro for end-to-end testing (yes, you can E2E test Expo apps!). Set up a dedicated Expo dev build or config for testing to mirror production behavior. ✅ Avoid Common Pitfalls: Don’t rely only on slow end-to-end tests or over-mock your app until tests lose meaning. Avoid flaky tests by cleaning up after each run (no shared state!). Ensure your tests are deterministic and reflect real usage as much as possible. ✅ Coverage vs. Real World: High coverage is nice, but meaningful coverage is crucial. Focus on critical user paths and edge cases. It’s better to have 80% coverage with robust tests than 100% coverage of trivial scenarios. Aim for quality, not just quantity. ✅ Confidence to Refactor: With a solid harness, you can refactor or add features without fear. Your tests will catch regressions early. That means faster iterations and happier users (and developers!). 🔗 Read the full blog for code snippets & detailed insights: https://lnkd.in/gWrTv7tD 💬 Join the conversation: How have tests saved you in your projects? Any tips for testing Expo/React Native apps? Share your experiences and let’s learn from each other!
-