Hacker News new | ask | show | jobs
by hebrox 1303 days ago
We're using Playwright [0] to do e2e testing. Locally I just run Chrome, but on CI FF and Safari are used as well. Using the official Docker image, this was really easy to setup. Because all browsers are automatically updated nowadays, we only test the most recent versions.

A recent issue we found, was that Safari was responding different to some HTTP headers.

[0]: https://playwright.dev/

1 comments

Do you use any tool like Browserstack or Lambdatest or Saucelabs for running your tests across browsers? My question is if you have already invested in end to end testing automation then why not run in 10 browsers to be on safe side than running in only 3. Price?
If it adds value, I think it's a good idea. But less is more, so right now I'm not inclined to add more to our CI/CD pipeline.

In the future our application will need to be able to run on mobile devices. Then I think I want to test it on a recent iPad, iPhone and Android device. We'll probably be using one of the tools you mentioned.