QA Test Plan

Comprehensive QA coverage for the SIPP iOS app, spanning the consumer experience (map search → ordering → loyalty) and the shop experience (café management → live order queue). Use this document while planning manual runs, writing automated UI tests, or preparing release sign‑offs.

1. Test Environment & Tooling

• Hardware & OS: iPhone 13–15 simulators on iOS 17.x plus at least one physical device to validate camera/QR scanning and StoreKit flows.
• Build configuration
• Copy Config.example.xcconfig → Config.xcconfig and Config.production.example.xcconfig → Config.production.xcconfig.
• Populate Supabase URLs/keys, App Store subscription IDs, and feature flags (keep real keys out of git).
• Build with xcodebuild -scheme sipp -destination 'platform=iOS Simulator,name=iPhone 15' build. Run tests via xcodebuild test ....
• Test accounts & data
• Consumer: at least one account with no orders, one with an active membership (credit balance), and one lapsed account.
• Shop: an owner account with ≥1 café (for order queue/staff flows) and a staff-only account.
• Preload Products.storekit for StoreKit testing; stage menu/catalog data for at least two cafés.
• Keep seeded orders/carts in Supabase so QA can perform cross-role tests end-to-end.

2. Consumer Journey Scenarios

2.1 Authentication & Role Selection (Features/Authentication)

• Sign in/out, sign up, and password reset for both Consumer and Shop roles.
• Validate inline error messaging (bad email, weak password, server error).
• Ensure the segmented control switches roles without losing typed credentials.
• Confirm AppState restores sessions on cold launch and clears data on logout (cart, profile, tokens).

2.2 Home Map, Search & Quick Actions (Features/Home)

• Location permission prompts, map centering, and viewport searches (search text vs “Near Me” context chip).
• Cafe list density: verify annotations, selection glow, and detail sheet presentation.
• Quick actions: Cart (ensure not shown when empty), Near Me, and Scan (launches QR scanner sheet).
• Offline handling: toggle airplane mode and confirm graceful errors/ retry affordances.

2.3 Café Detail & Ordering Entry (Features/CafeDetail, Features/Ordering)

• Open from map and ensure metadata (status, distance, address, contact actions) matches backend data.
• “Order Now” sheet loads menu sections, handles skeleton state, and respects café open/closed status.
• Role gating: Consumer-only features blocked when logged in as shop.

2.4 Menu Browsing & Customization (CustomizationView, MenuViewModel)

• Menu sections load with pagination; pull-to-refresh reloads data.
• Search within a menu; ensure results reset when query cleared.
• Customize items: variant selection, modifiers, quantity limits (1…12), notes persistence.
• Validation: mandatory option groups enforce selection, price deltas apply correctly.

2.5 Cart & Checkout (Shared/Stores/CartStore, CartView, CheckoutView)

• Add/remove items across sessions (cart persistence via CartStore/UserDefaults).
• Update quantities, tips, promo codes, pickup notes; verify totals and taxes update.
• Sync errors: simulate network failures to confirm error banners.
• Checkout sheet: ensure syncForCheckout() completes before enabling payment (mock flow).
• Empty cart states, “clear cart” confirmation, and multi-café guardrails (cart resets on different café).

2.6 Orders & Activity (Features/Activity, Features/Orders, Visits)

• Activity tab badges update on new visits/orders (Notification visitRedeemed focus change).
• Orders list: pagination, empty state, skeleton, and currency formatting.
• Visit history & redemption counts; verify QR scanning increments visits.

2.7 QR Scanner & Loyalty (Features/QRScanner)

• Camera permission request, torch toggle, and error states for invalid QR codes.
• Redeeming flows: after a successful scan, ensure alert, badge increment, and activity tab switch occur.

2.8 Subscription & Billing (Features/Subscription, Products.storekit)

• Launch the subscription screen and exercise both purchase paths:
• Subscribe with Apple (StoreKit): buy, cancel, and restore purchases in sandbox; ensure AppState.subscriptionStatus transitions correctly (active → expired → none) and that visit balances update after receipt sync.
• Pay with Card (Stripe Checkout): tap the pink CTA, complete a Stripe test payment, and confirm the app returns to the success URL with refreshed visits. Cancel mid-flow to ensure no charge but the CTA remains enabled.
• Tap Manage billing to open the Stripe Billing Portal; make a change (plan switch, cancellation) and verify the app reflects it once you dismiss the sheet.
• Confirm the Subscription screen always shows the latest visit balance after either flow (trigger a manual refresh if needed).

2.9 Profile & Settings (Features/Profile)

• Update display name, theme, notification preferences, and logout.
• Theme switching: verify tint updates globally (map, buttons, segmented control).
• Account deletion / reset flows if available.

2.10 Resilience & Edge Cases

• Kill & relaunch with active tasks (cart sync, map region fetch) to ensure no crashes.
• Background/foreground transitions: scenePhase handlers resume map refresh & location watchers.
• Accessibility: VoiceOver labels on quick actions, main buttons, and input fields.

