Maestro: 10 golden-path flows for critical user journeys
Cross-platform YAML flows (iOS + Android share the AccessibilityIds test-tag namespace). Covers login, register, residence/task CRUD, completion, join, document upload, theme, deeplink, widget. Run: maestro test .maestro/flows/ Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
29
.maestro/flows/10-widget-complete.yaml
Normal file
29
.maestro/flows/10-widget-complete.yaml
Normal file
@@ -0,0 +1,29 @@
|
||||
# Android-only: simulates a home-screen widget "complete task" tap by firing
|
||||
# the widget's deeplink URI directly. Maestro does not render the Android home
|
||||
# screen / App Widget host, so we exercise the underlying intent that the
|
||||
# widget's PendingIntent targets (honeydue://task/<id>/complete). On iOS this
|
||||
# flow is a no-op — iOS does not ship an equivalent widget surface yet.
|
||||
appId: com.tt.honeyDue
|
||||
name: Widget tap completes task (Android)
|
||||
tags:
|
||||
- android-only
|
||||
- widget
|
||||
env:
|
||||
TASK_ID: "test-task-id"
|
||||
---
|
||||
- runFlow: 01-login.yaml
|
||||
- openLink: "honeydue://task/${TASK_ID}/complete"
|
||||
- extendedWaitUntil:
|
||||
visible:
|
||||
id: "TaskCompletion.SubmitButton"
|
||||
timeout: 15000
|
||||
- tapOn:
|
||||
id: "TaskCompletion.NotesField"
|
||||
- inputText: "Completed via widget simulation."
|
||||
- hideKeyboard
|
||||
- tapOn:
|
||||
id: "TaskCompletion.SubmitButton"
|
||||
- extendedWaitUntil:
|
||||
visible:
|
||||
id: "Task.List"
|
||||
timeout: 15000
|
||||
Reference in New Issue
Block a user