XCUITest needs a Mac. Pie needs a build.

Take test writing off your iOS developers. Pie’s agents explore your build and write the tests, with no Swift for your team to write.

Pie

Pie is an agentic testing platform that writes iOS tests from a simulator build. Agents explore the app, with no Swift to write and no Mac to run tests on.

XCUITest

XCUITest is Apple’s UI automation framework, built into Xcode. Your iOS developers write each test in Swift and run it on a Mac or on Xcode Cloud.

The basics

Pie vs XCUITest at a glance

PieAgentic testing platform
What it is
An agentic testing platform for web, iOS and Android apps.
Who writes the tests
Pie’s agents explore your app and generate them. Your team adds the cases that matter in plain English.
What a test is
Plain-English steps and checks. No scripts to write, no locators to break.
Where it runs
iOS apps on the iOS Simulator, Android apps on the Android Emulator, and web apps in a browser. Nothing to install.
AI help
The whole product. Agents explore, write and run the tests, and group what they find into issues.
XCUITestApple’s UI testing framework
What it is
Apple’s UI automation framework, built into Xcode and used with XCTest.
Who writes the tests
Your iOS developers, in Swift. Xcode can record your taps as code for them to finish.
What a test is
Swift code that finds an element, often by an accessibility identifier, acts on it, then asserts.
Where it runs
On a Mac, against simulators and devices, or on Xcode Cloud.
AI help
Xcode 27’s coding agents can boot a simulator, tap through the app and take screenshots to check their work.
Who brings what

Five jobs in every mobile test. Who does each one?

A working mobile test needs an environment, a script, a device, upkeep and someone to read the failure. Here is who handles each part with XCUITest, and who handles it with Pie.

The jobXCUITestPie
Set up the environment

XCUITestA Mac with Xcode. Xcode 27.2 needs macOS Tahoe 26.6 or later.

PieNothing to install. Upload an iOS simulator build or an Android APK.

Write the test

XCUITestYour developers, in Swift. They add accessibility identifiers in the app’s code, and review and finish anything Xcode records.

PiePie writes it. Tell Pie Chat what to check, and it explores the flow and drafts the test for your OK.

Supply the device

XCUITestSimulators on your Mac, devices you own, or Xcode Cloud, with 25 compute hours a month included in the $99-a-year developer program.

PieSimulators and emulators for iPhone, iPad and Android phones and tablets, on the OS version you pick.

Keep it passing after a UI change

XCUITestYour developers update the element queries. In Apple’s WWDC25 demo, a UI change failed a test and a person pasted in the suggested replacement.

PieNo locators to repair. Pie re-reads the screen on every run.

Make sense of a failure

XCUITestYour developers, from Xcode’s test report and its video of the run.

PiePie groups related findings into issues. Your team decides what counts as a bug.

Where they differ

Four reasons to take UI tests off your iOS developers.

  1. 01

    XCUITest lives in Xcode

    Tests are Swift in the Xcode project, so writing one takes a Mac and a developer who knows the app. Pie’s agents generate the tests, and anyone on your team can add one in plain English.

    Source
  2. 02

    Free with Xcode, paid in developer hours

    XCUITest comes with Xcode. The cost is the developers who write the tests and repair them. In one study, flaky tests alone took at least 2.5% of a team’s productive time. With Pie, those hours go back into your iOS app.

    Source
  3. 03

    Recording still ends in code

    Xcode can record your taps as Swift. Apple’s own session says to review the recorded code and add the waits and assertions yourself. With Pie, you describe the check in plain English and Pie drafts the test.

    Source
  4. 04

    iPhone and iPad, on the iOS version you pick

    Pie runs your iOS tests on iPhone and iPad simulators, on the iOS version you pick, on a schedule or on every new build. The same platform covers your Android and web apps.

Side by side

Swift tests or plain-English tests, row by row.

An XCUITest suite is Swift your developers write on a Mac. A Pie suite starts from a simulator build.

What you’re comparingPieXCUITestAdvantage
Cost to run it No scripts to write and no locators to break, so your team spends those hours on your product. Your developers’ hours to write and repair tests, plus the Macs or Xcode Cloud hours they run on. Pie
Getting started Upload an iOS simulator build. You get results in hours, not weeks. A Mac, Xcode, a UI test target in the project, then your first test in Swift. Pie
Writing a new test Agents generate tests by exploring your app. Anyone on your team can add one in plain English. A developer writes it in Swift, or records it in Xcode and then adds the waits and assertions. Pie
When the UI changes No locators to update. Pie re-reads the screen on every run. Element queries live in code. When one stops matching, a developer edits the test. Pie
Android and web apps Web, iOS and Android apps, on one platform. XCUITest is for apps on Apple platforms. Android and web need their own tools. Pie
Fixing the bug Pie groups related findings into issues, and can open a Fix PR in a repo you connect. Merging it is always your team’s call. Xcode’s report shows the failure with video. Triage and the fix are your team’s. Pie
License cost Custom pricing, tailored to your team’s requirements and testing volume. Contact Pie for a quote. Comes with Xcode. The Apple Developer Program is $99 a year. XCUITest
Apple Watch, Apple TV and Mac apps Pie’s Apple coverage is iPhone and iPad apps. Covers iOS, iPadOS, macOS, watchOS and tvOS, with hardware inputs such as the Digital Crown. XCUITest
The exception

When the app runs beyond iPhone and iPad

Your app runs on Apple Watch, Apple TV or the Mac

XCUITest covers watchOS, tvOS and macOS as well as iPhone and iPad, and can press hardware controls such as the Action button and the Digital Crown. Pie’s Apple coverage is iPhone and iPad.

Source
Who should pick which

Which fits your team, Pie or XCUITest?

Pick Pie to

  • Get iOS tests without a Mac or a Swift developer.
  • Test on iPhone and iPad, on the iOS version you pick.
  • Give your developers back the hours they spend on queries and flaky runs.
  • Run your suites on a schedule or on every new build, with nobody starting them.
  • Test your Android and web apps on the same platform.

Pick XCUITest if

  • You test Apple Watch, Apple TV or Mac apps.
Getting started

Switch from XCUITest one flow at a time

No big rewrite. Your XCUITest tests keep running until Pie covers the same flow.

  1. 1

    Upload a build

    Give Pie an iOS simulator build. If the app has a login, add a test login through a supported path.

  2. 2

    Let Pie explore

    Pie explores your app’s reachable flows and generates tests. You get results in hours, not weeks.

  3. 3

    Add your edge cases

    Type the cases only your team knows into Pie Chat in plain English. Pie explores each flow, drafts the test and runs it once you confirm.

  4. 4

    Retire tests as Pie covers them

    Compare Pie’s results with your XCUITest runs, and delete each UI test once Pie covers the flow.

FAQ

Did we miss a question?
Email us directly →

Is Pie an XCUITest alternative?

Yes. Pie replaces the UI tests your developers write and maintain with tests its agents generate by exploring your app.

Stay on XCUITest if you test Apple Watch, Apple TV or Mac apps.

Is XCUITest free?

XCUITest comes with Xcode, and the Apple Developer Program costs $99 a year. Xcode Cloud includes 25 compute hours a month with that membership.

The larger cost is your developers’ time to write the tests and keep them passing.

Pie’s agents write and run the tests, so those hours go back to your developers.

Do I need a Mac for XCUITest?
Yes. XCUITest runs from Xcode, and Xcode 27.2 requires a Mac on macOS Tahoe 26.6 or later. With Pie there is nothing to install. You upload an iOS simulator build and Pie runs it.
Can XCUITest test Android or web apps?
XCUITest is Apple’s framework for apps on Apple platforms. Pie tests your iOS app, and your Android and web apps on the same platform.
Doesn’t Xcode have AI now?

Xcode 27’s coding agents can boot a simulator, tap through the app and take screenshots to check a change they made. An XCUITest suite is still Swift your developers keep in the project.

Pie’s agents find the flows by exploring your app, and the tests stay in plain English.

Does Pie test on real devices?

Real devices are available on demand. Pie runs iOS apps on iOS simulators and Android apps on Android emulators, on the OS version you pick.

Our guide to real devices, emulators and simulators covers which bugs need which.

Does Pie test APIs and accessibility too?

Yes, and both are in beta. Pie runs whole API flows call by call, and checks each screen its tests reach for accessibility problems.

Your UI, API and accessibility testing sit in one place.

How do I move from XCUITest to Pie?
One flow at a time. Upload a build, let Pie generate tests, and type your edge cases into Pie Chat. Keep your XCUITest tests running until Pie covers the same flow, then retire them.
Who on my team runs Pie?

Whoever owns quality today, such as a QA lead or an engineer who owns releases. Pie does the exploring, writing and re-running, and the owner decides what matters and what counts as a bug.

Anyone on the team, including a product manager, can read a test or add one in plain English.

What does Pie cost?

Pie’s pricing is custom, tailored to your team’s requirements and testing volume.

You buy one product: agents explore your web, iOS and Android apps, write and run the tests, group related findings into issues and can open a Fix PR.

Book a demo, tell us what you ship and how often you release, and we’ll send you a quote.

Give your iOS developers their time back.

Book a demo and bring the iOS flow your suite keeps breaking on. We’ll show you Pie testing it from a simulator build.

Sources

  1. XCUIAutomation, Apple Developer Documentation. Apple’s UI automation framework, used with XCTest; tests are written in the Xcode project and cover iOS, iPadOS, macOS, watchOS and tvOS, including hardware inputs. On visionOS it covers iPhone and iPad apps only.developer.apple.com/documentation/xcuiautomation
  2. Xcode 27.2 and Xcode 27 release notes. Xcode 27.2 requires a Mac running macOS Tahoe 26.6 or later and includes the current OS SDKs; Xcode 27 coding agents can boot simulators, tap and take screenshots to verify UI.developer.apple.com/documentation/xcode-release-notes/xcode-27_2-release-notes · developer.apple.com/documentation/xcode-release-notes/xcode-27-release-notes
  3. Apple WWDC25 sessions 344 and 247 on UI automation. Session 344 says to add accessibility identifiers in app code, review recorded code and add waits and assertions. In session 247 a UI change fails a test and a person pastes in the replacement query Xcode suggests.developer.apple.com/videos/play/wwdc2025/344 · developer.apple.com/videos/play/wwdc2025/247
  4. Xcode Cloud and the Apple Developer Program. Membership is $99 a year and includes 25 Xcode Cloud compute hours a month; paid plans run from $49.99 a month for 100 hours.developer.apple.com/xcode-cloud · developer.apple.com/programs
  5. Cost of Flaky Tests in CI, ICST 2024 industry track. Five years of history, about 30 developers, one commercial project; “at least 2.5% of the productive developer time”. Not specific to XCUITest.conf.researchr.org/details/icst-2024/icst-2024-industry/1