A sample text widget

Etiam pulvinar consectetur dolor sed malesuada. Ut convallis euismod dolor nec pretium. Nunc ut tristique massa.

Nam sodales mi vitae dolor ullamcorper et vulputate enim accumsan. Morbi orci magna, tincidunt vitae molestie nec, molestie at mi. Nulla nulla lorem, suscipit in posuere in, interdum non magna.

Myth: testers should be responsible for the quality of a product

There is a myth that only testers are responsible for the quality of a product but the reality is discussed and explained below.

– It is a very common misinterpretation that only testers or the testing team should be responsible for the product quality.
– Testers responsibilities include the identification of bugs to the stakeholders and then it is their decision whether they will fix the bug or release the software.
– Releasing the software at the time puts more pressure on the testers as they will be blamed for everything.
– Only the testers could not be blamed for everything.
– There are other factors which are responsible for introducing the bugs and hampering the quality of the software product.
– Testing is required only because there are errors.
– This only implies that whatever defects are present in the system, they have been introduced in the phases prior to testing and not during the testing phase.

Other factors that cause bugs in the software are:

  • 1. Human factors:
  • – This is one of the most common factors.
    – As the software is developed by humans and the humans have a tendency to commit errors, obviously the software also gets many errors and faults.
    – Therefore, someone who expects the software to be free of any errors is a fool of course.
    – Till now no other non-human agent has been discovered that would commit lesser mistakes while developing the software.

  • 2. Development time frame that is unrealistic:
  • – The release schedules under which the software is developed often suffer from many limitations such as limited time and resources as well.
    – This makes the deadline of the software very unrealistic.
    – Because of this, the entire development team has to make compromises in the various stages of software development for meeting the release schedules.
    – This has an adverse effect on the quality of the software since the software did not get the maximum possible development and testing time.
    – And since the pressure on the programmers and testers increases they both tend to make more mistakes.
    – Programmers write the wrong code and the testers forget about testing some part of the application.
    – That is why the software testers alone cannot be blamed.

  • 3. Bad coding practices:
  • – Bad coding practices always open the doors for the errors to creep in the application software.
    – Bad coding practices might include carrying out improper validations of the memory overflows, boundary conditions, databases; field ranges and so on, inefficient exception handling and so on.
    – Bad coding practices even extend to the use of the poor tools, debuggers, pro filers, compilers, validators and so on.
    – This makes it all easy to introduce the bugs and difficult to pick them out.

  • 4. Communication failure:
  • – Mis-communication is another factor responsible for the introduction of the errors.
    – There might be a lack of efficient communication between the team members during the various stages of development. – In some cases, the requirements might be vague or even incomplete.
    – This does not allow the programmers to clearly understand the requirements of the client.
    – Another case where errors creep in because of the communication failure is when one programmer writes the code and another one modifies it.

  • 5. Bad logic design:
  • – This is the era of the development of software systems that are very complex.
    – It takes a lot of brainstorming to make such reliable software and so it requires a lot of patience.
    – If we urge to complete it quickly, the whole thing can wrong and we might end up with erroneous software.
    – Not applying the technology properly, or going after the easiest way of implementation of the solution without properly understanding what is feasibility level of the technology being used in the software?
    – In some cases people are not just allowed to think.

  • 6. Lack of version control:
  • – If you keep on finding the same bug recurring (i.e., the regression bugs) at regular intervals of time, then there might be some problem with your version control.
    – With the concurrent version systems it is quite easy to keep track of the entire work.

    Leave a Reply

    You can use these HTML tags

    <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>