Software Testing Myths

Test Case
Dimensions of Software Quality

SOFTWARE TESTING MYTHS and FACTS

Just as every field has its myths, so does the field of Software Testing. Software testing myths have arisen primarily due to the following:

  • Lack of authoritative facts.
  • Evolving nature of the industry.
  • General flaws in human logic.

Some of the myths are explained below, along with their related facts:

  1. MYTH: Quality Control = Testing.
    • FACT: Testing is just one component of software quality control. Quality Control includes other activities such as Reviews.
  2. MYTH: The objective of Testing is to ensure a 100% defect- free product.
    • FACT: The objective of testing is to uncover as many defects as possible while ensuring that the software meets the requirements. Identifying and getting rid of all defects is impossible.
  3. MYTH: Testing is easy.
    • FACT: Testing can be difficult and challenging (sometimes, even more so than coding).
  4. MYTH: Anyone can test.
    • FACT: Testing is a rigorous discipline and requires many kinds of skills.
  5. MYTH: There is no creativity in testing.
    • FACT: Creativity can be applied when formulating test approaches, when designing tests, and even when executing tests.
  6. MYTH: Automated testing eliminates the need for manual testing.
    • FACT: 100% test automation cannot be achieved. Manual Testing, to some level, is always necessary.
  7. MYTH: When a defect slips, it is the fault of the Testers.
    • FACT: Quality is the responsibility of all members/ stakeholders, including developers, of a project.
  8. MYTH: Software Testing does not offer opportunities for career growth.
    • FACT: Gone are the days when users had to accept whatever product was dished to them; no matter what the quality. With the abundance of competing software and increasingly demanding users, the need for software testers to ensure high quality will continue to grow. Software testing jobs are hot now.

Management folk tend to have a special affinity for myths and it will be your responsibility as a software tester to convince them that they are wrong. Put forward your arguments with relevant examples and numbers to validate your claims.

Test Case
Dimensions of Software Quality