3 ms·
I've known a few good perl programmers, and a few ok ones, and I know for certain that a lot of perl programmers came out of the dot-bomb days and back then tes
by KevinMS 16y ago
I've known a few good perl programmers, and a few ok ones, and I know for certain that a lot of perl programmers came out of the dot-bomb days and back then testing just wasn't part of the culture.
Not misunderstand me, writing tests for published modules was expected, but with everything from scripting to websites unit testing wasn't that common at all.
It wasn't a big problem either, because when the perl shop got serious, it ramped up the QA, and even possibly had a less buggy product than today, because QA can be brutal, and unit testing can be LAZY and misguided.
Testing fanboys flame me all you want, but I was there, this was common, we walked to work both ways uphill, but built the foundations of the web you see around you.
- viraptor 16y agoQA is a not-automated repetitive (usually acceptance) testing. It doesn't have much to do with unittests and they're definitely not interchangeable. If you compare QA and unittesting... the argument is pretty much misguided. Ideally, you should have both. And then some more automation. And quick feedback from automated tests.
- berntb 16y ago>>the dot-bomb days and back then testing just wasn't part of the culture. Yes, but I wrote "Testing has been central in Perl for most of a decade." I was mostly doing C++ at that time, but when I looked at Perl again a few years later -- testing was like air; everywhere. >>Testing fanboys flame me all you want Nah, I found "religion" after the dot-bomb, too. :-)