Maestro: Reliable E2E testing made easy

End-to-end tests are often brittle, slow, and painful to maintain. But what if you could write E2E tests as easily as user stories, run them locally and in CI, and skip the flaky UI tests that break on every layout change?

In this talk, I’ll walk you through how Maestro, an open-source mobile UI testing framework, is reshaping the way we think about mobile E2E testing. We’ll explore how to set it up in under 5 minutes, write human-readable flows, integrate with CI, and gain confidence in your critical user journeys - from login to money transfer.

Whether you’re a test automation skeptic or looking for simpler tools, this session will give you a practical, production-ready approach to mobile E2E testing.

Transcript

1. Maestro 09 | 2025 1
2. Topic Zhanibek Marshal Senior Engineer at Trade Republic Hello, World! Hallo, Сəлем, Selam, Привет, こんにちは 👋 • LinkedIn: linkedin.com/in/johnmarshal • Mastodon: @zhanibek@androiddev.social • TR engineering blog: engineering.traderepublic.com 2
3. 01. The Problem E2E testing is complex, slow feedback and fragile 02. Integration of Maestro Explanation of the steps taken to integrate Maestro into Android project and iOS 03. Writing Test Case Overview of the approach to writing test case flows using Maestro 04. Maestro Studio An overview of Maestro Studio, the integrated development environment (IDE) for creating Maestro test cases. 05. Best Practices All views mine, no one else’s. 3
4. The problem E2E testing is complex, slow feedback and fragile 4
5. We are automating manual regression testing and doing it well And we got over 2700 test case 5
6. 1. Develop a feature 2. Test this feature 3. Release to production 4. Automate regression test scenario with UI test 6
7. 1. Develop a feature 2. Test this feature 3. Release to production 4. Automate regression test scenario with UI test 7
8. 1. Develop a feature 2. Test this feature 3. Release to production 4. Automate regression test scenario with UI test 8
9. 1. Develop a feature 2. Test this feature 3. Release to production 4. Automate regression test scenario with UI test 9
10. 1. Develop a feature 2. Test this feature 3. Release to production 4. Automate regression test scenario with UI test 10
11. 1. Develop a feature 2. Test this feature 3. Release to production 4. Automate regression test scenario with UI test 11
13. Integration of Maestro Explanation of the steps taken to integrate Maestro into Android project 13
14. Topic Run the following command to install Maestro on Mac OS, Linux or Windows (WSL) Install Maestro 14
15. Will automatically detect and use any local emulator or physical device. Run Maestro test 15
16. If you need a device farm running Maestro tests Run Maestro test on Cloud 16
17. If you need a device farm running Maestro tests - easy to integrate to your CI Run Maestro test on Cloud 17
18. But what if you want to custom integrate to your CI Run Maestro test on your CI 18 1. Boot your device on CI 2. Install APK to the device 3. maestro test --format junit myFolderWithTests/ 4. Export the result to your test automation report
19. Writing Test Case Flows Overview of the approach to writing test case flows using Maestro 19
20. Topic • launchApp • tapOn - tap on anything that visible on screen • inputText • runFlow - run commands from another file • takeScreenshot - saves a screenshot in a PNG file • assertVisible Common commands 20
21. Started from Login flow 21
22. appId: specify the application id to launch the application 22
23. appId: specify the application id to launchApp 23
24. tapOn: anything on a view 24
25. inputText: regardless of whether any text field is currently focused or not 25
26. env: 1. Supply env variable to test: $maestro test -e ... 2. Consume: —> 26
27. tapOn: id of the view* *not preferred option to consider a11y 27
28. assertVisible: same parameters as tapOn 28
29. runFlow: to avoid duplication of code and thereby modularize your Flow files 29
30. Let try to check our first screen - Login “ 30
31. Topic Now you can write a test cases 31
33. Maestro Studio An overview of Maestro Studio, the integrated development environment (IDE) for creating Maestro test cases. 33
34. Topic Run $maestro studio on command line 34
36. Learnings *All views mine, no one else’s 36
37. 1: Don’t rely on id and instead access by text Then we can run regression testing on both Android and iOS 37
38. 2: Don’t rely on id and instead access by text Then we can find many issues with a11y and improve them 38
39. Topic 39 © TRADE REPUBLIC BANK 2023 |Maestro - UI testing framework
40. 3: It’s really easy to write a regression test No extra setup required on a platform and everybody without knowledge of the platform can write them. 40
41. 4: For some use cases I had to write js code Like using runScript command to retrieve OTP code on login flow 41
42. 5: Worth to check recipes and get updated with new changes 42
43. 6: It’s very quick to automate regression tests 43
45. 45 Maestro 2.0 And many more new features that I was not aware
46. • Maestro documentation: https://maestro.mobile.dev/ • Maestro Cloud: https://maestro.dev/cloud • More best practices: https://docs.maestro.dev/advanced/recipes Related links 46
47. THANK 47