3. Shop Journey Scenarios

3.1 Role Switching & Access Control

• From profile tab, switch between Consumer ↔ Shop roles; ensure tab layout updates (Shop tab appears only for activeRole == .shop).
• Confirm consumer-only flows (ordering, cart) remain accessible when role is shop, but shop-specific data (order queue) hides otherwise.

3.2 Café Onboarding & Management (Features/Shop/ShopOnboardingView)

• Create café: validate required fields, geolocation inputs, template picker defaults, active toggle.
• Edit café details and confirm data persistence/back-end update.
• Staff management sheet: invite/remove staff, handle error states (duplicate email, network).
• Quick links disabled state when no shopSession.

3.3 Dashboard & Analytics (Features/Shop/Dashboard)

• Load metrics cards (sales, visits, top products) with skeleton state.
• Date range filters (if present) update charts; validate empty data handling.

3.4 Live Order Queue (Features/Shop/OrderQueue)

• Pull queue: new, in-progress, completed sections; empty state.
• Actions per order: accept, mark ready, complete/cancel—ensure state transitions propagate to backend.
• Background refresh timers and manual pull-to-refresh.
• Push/local notifications (if implemented) open specific orders.

3.5 Order Detail & QR Display

• Inspect individual order details, verify item breakdown, customer notes, totals.
• QR display for pickup scanning: renders correct code, handles brightness lock.

3.6 Shop Settings (Features/Shop/Settings)

• Update café availability, messaging, or theme; confirm persistence.
• Validate restricted actions for staff (vs owners) if differentiated in UI.

3.7 Cross-Role End-to-End

• Consumer places order → verify appearance in shop queue → shop completes order → consumer order history updates.
• Subscription perks or loyalty rewards triggered by shop actions (visit redemption).

4. Cross-Cutting Regression Areas

• Networking & Error Handling: simulate API failures (Supabase down, 401 responses) to ensure alerts bubble up with actionable text.
• Persistence: CartStore state, AppState session, preferred role selection, theme, and cached cafes survive relaunch.
• Offline/Low Connectivity: caching, background tasks cancellation, user feedback (retry buttons) across Home, Ordering, Shop queue.
• Localization & Formatting: currently English-only, but verify dynamic type sizing and currency formatting for different locales.
• Accessibility: VoiceOver order, focus indicators, contrast on glass backgrounds, button hit targets (44pt).
• Performance: Map panning, large menus, and order queue updates stay below 16ms frame budget; watch memory usage when loading multiple sheets.
• Security: Config files exclude secrets; ensure logout clears cart/session; confirm Keychain tokens wiped via AppState.clearSession.

5. Automation Candidates

• Unit: continue covering CartStore, services, and view models under sippTests.
• UI: add XCUITests for login, home map smoke, cart sheet presentation (recent regression), ordering flow, and basic shop queue action.
• Snapshot tests for key screens (Home, Ordering, Shop Dashboard) to guard against UI regressions.

6. Release Checklist

1. Run xcodebuild test -scheme sipp -destination 'platform=iOS Simulator,name=iPhone 15'.
2. Execute manual smoke on latest production configuration (consumer + shop).
3. Validate StoreKit purchases in sandbox & revoke to ensure grace-period logic works.
4. Confirm Supabase migrations (if any) deployed and backward compatible.
5. Capture before/after screenshots for any UI-affecting PR (per repository guidelines).
6. Ensure Config*.xcconfig with real keys remain untracked; verify build settings reference base configs correctly.
7. Update QA doc when new features ship (e.g., loyalty perks, new shop modules).

7. Submitting QA Tickets

When filing an issue (GitHub, Linear, Jira, etc.), include:

1. Title — concise summary, e.g., Subscription: Pay with Card hangs on loading.
2. Environment — device model + iOS version, build number/TestFlight version, Supabase project (staging/prod), and whether you used a simulator or physical device.
3. Preconditions — account role (consumer/shop), membership state (active, expired), data fixtures (cart contents, café), feature flags.
4. Steps to Reproduce — numbered list referencing screen names from this doc (Home → Profile → Subscription, etc.), including form inputs and waits.
5. Expected vs Actual — bullet what should happen versus what did.
6. Artifacts — attach:
7. Screenshots/video (full screen).
8. Console logs or device logs (copy/paste or attach .log).
9. Edge-function output (curl/HTTP response) when available.
10. Severity/Priority suggestion — P1 (blocks checkout), P3 (UI polish).

For regressions, link to the last known good build/PR. For backend issues, paste the exact error surfaced in the UI (e.g., “Set STRIPE_PRICE_STANDARD”) so engineers know which env var or service failed.

Use this plan as the living reference for regression passes. When new features merge, append scenarios to the relevant consumer or shop sections and link to tracking tickets so QA can prioritize by release scope. The directories referenced above map one-to-one with on-device screens, making it easy to discover the underlying implementation if additional instrumentation or debug logging is needed.