fteschke
Playwright_ex - Playwright client for browser automation
Announcing: playwright_ex
A simple Elixir client for the Playwright node.js server.
Automate browsers like Chromium, Firefox, Safari and Edge.
Experimental.
Extracted from phoenix_test_playwright, so the foundation is proven to work.
What I’m less sure about is the API. Happy to hear your thoughts!
References:
- Code extracted from phoenix_test_playwright.
- Inspired by playwright-elixir.
- Official playwright node.js client docs.
Trending in Announcing
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Bringing learning, work and compliance together since 1987.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #performance
- #security
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Practical resources that improve the lives of professional developers.
Bringing learning, work and compliance together since 1987.
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Most Liked
michallepicki
Thank you!!! I worked a bit in the past on maintaining a e2e web app integration test suite, testing on both Chrome and Firefox, and one of the most annoying things in the legacy WebDriver protocol was behavior differences when running the tests on different browsers. Or tests breaking after a browser update. And the new-er W3C WebDriver protocol didn’t solve this problem (and maybe actually even introduced more problems). I think the biggest contribution of Playwright is that Microsoft is putting in the leg work to make it work consistently across all the browsers (and that it works with their new versions). Sure, it’s not exactly 100% Firefox or Safari (they maintain forks) but I think it should be good enough to test most important functionality across all browsers.
michallepicki
Related, the W3C people have been working on another huge specification in WebDriver BiDi, we’ll see how well supported that one will be… And fresh off the press, with a 1.0 version already released (in Gleam style, where they intentionally discourage library authors from publishing 0.x versions so that APIs are well thought out from the start and libraries are not stuck in that chaotic pre-1.0 world) there’s now a Gleam library called butterbee for working with WebDriver BiDi.
That probably goes without saying, but I think all of the hound, wallaby and now also butterbee could be an inspiration here. Personally I like your approach of having extracted the lower-level bits from phoenix_test_playwright, I think it would be best to focus on the protocol itself and a “client library” alone, and leave the higher level testing helpers and Ecto/Phoenix integration conveniences to other libraries building on top of it. For Wallaby, I know @aaronrenner extracted web_driver_client having that approach in mind
Last Post!
fteschke
Some quick tinkering: Might be worth looking into a WebDriver BiDi/Butterbee driver for PhoenixTest.
https://github.com/germsvel/phoenix_test/pull/278