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


skill-level: medior status: done

Task: Create Settings and Misc Screen Flows

End Goal

3 per-screen Maestro flows for settings and miscellaneous screens with parameterized invocation.

Currently

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

Should

  • screens/settings/settings.yaml - App settings
  • screens/misc/whats_new.yaml - What's New changelog
  • screens/misc/oops.yaml - Error screen

Constraints

  • [x] Must use auto-login via screenshot mode (except oops which may not require auth)
  • [x] Must use utility flows for login
  • [x] Oops screen may require special triggering (simulated error state)

Acceptance Criteria

  • [x] settings.yaml captures settings screen with profile, theme toggle, logout
  • [x] whats_new.yaml navigates to What's New and captures changelog
  • [x] oops.yaml captures error screen (may need mock error or offline state)
  • [x] All flows tagged with screenshot and appropriate feature tag

Implementation Checklist

  • [x] 9.1 Create screens/settings/ and screens/misc/ directories
  • [x] 9.2 Create settings.yaml - Navigate via settings_button from home, capture
  • [x] 9.3 Create whats_new.yaml - Navigate via inbox_button then whats_new_button, capture
  • [x] 9.4 Create oops.yaml - Trigger or simulate error state, capture (may use special build flag or network simulation)
  • [x] 9.5 Validate all flows with YAML syntax check (maestro test --check-only flag not available in current version)

Notes

  • Settings accessed via settings_button from home screen
  • What's New accessed via inbox_button then whats_new_button
  • Oops screen may require --dart-define=simulateError=true or similar

Reacties

Nog geen reacties