Jason Merx | Comments

I like the framing of starting from the user path instead of the checklist. One related thing I’ve been exploring is UI-driven API regression testing: use an important user journey as the driver, record the API traffic behind it, then compare response shapes across versions. It fits this product-minded view because you’re not trying to diff every endpoint. You’re asking: did the backend behavior behind the paths users actually rely on drift unexpectedly?

Good article. One related pattern I’ve been exploring is UI-driven API regression testing: use the Playwright UI flow as the stable driver, record the API traffic behind it, then compare response shapes across versions. POM fits well here: it helps reach meaningful product states reliably, while the API diff checks whether backend behavior drifted behind a green UI.