4 ms·

>Unless you propose that my test suite tests the libraries I am using, testing does not find code affected by API breakage. I do find that well crafted integra

>Unless you propose that my test suite tests the libraries I am using, testing does not find code affected by API breakage. I do find that well crafted integration tests give the best bang for the buck. >First of all, I doubt it. Second, you just sound rather arrogant. This was a mirror image response to your condescending assumption that I "just hadn't worked on large enough code bases" It's a little sad that you didn't have the self awareness to recognize that my feigned arrogance was satirizing yours ;-)

choeger 7y ago
> integration tests if you really worked on large projects you would know that integration tests involve more than just one language. They are a helpful tool, and a very important one. But if I had to rely on integration tests to figure out API breakage, I would have to quote a massive price for any libray upgrade. Fortunately I have cheaper and better means. > It's a little sad that you didn't have the self awareness to recognize that my feigned arrogance was satirizing yours ;-) Yeah right. You quote two projects and consider your work better tested than mine. And I am the arrogant one. All I said is that you sound like you did not see the kind of projects I did. Here's the thing. You either are really up to something and know something that all us soundness-first old farts doni know. Then you are going to revolutionize software development that has been coping with the same issues since the 70s. Or you are simply an arrogant youngster full of Kool aid, and you will crash against the same walls everyone else in the industry did.