The Top 5 Wrong Reasons For Not Hiring Testers

Considering whether or not your software company should hire a dedicated team of testers? Here are the Top 5 Wrong Reasons why you shouldn’t.

We Have a Beta Program
Some people feel that the best way to debug a system is to ship it to your customers and wait for trouble tickets. I don’t know how things work in your industry, but as far as I’m concerned, finding new customers is hard enough. I definitely don’t want to make matters worse by shipping them buggy software.

I’ve spent the last 5 years in the telecommunications industry where the standard for reliability is 5-9. If I even suggested to my customers that my software was in its Beta phase, they’d hang up on me immediately. I’m positive the same is true in any industry.

Imagine if I published articles that were not only full of grammatical errors but also missed a complete sentence here and there. Would you bother sending me an email to inform me that my articles are defective? Would you recommend my newsletter to your peers? I didn’t think so! So imagine how your customers feel when mission critical software breaks and crashes on them.

Developers Will Get Lazy
Some managers feel that developers will get lazy if they know someone else is responsible for testing their code. Developers are either lazy or they’re not. Someone who takes pride in his work will rigorously test his code regardless of whether or not you have a dedicated team of testers.

If your developers are lazy, don’t blame your testers. Blame the developers! Not hiring a team of dedicated testers won’t improve the situation. It’ll actually make the problem worse because your sloppy developer’s code will find itself in your customer’s hand instead of your testers’ lab.

We Can’t Afford Testers
If you can afford testing, then you can afford testers. Basic economics

Leave a Reply