Mobile Testing Fundamentals

// ══════════════════════════════════════════════════════════════
// MOBILE TESTING PYRAMID
// ══════════════════════════════════════════════════════════════

// Bottom (70%): Unit Tests (Jest, JUnit, XCTest)
//   - Business logic, utils, API calls
//   - Runs in milliseconds, no device required

// Middle (20%): Component/Integration Tests (Detox, Espresso, XCUITest)
//   - Individual screens and user flows
//   - Requires emulator, fast

// Top (10%): E2E Tests (Appium, Detox)
//   - Critical user journeys on real devices
//   - Slow, expensive, must be selective

// ══════════════════════════════════════════════════════════════
// WHICH TESTS TO AUTOMATE WITH APPIUM (E2E layer)
// ══════════════════════════════════════════════════════════════

const e2eTestPriority = {
    // MUST automate (critical paths):
    critical: [
        "User registration and login",
        "Core purchase/checkout flow",
        "Payment processing",
        "Account settings changes",
        "Logout and session expiry",
    ],
    
    // SHOULD automate (high-frequency):
    high: [
        "Product search and filter",
        "Cart add/remove/update",
        "Push notification tapping",
        "Deep link handling",
        "Offline mode data sync after reconnect",
    ],
    
    // MANUAL ONLY (too expensive to automate):
    manual: [
        "New feature exploratory testing",
        "Accessibility testing (VoiceOver, TalkBack)",
        "Complex gestures and animations",
        "Battery drain measurement",
        "AR/camera features",
    ]
};