Why to let / not let developers test their own work
Posted
by
pyvi
on Programmers
See other posts from Programmers
or by pyvi
Published on 2011-05-18T08:38:49Z
Indexed on
2012/03/25
5:39 UTC
Read the original article
Hit count: 256
testing
|development-process
I want to gather some arguments as to why letting a developer testing his/her own work as the last step before the product goes into production is a bad idea, because unfortunately, my place of work sometimes does this (the last time this came up, the argument boiled down to most people being too busy with other things and not having the time to get another person familiar with that part of the program - it's very specialised software).
There are test plans in this case (though not always), but I am very much in favor of making a person who didn't make the changes that are tested actually doing the final testing. So I am asking if you could provide me with a good and solid list of arguments I can bring up the next time this is discussed. Or to provide counter-arguments, in case you think this is perfectly fine especially when there are formal test cases to test.
© Programmers or respective owner