Athena — roomy-mobile/archive/changes/2026-01-05-add-per-screen-maestro-flows/tasks/008-create-payments-flows.md


skill-level: medior status: done

Task: Create Payments Screen Flows

End Goal

3 per-screen Maestro flows for payments screens with parameterized invocation.

Currently

  • Payments screens captured as part of monolithic screenshot-main-flow.yaml
  • No per-screen invocation capability

Should

  • screens/payments/payments.yaml - Payments overview
  • screens/payments/manage_payment.yaml - Payment detail/create (parameterized by PAYMENT_ID, MODE)
  • screens/payments/all_payments.yaml - All payments list

Constraints

  • [x] Must use auto-login via screenshot mode
  • [x] Must use utility flows for login and tab navigation
  • [x] Payment IDs must match seed data

Acceptance Criteria

  • [x] payments.yaml captures payments overview with recent payments
  • [x] manage_payment.yaml accepts PAYMENT_ID and MODE (create|edit) parameters
  • [x] manage_payment.yaml defaults to create mode when no PAYMENT_ID provided
  • [x] all_payments.yaml captures full payments list
  • [x] All flows tagged with screenshot and payments

Implementation Checklist

  • [x] 8.1 Create screens/payments/ directory
  • [x] 8.2 Create payments.yaml - Navigate to payments tab, capture overview
  • [x] 8.3 Create manage_payment.yaml - Navigate to payments tab, tap create or specific payment, capture
  • [x] 8.4 Create all_payments.yaml - Navigate to payments tab, tap "See All", capture full list
  • [x] 8.5 Validate all flows with maestro test --check-only

Notes

  • Available PAYMENT_IDs from seed data: payment-utilities, payment-groceries, payment-internet, payment-rent, payment-dinner, payment-cleaning, payment-dec-utilities, payment-dec-groceries
  • Semantic identifiers: create_payment_button, see_all_payments_button
  • Keyboard may need hiding for create payment screen: hideKeyboard

Reacties

Nog geen reacties