Performance Testing
Lighthouse is good at measuring page load performance. It's bad at measuring everything that happens after load: navigation between pages, complex interactions, data-heavy operations, application-specific flows. For those, Playwright with Chrome DevTools Protocol (CDP) is the right tool. This guide covers using Playwright to catch performance
Regression Testing
Regression testing — verifying that existing functionality still works after a change — is the unglamorous backbone of software quality.
Testing
Every mature test strategy uses multiple types of tests, each serving a different purpose.
Testing
A regression test suite that nobody maintains is a liability, not an asset.
Testing
"Regression testing" and "retesting" get used interchangeably in engineering conversations, but they're different activities with different goals, different triggers, and different scopes. Mixing them up leads to either missed bugs or wasted effort. Here's a clear breakdown. The Short Version Retesting: You
Testing
A regression test suite that runs once a week on a developer's laptop isn't regression testing — it's wishful thinking.
Testing
Playwright has become the go-to tool for browser-based regression testing. It's fast, reliable, and supports Chromium, Firefox, and WebKit out of the box.
Testing
Running your entire regression suite on every commit is a solved problem — it's just slow and expensive.
Testing
Traditional software regression: you change a function, run tests, and if they fail you've introduced a regression. Easy to detect.
Testing
Every time you ship a new feature, you're rolling the dice on the code that already works.