Home / Risks & Metrics Mistakes / 9 Common Myths of Being a Software Tester

9 Common Myths of Being a Software Tester

Testing is typically treated as one of the less glamorous parts of software development, in spite of its critical importance. This lack of enthusiasm has in turn given way to various myths about software testers, and buying in to them can make development even harder. In a post for Software Testing Help, Meenal Balajiwale addresses nine of these myths:

  1. Testers get involved only during post-development in the project lifecycle.
  2. Testers will not become project managers.
  3. Reporting to the lead developer impedes a tester’s career.
  4. People with weak code skills are assigned to testing.
  5. Testing is clicking at random places.
  6. Testing is just documentation and Excel sheets.
  7. Testers are paid on the low end of the scale.
  8. Testing is a thankless job.
  9. Testers delay project delivery.

Bugs in the Truth

Quality assurance (QA) needs to be a part of a project from day one, not relegated to a post-development activity. Any good manager these days will understand that. Speaking of which, it is not unheard of for a tester to become a project manager. The fact is that testing and management are largely two separate skill sets, the same as standard coding and management are separate, so testers have as equal opportunity of becoming management as anyone else in that sense.

Testing has artistry of its own. That might mean writing dense SQL queries to validate data, or it could refer to having the vision to test applications for extraordinary but plausible circumstances. Sure, documentation will be part of the job, but documentation is part of all jobs. And no, testers do not get paid less as a rule either.

Lastly, about testing delaying project delivery, Balajiwale says this:

Irrespective of starting out in parallel with the Dev team, we still have to wait until the development is completely done to start testing. Following that there is bug reporting, correcting, retesting, etc. This gives a superficial impression that testing is dragging the project on and on.

This problem does not arise with teams that have pre-planned test cycles. So, testing does not delay projects but incorrect planning and unreasonable expectations do.

For further thoughts on these points, you can view the original post here: http://www.softwaretestinghelp.com/myths-about-being-software-tester/

About John Friscia

John Friscia is the Editor of Computer Aid’s Accelerating IT Success. He began working for Computer Aid, Inc. in 2013 and continues to provide graphic design support for AITS. He graduated summa cum laude from Shippensburg University with a B.A. in English.

Check Also

Is Your Company Using Employee Data Ethically?

Like Jeff Goldblum’s character observed in Jurassic Park, sometimes we get so swept up in …

Leave a Reply

Your email address will not be published. Required fields are marked *