4 ms·
They should at least admit they made a mistake with the "test pyramid".
by pydry 2y ago
They should at least admit they made a mistake with the "test pyramid".
- codeflo 2y agoNot the least of which is that people who take stuff like that as gospel instead of as heuristics tend to endlessly argue what is and isn't a "unit".
- petesergeant 2y ago> who take stuff like that as gospel In 2011 I wrote a blog-post[0] about the dangers of taking TDD too literally, and until I disabled comments on it ~5 years later people were still angrily shaking their fists at each other online. 139 angry comments for a very short post. 0: https://writemoretests.com/2011/09/test-driven-development-give-me-break https://writemoretests.com/2011/09/test-driven-development-g...
- ben_w 2y agoMm. Those comments are indeed quite melodramatic. Someday I may write up the comparative experiences of joining an existing 120kloc mess where everything in the app code was done wrong and had no unit tests (that I recall finding) on one side, vs a carefully engineered ISO 9001 certified project on the other. The mess repeatly won awards. End users don't care about unit tests themselves, they care about the stuff the unit tests are a proxy for. (Previously wrote "customers don't care", but sometimes the customer is a business where the tests are a requirement, YMMV). Tests are the map, absence of bugs is the territory.
- pydry 2y agoIt's not even good as a heuristic. It's simply a bad idea which only got off the ground because it came from the Google testing blog.
- candiddevmike 2y agoConjoined triangles of testing
- petesergeant 2y agoI feel like "testing trophy" has been in vogue for a while now, and definitely feels more right as someone who's made a career of unfucking test suites, but there's almost no area of software engineering as involved in navel-gazing as testing.