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


skill-level: medior status: done

Task: Create Shopping Screen Flows

End Goal

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

Currently

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

Should

  • screens/shopping/shopping_lists.yaml - Shopping lists overview
  • screens/shopping/shopping_list.yaml - Single list detail (parameterized by LIST_INDEX)
  • screens/shopping/edit_shopping_list.yaml - Edit list (parameterized by LIST_INDEX)

Constraints

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

Acceptance Criteria

  • [x] shopping_lists.yaml captures all shopping lists
  • [x] shopping_list.yaml accepts LIST_INDEX parameter, defaults to 0
  • [x] edit_shopping_list.yaml accepts LIST_INDEX parameter, navigates to edit mode
  • [x] All flows tagged with screenshot and shopping

Implementation Checklist

  • [x] 7.1 Create screens/shopping/ directory
  • [x] 7.2 Create shopping_lists.yaml - Navigate to shopping tab, capture lists overview
  • [x] 7.3 Create shopping_list.yaml - Navigate to shopping tab, tap list by index/ID, capture detail
  • [x] 7.4 Create edit_shopping_list.yaml - Navigate to list detail, tap edit button, capture edit screen
  • [x] 7.5 Validate all flows with YAML syntax validation

Notes

  • Available LIST_IDs from seed data: list-groceries, list-household, list-party, list-pet, list-office
  • Semantic identifier pattern for lists: shopping_list_{index} (0-based)
  • Edit button identifier: edit_shopping_list_button

Reacties

Nog geen reacties