Why your tests are slow
Six causes, ranked by how often they are the real problem, and the fix for each.
#testing
9 pieces tagged testing,
from May 9, 2025 to September 16, 2026.
Property-based testing deserves its moment
State an invariant, let the machine find the counterexample. A twenty-year-old technique that fits this moment exactly.
Static analysis is finally worth the false positives
The tools got dramatically better while everyone was ignoring them because of a bad experience in 2015.
Model evaluation for people who ship
Not research benchmarks. A practical harness you can build in a day that makes every future model decision an hour instead of a week.
Run the incident before the incident
Game days, failure injection, and the specific reason your untested runbook is wrong.
Accessibility is a testing problem
Most accessibility failures are mechanical and catchable. Treating it as a specialist concern is why it doesn't get fixed.
Feature flags and the state space nobody tests
Twenty flags is a million configurations. You are testing one of them. Here's how to keep that from being a problem.
Verification is the whole job now
Producing code got cheap. Knowing whether it's right did not. Everything downstream follows from that asymmetry.
The test suite is a design document
If your tests are hard to write, your design is wrong. That's the signal, and most teams ignore it.