AI Prompts for Planning Appium Mobile Automation

Sample input: add item to cart (Android + iOS)

Fictional example written for this guide.

App: ShopLite, React Native
Platforms: Android 12–14, iOS 16–17
Stack: Java + TestNG + Appium 2 (UiAutomator2 / XCUITest)
Manual steps:
1. Launch app, allow notifications
2. Search "running shoes"
3. Open first result
4. Select size 42
5. Tap "Add to cart"
6. Verify cart badge shows 1

Sample AI output (illustrative, untested skeleton)

Sample output only — this shows the shape of a good answer. It has not been run, executed, or verified against a real system.

Page Objects: HomeScreen, SearchResultsScreen, ProductScreen, CartBadge (component)

ProductScreen
- sizeOption(size)   → accessibilityId "size-<n>"   (ask devs to add testID)
- addToCartButton    → accessibilityId "add-to-cart"
- methods: selectSize(int), addToCart()

Waits
- After search: wait until first result is visible (max 10s)
- After addToCart: wait until cart badge text equals "1"

Android vs iOS
- Notification prompt: Android 13+ system dialog vs iOS alert → handle via capability autoGrantPermissions (Android) / autoAcceptAlerts (iOS) or a dedicated handler

// UNTESTED SKELETON
public class ProductScreen {
  private final AppiumDriver driver;
  private final WebDriverWait wait;
  public ProductScreen(AppiumDriver driver) {
    this.driver = driver;
    this.wait = new WebDriverWait(driver, Duration.ofSeconds(10));
  }
  public void selectSize(int size) {
    wait.until(ExpectedConditions.elementToBeClickable(
      AppiumBy.accessibilityId("size-" + size))).click();
  }
  public void addToCart() {
    driver.findElement(AppiumBy.accessibilityId("add-to-cart")).click();
  }
}

Locator strategy, best to worst

Page Object Model suggestions

• One class per screen; shared widgets (tab bar, toasts) as components.
• Methods describe user intent (addToCart) — never expose raw locators to tests.
• Keep assertions in tests, not in page objects, except for “screen is loaded” checks.
• Hold platform-specific locators in one place so tests stay platform-agnostic.

Waits and validation tips

• Replace Thread.sleep with explicit waits on visibility, clickability, or text.
• Keep implicit wait at 0 when using explicit waits to avoid compounded timeouts.
• Reset app state between tests (noReset / fullReset) deliberately, not by default.
• Capture screenshot + page source on failure; they make flaky failures diagnosable.
• Validate on at least one real device per platform before trusting emulator results.