The test that would have caught it
The same bug arrived twice, 18 months apart, on the same client site, and the second time I found my own fix from the first time sitting in the git history with no test next to it.
5 posts filed under Testing, newest first.
The same bug arrived twice, 18 months apart, on the same client site, and the second time I found my own fix from the first time sitting in the git history with no test next to it.
I asked for test coverage on a module that didn't have any, got 14 tests back, and all 14 passed, and about half of them could not have failed under any circumstances whatsoever.
A test that failed about one run in 15, and a team with a ritual around it. The ritual was clicking a button. It had been going on for eight months.
For five years, the production version of every site I built was assembled on one MacBook in one room in San Diego. What finally moved me wasn't a disaster. It was noticing how much I was relying on not having one.
The testing pyramid assumes your software is mostly logic, and a brochure site is mostly templates, content and CSS, so the bottom of the pyramid ends up testing functions I wrote to have something to test.