u/waltergalvao — reddlx

Playwright testing in Staging vs Production

TLDR: We wrote a decision framework for splitting Playwright tests between staging and production, including when production testing isn't worth the operational cost.

Either you trust staging or you don't.

The real problem is that staging and production have different risk profiles, and almost nobody configures their test suite to reflect that.

The article covers what your timeouts, feature flags, parallelism, retry policy, trace capture, and auth setup should actually look like in each environment, and when production testing creates more problems than it solves.

currents.dev

u/waltergalvao — 7 days ago

▲ 34 r/Playwright

Hey folks, back with another article - this time about how to design tests that survive when the UI is refactored.

TLDR: Learn why UI refactors keep breaking Playwright tests even when the features work fine.

It covers the coupling patterns that make suites fragile and ranks selectors by what actually survives design system changes. There's also content on structuring page objects so migrations don't cascade into dozens of test failures.

u/waltergalvao — 17 days ago

▲ 4 r/Playwright

TLDR: Wrote about why Playwright's HTML reporter stops working once your suite grows past ~100 tests.

The reporter is fine for debugging failures in a single run. But it treats every run as a clean slate. No history, no cross-run comparison, no way to tell if a test has been flaky for months or just broke today. You end up not knowing whether the suite is getting better or worse. Failures all look the same whether they're fresh regressions or known offenders you've been ignoring.

In our experience, the pain hits earlier than people expect. Somewhere around 50-100 tests, not 200+. By 300 tests you've probably already built something custom or just accepted that CI is chaos 🙃

u/waltergalvao — 28 days ago