4 ms·
> "unit tests" appeals to me only rarely Give this man a node.js application with 100000 dependencies where an update from package version 34.2.4 to 34.2.5 br
by tralarpa 2y ago
> "unit tests" appeals to me only rarely
Give this man a node.js application with 100000 dependencies where an update from package version 34.2.4 to 34.2.5 breaks everything because the developers decided to change the order of parameters in one function just for fun.
- jimhefferon 2y agoOk, that's fine but that's not what he does.
- ajfriend 2y agoI think that says more about programming today than it does Knuth.
- kragen 2y agohe was dealing with that situation already in the 01970s—he was using an extensible programming language that people kept extending, so the programs he wrote one day would break the next—which is why he designed τεχ in such a way that you can take any τεχ document from 40 years ago and render it in exactly the same way in current τεχ one of the drop-dead showstopper tests in the τεχ release process since that time has been the 'τεχ torture test'; it's an enormous random τεχ document which has to produce byte-identical output on each new version of τεχ for it to be released, unless he can justify each difference. so he's not opposed to automated testing, he just tends to do it at a larger granularity
- hun3 2y ago> node.js application with 100000 dependencies where an update from package version 34.2.4 to 34.2.5 breaks everything because the developers decided to change the order of parameters in one function just for fun. aka "totally unknown environment" which you "need feedback about what works and what doesn’t"