Long-form writing on quality engineering, automation, CI/CD, and the moving target of AI inside the test lifecycle.
A step-by-step way to introduce AI into an existing automation suite: where it helps, where it must stay read-only, and how to measure whether it actually saved engineering time.
The recurring causes of flaky Playwright tests—timing, shared state, animation, network and parallelism—and the concrete fix for each, plus how to stop new flake from entering the suite.
What Playwright actually is, how it differs from older browser automation tools, which testing jobs it suits, and where an API or unit test is the better choice.
Learn how to test AI agents using outcome, trajectory, tool-contract, policy, resilience, and cost evaluations instead of relying on final-answer accuracy.
Learn how to convert traces, incidents, user journeys, and operational signals into privacy-safe regression tests and continuously updated QA priorities.
Book a private session and we'll work through it on your repo.