In Part 1 we covered what Maestro is, how it works and how it compares to Appium, XCUITest, Detox and the paid device clouds. Now it is time to write real tests.

In this article we will:

Build a small SwiftUI app with a login screen and a to-do list.

Make it testable with accessibility identifiers.

Write a Maestro suite with reusable sub-flows, environment variables, conditional logic, JavaScript and tags.

Run it locally, generate reports and debug failures.

Look at how the same test would look in XCUITest, and where AI agents fit in.

Everything here uses the free, open-source Maestro CLI.…