Who to Blame for Software Defects in Production?

by Nataliia Vasylyna | August 2, 2013 10:00 am

If many defects were found by users in a certain part of software after release the tester is not always the one to blame. It may be that this part of the application is very sophisticated or of high risk. The application could have been released in haste and there was too little time on testing.

Before asserting that the tester neglected his duties and that is why the mobile testing, desktop testing or web site testing was performed careless, some facts should be taken into account.

The Facts That Are to Be Considered When Judging Tester’s Fault in Appearance of Software Bugs After Release:

• Overlooked software bugs that are in rarely used functionality and to reproduce them one must do complicated combination of steps, are not considered to be very serious fault.
• If the software was developed and tested in a hurry, there was no time on thorough web site testing, desktop testing or mobile application testing and the product was released without matching the release requirements, errors found in production are not the tester’s slip-ups.
• In case automated testing was applied to the software part with overlooked defect[1], one should find out if the automated script skipped the step containing the defect. If it did, then the missed defect is test engineer’s mistake.
• If the testing was performed manually, the tester could have omitted executing the same annoying steps in the part of the system that previously worked well. If it is so, the missed software bug is the tester’s neglect.

Related Posts:

• The Secret of NFT Games Popularity: Features and Benefits[2]
• Software Bugs Monthly Digest – July 2021[3]
• Is software testing a waste or a benefit?[4]

Source URL: https://blog.qatestlab.com/2013/08/02/are-testers-always-to-blame-for-software-defects-in-production/

---