It’s amazing how many product teams never laissez passer plenty importance to testing (and testers). And the excuses you lot listen are fifty-fifty to a greater extent than astonishing; albeit funny. With all the gratis too opened upwards rootage testing tools, services, sites, blogs too books available, ane tin no longer direct maintain whatever to a greater extent than excuses non to perform software testing on their production before they unloosen it. It powerfulness come upwards equally a surprise to some, but inward most cases many developers create non larn the chance to operate amongst a truly competent tester too thus they don't know what that is like. Ignoring the importance of testing too testers inward a team is such a hideous false economy that it is difficult to believe so many organizations too people withal believe inward it too thus direct maintain to resort to these stupid excuses for non having plenty testing/testers.
I realize that it may live difficult to rank these (dumb) reasons that people similar to role for non doing plenty testers (and hiring plenty testers) but hither are the top v stupid reasons people don't hire testers. Read on...
My Product isn't Finished Yet
In today's rapid evolution historic menses where methodologies similar agile scrum too sprint are mainstream, how to a greater extent than absurd could your excuse live than this one? Even if you lot operate inward an surroundings where several Beta versions are released showtime before the lastly product, volition you lot live willing to adventure losing your customer's trust too your reputation yesteryear releasing versions that are laced amongst defects?
Also, volition you lot live willing to bet that your star programmer doesn't exit you lot too bring together roughly other arrangement amongst a dedicated testing squad too proper QA methodologies inward place, because he got fed upwards reading through too fixing hundreds of client reported bugs everyday? The sooner you lot realize the importance of finding too fixing bugs before inward the production cycle, non alone volition it salve you lot revenue but also your reputation.
Quality is Everyone's Responsibility; No Dedicated Testers are Needed
Such excuses commonly come upwards from teams that (at to the lowest degree believe that they) follow the mantra "Quality is everyone's responsibility", too thus they boundary into this inappropriate misconception that you lot tin really larn dandy results without dedicated testers. Theoretically, this all works. But the work begins when everyone starts assuming that every other guy inward the other cubicles are already testing the production too thus it is okay if he skips it.
An extension to the inward a higher house excuse that I listen often is that the programmers volition croak lazy too destination upwards writing buggy code if they know at that topographic point is a testing squad responsible of finding the defects. But let's confront it; programmers are either lazy or they're not! H5N1 programmer who takes pride inward his operate volition rigorously exam his code no affair whether or non you lot direct maintain a dedicated squad of testers.
We direct maintain Budget/Time Constraints.
Who doesn't? Do-it-yourself testing yesteryear your programmers tin salve you lot roughly dollars too tin fifty-fifty live effective (if they’re imaginative). Also, it is withal cheaper to hire an average tester than it is to hire an average programmer. And if you lot don't hire testers, you're going to destination upwards having your programmers doing testing.
From my ain experience, non alone the programmers are mediocre when it comes to testing but they also tend to overlook errors inward their code equally compared to a tester testing it. Everyone has budget constraints. But dandy production teams are proficient at realizing the importance of a dedicated QA squad on board too they know it is to a greater extent than of an investment than an unnecessary expense. And hither are roughly things to visit if you're worrying close testing on a tight schedule.
My Product is Perfect. It doesn’t ask Testing.
Actually, NO! If your production is perfect too so either it is non a production or isn't really perfect. In either of the cases, this way that all products ask testing equally long equally they are complex plenty to qualify equally proficient usable products (software, website, spider web application etc).
H5N1 divide QA squad tin create an 'Us vs Them mentality', which is non Healthy
I've worked inward teams where exam too dev reported to the same manager, too also inward teams where the testers reported to dedicated exam managers. In my experience, both of these tin operate good provided the percentage politics is kept nether command too the team's managing director is responsible at ensuring so. Good teams realize that a dedicated testing squad is essential to the team's overall success too that the QA squad non alone saves the programmers a lot of fourth dimension (and credibility) yesteryear helping them ready defects before they honor their way to the customers but also salve the stakeholders substantial revenue that would otherwise live spent on fixing the bugs inward a post-release scenario too would require subsequent patches to live released; non to advert the frustrated customers too angry investors.
As per the 'Us vs Them mentality', it is inward the manus of the team's managers too the stakeholders too how they cope their resources. There is a argue why people withal role the one-time proverb -- 'garbage inward is garbage out'!
Let me know if I missed whatever to a greater extent than stupid excuses that people brand justifying their determination non to hire to a greater extent than testers too non to create to a greater extent than testing. Happy Testing...