Skip to content

chore: Port playwright e2e tests to Elixir client - #159

Open
ftes wants to merge 8 commits into
Valian:mainfrom
ftes:upstream-pr
Open

ftes wants to merge 8 commits into
Valian:mainfrom
ftes:upstream-pr

Conversation

@ftes

@ftes ftes commented Nov 19, 2026 •

Copy link
Copy Markdown

tl;dr I'm preparing the next playwright_ex major version and ported your test suite to validate the RC.

Please feel free to close this PR without comment if you're not interested 🙂.

What changed?

  • Port the e2e tests from official Javascript to unofficial Elixir client, using the 1.65.0-rc.2 of playwright_ex

Why make these changes?

  • For you: Maintain a larger part of your codebase in Elixir.
  • For me: I'm validating the new RC by porting existing open source test suites to see if the playwright client is feature complete and performant.

Further notes

  • Timing: Currently, playwright_ex 1.65 is in RC phase. I chose to open the PR now anyway in case you want to have a look and possibly raise any comments.
  • I let Claude code do most of the port, and did some cursory review myself. If you're generally interested, I'm more than happy to do a more in-depth review myself up front.

ftes added 8 commits November 19, 2026 07:55
The browser tests run as ExUnit tests in e2e_pw/ (MIX_ENV=e2e mix test), against the server of test/e2e/server.exs started in the same VM. The suite lives outside test/ so that a plain mix test, including on Elixir 1.15, does not load it. The e2e CI job runs on Elixir 1.19, as playwright_ex needs 1.18 or later.
Delete the Playwright Test specs, config and helpers, and the @playwright/test dependency and npm scripts. mix e2e.test builds the assets and runs the ExUnit suite; docs updated.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant