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:
20
.maestro/flows/09-notification-deeplink.yaml
Normal file
20
.maestro/flows/09-notification-deeplink.yaml
Normal file
@@ -0,0 +1,20 @@
|
||||
# Golden path: cold-launch via deeplink honeydue://task/<id> resolves to task detail.
|
||||
# Requires a valid task id for the logged-in test account. CI can seed a fixture
|
||||
# id via environment/script and interpolate; here we use "test-task-id" as a
|
||||
# placeholder that a seed-step can replace.
|
||||
appId: com.tt.honeyDue
|
||||
name: Notification deeplink opens task
|
||||
tags:
|
||||
- regression
|
||||
- deeplink
|
||||
env:
|
||||
TASK_ID: "test-task-id"
|
||||
---
|
||||
- runFlow: 01-login.yaml
|
||||
- openLink: "honeydue://task/${TASK_ID}"
|
||||
- extendedWaitUntil:
|
||||
visible:
|
||||
id: "TaskDetail.View"
|
||||
timeout: 15000
|
||||
- assertVisible:
|
||||
id: "TaskDetail.CompleteButton"
|
||||
Reference in New Issue
Block a user