Live data from Hacker News

Playwright: Automate Chromium, WebKit and Firefox

github.com

61–70 of 149 posts

Re: Playwright: Automate Chromium, WebKit and Firefox

#61
post #18

What do people thing of playwright vs cypress? I've been considering using playwright instead as it supports more browsers and I feel like it's easier to do production monitoring (by putting it in a aws lambda or using checkly) - Cypress: https://www.cypress.io - Playwright aws lambda: https://github.com/PauloGoncalvesBH/running-playwright-on-aw... - Checkly: https://www.checklyhq.com

We see a strong adoption of Playwright. It’s the default we recommend to users now. We also support Puppeteer, but its development is lagging. Having said that, I would love to support Cypress if I had infinite time and focus. Side note: Selenium is not on the menu, even with its large install base. We are aiming for where the puck is going and it’s going to Playwright. Full disclaimer: I’m CTO at Checkly.

Why was Selenium off the menu?

Re: Playwright: Automate Chromium, WebKit and Firefox

#63

Is there an open source web testing tool which also integrates a dashboard, keeps track of test runs, creates reports, something that I can just install on a vm and run to test a web app?

Give Lighthouse CI a shot.

https://github.com/GoogleChrome/lighthouse-ci

Re: Playwright: Automate Chromium, WebKit and Firefox

#65

Off-topic, but our freemium website is under attack by headless browsers. The freemium service provides access to compute-heavy machine learning models running on GPUs. Hackers blast 50-100 requests in the same second, which clog the servers and block legitimate users. We reported IPs to AWS and use Cloudflare "Super Bot Fight Mode" to thwart attacks, but the hackers still break through. We don't require accounts, bu…

what's your site? would like to play with it

Re: Playwright: Automate Chromium, WebKit and Firefox

#66
post #18

What do people thing of playwright vs cypress? I've been considering using playwright instead as it supports more browsers and I feel like it's easier to do production monitoring (by putting it in a aws lambda or using checkly) - Cypress: https://www.cypress.io - Playwright aws lambda: https://github.com/PauloGoncalvesBH/running-playwright-on-aw... - Checkly: https://www.checklyhq.com

We see a strong adoption of Playwright. It’s the default we recommend to users now. We also support Puppeteer, but its development is lagging. Having said that, I would love to support Cypress if I had infinite time and focus. Side note: Selenium is not on the menu, even with its large install base. We are aiming for where the puck is going and it’s going to Playwright. Full disclaimer: I’m CTO at Checkly.

I saw puppeteer is actively developed, wonder where the 'lagging' implies.

doesn't playwright use puppeteer for chromium-based browsers(even edge-based), I thought it's just a wrapper for puppeteer with extra support for firefox.

Re: Playwright: Automate Chromium, WebKit and Firefox

#67
post #55
post #53

Earlier quoted context omitted.

I wonder what the story is there. Why wouldn't MS just have him continue to work on Puppeteer? They're both open source, so there's not much point in "owning" their own clone of it.

From what I know puppeter works only with chromium, this could be deal breaker for microsoft

Puppeteer has experimental Firefox support.

https://pptr.dev/#faq:~:text=What%20is%20the%20status%20of%2...

Re: Playwright: Automate Chromium, WebKit and Firefox

#68

Earlier quoted context omitted.

It could be. I watch the FastAPI repos a lot and tones of people do not understand how async python works and put their models with sync code in an async context.

Consider us one. :) We tried removing "async" -- thinking it would force sequential processing -- but it unexpectedly seemed to cause parallel processing of requests, which caused CUDA memory errors. Before removing "async", this is the weird behavior we observed: * Hacker blasts 50-100 requests. * Our ML model processes each request in normal time and sequentially. * But instead of returning individual responses imm…

What are the bots goals? Curious

Re: Playwright: Automate Chromium, WebKit and Firefox

#69
post #61
post #18

Earlier quoted context omitted.

We see a strong adoption of Playwright. It’s the default we recommend to users now. We also support Puppeteer, but its development is lagging. Having said that, I would love to support Cypress if I had infinite time and focus. Side note: Selenium is not on the menu, even with its large install base. We are aiming for where the puck is going and it’s going to Playwright. Full disclaimer: I’m CTO at Checkly.

Why was Selenium off the menu?

Selenium is slow and based on webdriver. I think most consider it legacy at this point. Most new projects tend to use Playwright, Cypress, or Puppeteer for E2E tests. All three options are much more performant and reliable.

Re: Playwright: Automate Chromium, WebKit and Firefox

#70

Earlier quoted context omitted.

Why not ReCAPTCHA?

Thanks for the suggestion. It is possible, but this degrades the experience for legitimate users. We prefer solving this without impacting/taxing normal users if possible.

Just add the captcha only for requests coming from the problematic ASNs, like AWS.

edit: Actually, since you use CF, just make a firewall rule that forces the captcha for those ASNs before it even gets to your app. They have a field named "ip.geoip.asnum" for that, and an action called "challenge" which will force a captcha.

Post reply on HN