3 ms·
Having dedicated testers is great, but not the kind Joel is talking about. He's talking about low-paid manual laborers whose work has mostly been automated, no
by kragen 5y ago
Having dedicated testers is great, but not the kind Joel is talking about. He's talking about low-paid manual laborers whose work has mostly been automated, not accomplished programmers whose work is considered just as valuable as that of writing the production code they're responsible for testing, and who spend a lot of their time on automating the test process. Joel's argument is specifically that testers are cheaper than programmers, so it's silly to have programmers test their own code instead of having testers do it. Contrast Dan Luu's internship work as a tester:
> Most of them were only slightly less manual than "testing" a phone by mashing buttons, but I did one not-totally-uninteresting task, which was to verify that a flash chip's controller behaved correctly. Unlike my other tasks, this was amenable to automation and I was able to write a Perl script to do the testing for me. ... they had me do verification on the logic they were writing. They had a relatively new tool called SixthSense, which you can think of as a souped-up quickcheck. The obvious skill I learned was how to write tests using a fancy testing framework, but the meta-thing I learned which has been even more useful is the fact that writing a test-case generator and a checker is often much more productive than the manual test-case writing that passes for automated testing in most places
- 3np 5y agoIt also depends on what you're developing. In games, in particular, dedicated testers/QA are very much part of the norm and best practices in a different way compared to web apps.
- kragen 5y agoThat is an excellent point.
- dfabulich 5y agoJoel is specifically referring to the kind of testers that Microsoft had at the time the Joel Test was written (Aug 2000). At that time, for Windows and Office, Microsoft had testers who would write their own test plans (and then execute the tests themselves). This is not the low-paid manual labor you're thinking of where a test manager writes a test plan and then delegates it to folks who are expected to just follow instructions. The "manual labor" style of testing was/is typical of game dev companies, where it's easy to trick inexperienced kids into working for very cheap or even free, just to have early access to upcoming games and the (mostly illusory) opportunity to land a "real job" in the game industry.
- dgb23 5y agoIn some companies these game testers are treated as second class citizens in every way imaginable. If I remember correctly, JS very much cherished skilled testers and emphasized that they ought to be experienced, that they’re doing a very hard job. I personally never worked with dedicated testers, but I appreciate both lower level automated tests for critical code, and higher level acceptance, even manual tests by domain experts. Some of the best feedback I got was from people who can’t program but are much closer to the real world problems.
- kragen 5y agoThank you for adding that context! I didn't know that. In https://www.joelonsoftware.com/2000/08/09/the-joel-test-12-steps-to-better-code/ https://www.joelonsoftware.com/2000/08/09/the-joel-test-12-s... Joel lays out his reasoning: > If your team doesn’t have dedicated testers, at least one for every two or three programmers, you are either shipping buggy products, or you’re wasting money by having $100/hour programmers do work that can be done by $30/hour testers. Skimping on testers is such an outrageous false economy that I’m simply blown away that more people don’t recognize it. I still think jobs for people to "write their own plans and then execute the tests themselves" have mostly been automated out of existence, and they were still low-paid in Joel's mind.
- baud147258 5y ago> I still think jobs for people to "write their own plans and then execute the tests themselves" have mostly been automated out of existence, Where I work, it's complicated to automate a lot of things, mostly because of the various installation configuration and how testing has to rely on external hardware like HSM and smartcards. And so the QA write the test plans and execute them, with automation testing non-regression on the most current use cases > and they were still low-paid in Joel's mind. Though I think the QA people at my current job at less paid than the equivalent on the dev side.
- kragen 5y agoHopefully they are paid more than the 30 cents on the dollar Joel is citing!
- deleted 5y ago[deleted]