Tests just saved me from making a change that would've broken some setups. I immediately fixed everything, of course, so no-one would ever know that originally, I screwed up.
Just though I'd let you know, in case you're wondering if you should "waste" time writing tests ;)
@minoru It depends. The technique of the tests is crucial: random, property-based testing is good (at least until we can verify everything formally). But the manual "tests" just mirroring the algorithms and dependent on every implementation detail is indeed a waste of time, IMO.
@amiloradovsky Sure. In this specific case though it was a lowly smoke test: I fed a bunch of static data into a parser and checked that it doesn't error. This isn't even proper unit testing, but it saved me this time around.
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!