#PHP folks, what framework-agnostic tooling (as in not #Symfony / #Laravel / #Laminas etc) are you using for running headless browser-based tests these days via something like #PHPUnit?
I'm looking at setting something up in #Docker on #macOS, I've tried Symfony Panther and it's been a shitshow of errors and not being able to get #Chrome or #Firefox running in Docker :/
@brunty If you’d prefer not to use JavaScript, could PHPUnit call a PHP Selenium wrapper? (I assume there’s one of those for every language ever invented at this point)
@brunty@Flyingmana I assumed everyone used Cypress or Playwright. We’re considering migrating from Cypress to Playwright right now since our Cypress tests are unpredictably flakey.
@SamStrong@brunty@Flyingmana
Every single frontend test, of a non-legacy system, or any system with bugs (all of them), will be flakey, and expensive.
The further out you go from unit testing, this is an inescapable truth. It happens later, often not by the folks building; their tools (looking at you webpack, emotion, etc) mangle the source tree; require hacks like waiting up to n seconds for elements to be in a desired state.
If your frontend is de-coupled, you might gain more win from API
@lewiscowles1986@brunty@Flyingmana I’m not sure what you’re suggesting. Just writing unit tests? We need more than that in our testing triangle. And we need tools that use real browsers to run them.
@SamStrong@brunty@Flyingmana
I did not suggest only writing unit tests, I merely acknowledged the truth that the further out from them you get, the more expensive, time consuming and fragile those tests become.
At no point did I say don't write any type of test.
@lewiscowles1986@SamStrong@Flyingmana please untag me from this, I'm not interested in yet-another-testing-pyramid-unit-vs-higher-level-tests-discussion thanks - that's not what my question was about
Add comment