Tag archive
Using agent-browser for goal-oriented UI exploration, independent assertions for verification, and turning discovered failures into cheaper regression checks.
1. What is Playwright? Playwright is Microsoft's open-source browser automation framework...
We made an email test verify the wrong account. The heading check passed. One identity assertion caught it. Here is the tested example and a six-point checklist.
Our app has a feature that replies to a rental listing on the user's behalf, filling in whatever...
Disclosure: I built inboxsink, the inbox API used in this post. The original, kept up to date, is on...
Make Playwright email verification tests easier to debug with a small failure receipt that records timing, identity, and the last useful state.
Most signup tests die at the same line. The form submits, the app renders "check your email", and...
Record a browser task, add a saved-result check, and test a deliberately broken save.
A Staff SDET's field guide to the architectural shift — for juniors who want to actually understand...
Our scraping pipeline only got reliable after we stopped treating CAPTCHAs as the main problem and rebuilt around queues, short-lived browser sessions
A practical Playwright workflow for separating inbox, selector, timing, and application failures in email verification tests.
The chat said 47 passed. CI said the browser was missing. Those two facts can both be true. You ran...