Skip to content

Tests E2E de flujo wallet (onboarding -> deposit) #49

@Kalebtron1

Description

@Kalebtron1

Why this matters

Automated E2E coverage protects the wallet flow against regressions.

Problem

The onboarding and deposit flow does not have a repeatable E2E safety net.

Scope

  • Add or extend the E2E path for onboarding, wallet setup, and deposit.
  • Keep the test data deterministic and easy to reset.
  • Document any mocks or fixtures needed for the flow.

Implementation guidance

  • Use playwright.config.ts, playwright-fixture.ts, src/components/DepositModal.tsx, src/pages/Onboarding.tsx, and src/components/WalletSetupModal.tsx as the main touch points.
  • Add the test next to the current Playwright or fixture setup.
  • Keep the test focused on the most important user journey.

Out of scope

  • A full test suite for every app route.
  • Adding flaky dependencies that make the test hard to run.

Acceptance criteria

  • PR includes the automated test and the instructions to run it.
  • Reviewer can execute the documented command and see the expected pass result.
  • The PR description states which user journey is protected by the test.

Validation

  • Run the documented Playwright or E2E command locally.
  • Run npm run build if the test change touches app code.
  • Confirm the flow passes from onboarding through deposit.

PR requirements

  • Include Closes #49.
  • Document how to run the test locally.
  • Explain what user journey is covered and what is not.

Complexity

  • Medium (100 points)

Metadata

Metadata

Assignees

No one assigned

    Labels

    Stellar WaveIssues in the Stellar wave programcomplexity:medium150 points - standard feature touching multiple areastestingTests, CI and E2EwalletWallet connection and signing flows

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions