การทดสอบส่วนติดต่อผู้ใช้ด้วย XCUITest

UI tests drive your app like a real person: they tap, type, and swipe, then check the screen reacted correctly. 📱

UI tests live in their own UI Testing target. Xcode adds it when you create the project or from the test navigator later.

Every UI test starts by launching a fresh app instance with XCUIApplication. This gives you a clean state to work from.

You reach controls through queries like buttons, staticTexts, and textFields. Each query finds elements by their kind on screen.

Call tap on an element to simulate a finger press. The app responds exactly as it would for a real user.

Tap a field first, then send keystrokes with typeText. This is how you fill in forms during a test.

Give views a stable accessibilityIdentifier so tests find them even when the visible label changes or is localized.

Check the result with exists. It returns true when the element is on screen, confirming your action worked.

If content loads after a delay, use waitForExistence with a timeout. The test pauses until the element shows up. ⏳

New to queries? Use Xcode's record button. It writes code as you tap, giving you a starting point to clean up.

UI tests are slower than unit tests. Cover key flows like sign-in and checkout, and leave the rest to faster unit tests.

What is the most reliable way for a UI test to find a control?

You drove the app with XCUITest: launch it, query controls, tap and type, then assert with exists. Real user flows, automated. 🎉