Hacker News Reader

Comment by no_wizard | Hacker News Reader

I love playwright, especially since you get three browser engines (Webkit, Chromium and Gecko) under one unified API.

I am little disappointed they don’t have a testing library built on top of it, so I’m constantly either trying to re-invent the wheel or I end up using libraries I don’t like.

Sam issue I had with puppeteer. I think first party testing integration would be such a huge win with this.

I otherwise have nothing but awesome things to say about the playwright project, it really is such a great improvement over selenium and I think it’s now got a more ergonomic API than puppeteer

View on HN

Thanks for the feedback! I'm on the Playwright team.

We are building playwright-runner[1] to solve this problem. We are dogfooding the project internally, and a few weeks away from opening it up to early adopters.

[1] https://github.com/microsoft/playwright-runner

It does not support Drag & drop, is it right?

I think the support is missing in Playwright.

Are there any plans about this?

You should try out WebTestRunner: https://www.npmjs.com/package/@web/test-runner

It's a very, _very_ fast test runner that supports Playwright, Puppeteer, Selenium, BrowserStack and Sauce launchers.

We're using it for the new versions of lit-html and LitElement and the speed of re-running only effected tests on all three engines is amazing - it's nearly instant.

Abstracting away the browser launcher from just Playwright or Puppeteer means that your test infra still runs against IE11 or specific versions of, say, Safari if you need to.

I quite enjoying using testing-library's playwright library, see: https://www.npmjs.com/package/playwright-testing-library and www.testing-library.com

I didn’t see this listed on the official testing library page. Is it maintained by them?

No, but it’s a fork of the puppeteer version which is part of testing library. As playwright is quite similar to the puppeteer library with small changes, it’s quite well maintained imho. Enjoying using it

I've had a brief but successful experience with QAWolf (https://www.qawolf.com/), which is built on Playwright (last I checked)

Beauty about Playwright (or puppeteer) is API itself is much complete & good devx to start using for browser testing. All you need is jest kind of wrapper.

Just curious, why do you prefer a first-party testing integration; Is it to save on harness maintenance or do you not like any of the stand-alone testing libraries, or something else? I guess I don't quite follow what you mean by "re-invent the wheel".

have found using the jest preset pretty good, a little awkward getting my code injected in some cases though

same, using mocha and getting by, but would be amazing if there was a straightforward test layer built for it

Reply on news.ycombinator.com