Skip to content

Add a cross-browser end-to-end matrix with Chromium, Firefox, and WebKit #850

Closed

Description

@thegreatfeez

Testing & QA

Summary

Run the end-to-end suite across Chromium, Firefox, and WebKit so browser-specific breakage is caught.

Background

E2E currently runs in one browser. Wallet and rendering behavior can differ across browsers, so a single-browser run can miss real issues.

What Needs to Be Done

  1. Configure the E2E runner for all three engines.
  2. Run the core flows in each engine.
  3. Fix browser-specific failures.
  4. Report results per engine.
  5. Keep runtime reasonable with parallelism.

Acceptance Criteria

  • E2E runs in all three engines.
  • Core flows are covered per engine.
  • Results are reported per engine.
  • The suite passes within a reasonable time.

Files to Look At

  • frontend/e2e/ — E2E tests
  • frontend/playwright config — engines
  • .github/workflows/ — CI

Difficulty: Medium

Activity

  1. deslawson commented on Oct 18, 2026

    @deslawson

    @deslawson has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    I'd love to work on this

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @deslawson to this issue.

  2. DeeMyth commented on Oct 18, 2026

    @DeeMyth

    @DeeMyth has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    Good day maintainer
    I have gone through the requirement of this issue and I can definitely solve it
    Please assign it to me

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @DeeMyth to this issue.

  3. pchieneye commented on Oct 18, 2026

    @pchieneye

    @pchieneye has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    Hi, I’ve carefully reviewed the issue and understand the expected outcome. I have the relevant experience to implement the solution and would be glad to take it on. Please assign it to me.

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @pchieneye to this issue.

  4. GazzyLee commented on Oct 18, 2026

    @GazzyLee

    @GazzyLee has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    I’d like to take this issue. I’ve reviewed the requirements and would be happy to work on the implementation and provide a tested solution.

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @GazzyLee to this issue.

  5. YoungBoss04 commented on Oct 18, 2026

    @YoungBoss04

    @YoungBoss04 has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    Having gone over the task and its requirements, I'm sure I can build a solution that matches the intended design and acceptance criteria.

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @YoungBoss04 to this issue.

  6. Allen-altron commented on Oct 18, 2026

    @Allen-altron

    @Allen-altron has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    . Hello, I’m interested in working on this issue. I have relevant experience and can get started as soon as possible

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @Allen-altron to this issue.

  7. Fi-zzy commented on Oct 18, 2026

    @Fi-zzy

    @Fi-zzy has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    Hello Maintainer, this looks like a task I can handle comfortably. I’d appreciate the opportunity to work on it.

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @Fi-zzy to this issue.

  8. stephanieefeakpokrire-droid commented on Oct 18, 2026

    @stephanieefeakpokrire-droid
    Contributor

    @stephanieefeakpokrire-droid has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    maintainer assign

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @stephanieefeakpokrire-droid to this issue.

  9. drips-wave commented on Oct 18, 2026

    @drips-wave

    Congratulations, @stephanieefeakpokrire-droid! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.

    🧑‍💻 @stephanieefeakpokrire-droid: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

    Warning

    When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

    🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

    🌊 Happy Wave 🌊

  10. stephanieefeakpokrire-droid commented on Oct 19, 2026

    @stephanieefeakpokrire-droid
    Contributor

    Resolved via PR #920

  11. drips-wave commented on Oct 19, 2026

    @drips-wave

    This issue has been completed by @stephanieefeakpokrire-droid as part of the Stellar Wave Program's 10th Wave 🥳

    😎 @stephanieefeakpokrire-droid: You earned 200 Points for completing this issue! Once the Wave's rewards are finalized, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

    🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.

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

Metadata

Metadata

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions