
·7 min read
Let's turn a browser task into a Playwright test
Record a browser task with Playwright, then add a saved-result check. Run the same test against broken and working saves.
Playwright tutorials, Selenium migration guides, and QA engineering patterns from 10+ years in the field. No fluff. Only what works.

·7 min read
Record a browser task with Playwright, then add a saved-result check. Run the same test against broken and working saves.

·5 min read
One good run is not proof. Microsoft measured a 40-point gap between working once and working every time. Here is the ten-run check, in Playwright, with code.

·4 min read
Shift-left made developers own testing. Here are the five questions every developer asks when handed Playwright, answered with code.
·7 min read
Record a browser task with Playwright, then add a saved-result check. Run the same test against broken and working saves.

·5 min read
One good run is not proof. Microsoft measured a 40-point gap between working once and working every time. Here is the ten-run check, in Playwright, with code.

·4 min read
Shift-left made developers own testing. Here are the five questions every developer asks when handed Playwright, answered with code.

·3 min read
Most regression suites only grow. These five questions, with Playwright code for each, tell you which tests earn their place and which are furniture.

·5 min read
Use seven plain checks to decide whether an AI-generated test proves a real user risk and deserves a place in your test suite.

·4 min read
A test that fails, then passes on retry, is not fixed. Two readers explain why, with the race-condition case and a Playwright setup that treats retries as detection.

·5 min read
Your login helper exists twice: one that expects success, one that expects an error. Here is the options-object pattern that keeps one method, with Playwright code.

·4 min read
Should page objects contain assertions? A practical rule: business checks live in tests, technical guards live in page objects. With Playwright code.

·5 min read
What a page object model is, five outdated habits, and a simpler Playwright pattern with less shared code.

·5 min read
An AI model can change or vanish under your test suite overnight. The three-rule discipline, pin the version, keep a validated fallback, re-run the same suite on both, explained with the 19-day Fable 5 outage as the case study.

·7 min read
Where AI helps in QA, where it lies, and the one rule that keeps AI tests trustworthy, the AI does the work, a fixed check decides. With a working example.

·7 min read
Test passkey and WebAuthn login in Playwright with no hardware key. A complete working test using the virtual authenticator, in Chromium, Firefox and WebKit.

·10 min read
14 Playwright best practices for stable tests in 2026: locators, auth reuse, API testing, page objects, CI and traces. Plus the ones AI code agents get wrong.

·3 min read
An honest method for benchmarking LLM speed: tokens per second vs time to first token, across 42 Ollama Cloud models, measured every 10 minutes.

·5 min read
Learn how to score the tests an AI agent writes. Record the run as a trajectory, replay it offline, and grade it without live API calls.

·3 min read
Learn how to generate clean test scripts using Playwright Codegen, and how to scale those drafts into a production-ready test architecture.

·7 min read
An AI QA Architect designs the test systems AI agents run on. Learn the role, architecture, skills, and MCP testing boundary.

·4 min read
Compare Playwright, Cypress, and Selenium in 2026. Pick the right browser test tool for AI-agent workflows.

·6 min read
Playwright v1.60 adds scoped HAR recording, locator.drop(), ARIA boxes, and test.abort(). The release helps QA teams capture proof during the test run, not after the failure.

·4 min read
AI Test Automation Architecture: The 3-Layer System AI test automation architecture is the system that tells AI what to test. It also defines how to run tests and prove the result. I split it into three layers: orchestration, execution, and evidence. Without all three, AI testing becomes prompt output with no production gate.

·2 min read
Native drag-and-drop in Playwright MCP cuts brittle mouse steps. Learn what changed, when to use it, and how QA teams should validate complex flows.

·7 min read
Most teams install MCP servers and hope they work. Here is how to test, evaluate, and gate MCP servers before they break your CI pipeline.

·5 min read
Playwright MCP v0.0.73 fixes a critical gap where extension channels and executable paths couldn't be resolved from CI/CD environment variables. This release enables true containerized test pipelines, configure browser installations once in your Dockerfile, override per job via environment variables, no hardcoded paths required.

·5 min read
Playwright MCP v0.0.72 renamed browser_run_code to browser_run_code_unsafe, making sandbox escape risk explicit. The new browser_network_request tool enables indexed request inspection. Teams using this MCP server in CI pipelines need to update tool references and security documentation now.

·6 min read
Playwright CLI v0.1.10 introduces a spec-driven testing skill that guides AI agents through plan/generate/heal workflows for maintaining test suites from written specifications. Network inspection now uses stable request indexing, and raw output is default for all data-fetching commands, eliminating preprocessing steps in CI pipelines.

·4 min read
AI agents made it worse. They still get stuck at login screens. This month, that changed. MCP (how AI talks to tools) is changing how we test. Two teams at Microsoft shipped a fix. They released two ways to share your browser with AI. Playwright core added browser.bind(). The CLI team added an MCP Bridge. Both land in the same month. This is not a test. It is the new way.

·5 min read
Playwright MCP v0.0.71 ships browser_drop. It gives you native drag-and-drop from any MCP client. No more evaluate scripts. No more mouse.move chains. Grid reordering, file drop zones and text editor drags all work the same way a real user does.

·11 min read
Playwright's new stabilization work echoes a flaky-test fix from enterprise QA. See the pattern, why it matters, and how teams can reduce noisy failures.

·4 min read
Why skills need testing, not just writing, and how to do it systematically.

·6 min read
Playwright v1.59.0 ships the Screencast API, letting AI agents produce verifiable video evidence of their work. Engineers can replay agent actions with chapter markers and action annotations, no manual test replay required. Setup is three lines: start the screencast, run your agent logic, stop and save. This is the observability layer agentic workflows have been missing.

·6 min read
Technical decisions and lessons learned from rewriting a Python CLI tool as an OpenCode plugin.

·7 min read
I built a tool to benchmark AI skills, then ran it on my own project. The numbers changed how I ship: eval-driven development, proved rather than assumed.

·6 min read
A practical walkthrough for creating, testing, and installing production-grade OpenCode skills.

·7 min read
Master Page Object Model in Playwright & TypeScript (2026). Structure scalable tests, copy real-world architecture patterns, and speed up testing.

·5 min read
A practical, step-by-step guide to migrating your Selenium test suite to Playwright. Includes code comparison, common pitfalls, and a migration strategy that won't disrupt your team.

·6 min read
Flaky tests destroy team confidence and slow deployment. Here are 10 proven strategies to eliminate flaky Playwright tests, from someone who's fixed thousands of them.

·4 min read
Learn Playwright from scratch. This step-by-step tutorial will have you writing your first automated test in under 10 minutes, no prior automation experience required.

·5 min read
Which test automation framework should you choose in 2026? A side-by-side comparison of Playwright, Cypress, and Selenium based on real-world experience testing for Apple, Fortune 500 companies, and enterprise teams.

Get notified when I publish something new, and unsubscribe at any time.