Stereotypes have been given to just about every profession. There’s the sleazy used car salesman, ambulance-chasing lawyers, doughnut-eating sheriffs, corrupt politicians, drunken pilots – I could go on.
Software testers are apparently no exception to this rule. In fact, the editors over at TestingGeek.com just wrote a piece on some common (and unfair) tester stereotypes. With the aid of a Top Ten list, the authors break down some of the wrong reasons why people enter the field of software testing. You should go check it out.
Of course, if you’re at all familiar with the uTest community – and if you’ve spent any time chatting in our online Forums – you’d know that software testers are an especially difficult bunch to pigeonhole. There’s an amazing cross-section of backgrounds, personalities, ages and experience levels. In other words, there’s nothing typical about them! You can read our Tester Spotlights if you don’t believe us.
Anyway, here are a few of the “wrong reasons” they listed, in no particular order:
Software Testers can be Lazy
Software testing could be the perfect job for lazy people. There are so many things you need before start testing the product. You can happily wait for documentation, changed documentation and final documentation and documents describing some more changes after the final documentation. You can also wait for software to be delivered in test environment, defect tracking system to be setup and configured properly, Finalize the process which needs to be followed, testable system and list can just go on. As a tester, you can find thousands of things which can prevent you from testing the system.
Software Testers can preserve grey cells
Some testers feel that grey cells are precious and they make all the effort to ensure that mind is not exercised / challenged. Following test scripts manually is perfect way to preserve these precious grey cells. I remember someone telling me – I’ll happily follow written scripts and not apply my brain as long as I am getting paid. Surely you are getting paid, but are you enjoying the process? Does it not become boring for you? Do you feel good and proud about the work you are doing? Also, even if you are following the script, are you not observing things which are not part of the scripts?
Software Testers can blame anyone
As a testers, there is always opportunity to blame someone for your failures. You can blame BAs for changing requirements, infrastructure for not providing test environment, developers for not writing unit tests, introducing regression defects and delivering late and management for not giving enough importance to testing and cutting time for testing.