Writing
Notes on testing things properly
Practical, hands-on pieces on test automation, quality gates and AI testing — each one written to be immediately useful to the engineer reading it.
Why your Playwright suite is flaky, and the three causes behind almost all of it
Flakiness is not random. In practice it comes from three specific causes — shared state, implicit timing assumptions and unstable locators — and each has a concrete fix.
Test the API first: why UI-first automation is the most expensive mistake in QA
Most teams automate the UI first because it looks like testing. It produces the slowest, most fragile and most expensive coverage available. Here is the order that actually works.
How to test an LLM feature when the output changes every time
Conventional automation assumes the same input gives the same output. LLM features break that assumption. Here is the practical shift from assertions to evaluation.
RSS feed — no email signup anywhere on this site.
Have a QA task? Get a committed timeline.
Describe the work — a feature to test, a regression pack to automate, a release to validate. Within two business days you get a written scope, a delivery date in days, weeks or sprints, and a fixed quote.