Skip to content

Add comprehensive Maestro E2E coverage for wallet connection error paths #101

Description

@Lakes41
  • Difficulty: Advanced
  • Type: test
  • Background: The existing .maestro/ suite (per README) covers onboarding, manual entry, guild navigation, access checks, and app reset, but not wallet-connection failure modes (relevant once Issue Add push notification registration and preferences #21 lands).
  • Problem: Wallet connection is a high-risk, multi-step external-dependency flow (deep linking out to wallet apps and back) prone to regressions that unit tests can't catch.
  • Expected outcome: New Maestro flows covering: user cancels connection in the wallet app, connection times out, connection succeeds but returns an unsupported chain, and reconnect-after-disconnect.
  • Suggested implementation: Add new .maestro/*.yaml flow files following existing naming conventions (e.g., 06-wallet-connect-cancel.yaml); document any required mocking/stubbing of the wallet app interaction for deterministic local runs.
  • Acceptance criteria: New flows are documented in .maestro/README.md; each flow asserts a specific, distinct end state; flows run successfully against a local development build per the README's E2E instructions.
  • Likely affected files/directories: .maestro/
  • Labels: test, GrantFox OSS, Maybe Rewarded, Official Campaign | FWC26

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

GrantFox OSSGrantFox Open Source Sponsorship program tagMaybe RewardedIssue may qualify for a reward upon successful completion per campaign rulesOfficial Campaign | FWC26Official FWC26 campaign issue — eligible for campaign scoring and rewardstestTest coverage additions, test fixes, or test infrastructure work

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions