#testing
9 pieces filed under “testing”.
Swapping the model without breaking the product
Model migrations without breaking the product: shadow runs, eval-gated cutovers, tone and format regression diffs, and rollback plans for behaviour you can't unit test.
HTML emails in 2026: engineering for a hostile medium
Table layouts without despair, the dark-mode inversion lottery, bulletproof buttons, image-off rendering, and a testing matrix a small team can actually run.
Screen-reader testing: a 30-minute workflow for every release
Automated checks catch a third of accessibility problems. A repeatable 30-minute manual screen-reader script catches the rest — the workflow we run every release.
Evals are the new unit tests: a practical guide for product teams
Golden sets, rubric graders, regression gates and CI plumbing: how product teams build LLM evaluations that catch real regressions without a research team.
Build times are a team-health metric
Build time as a team-health metric: profiling CI honestly, cache strategies, test sharding, and the cultural rules that keep pipelines under five minutes.
Playwright suites that survive the redesign
How to write browser tests against intent, not pixels: accessible locators, honest page objects, visual diff quotas, and keeping the whole suite under ten minutes.
Golden evals: mining support tickets for test sets
Your support inbox is the best LLM eval dataset you'll ever get. How to mine tickets into versioned golden sets that catch regressions before users do.
Testing design tokens in CI like the API they are
Design tokens are an API contract between design and engineering. The CI pipeline that enforces it: grammar linting, ancestry checks, contrast tests.
A testing strategy that ships: what to test, what to skip, what to delete
Our testing pyramid, rebuilt for reality: contract-first unit tests, a thin layer of Playwright journeys, flake budgets, and a CI bill we defend monthly.