I have and follow my code of ethics in software testing, do you? My code is simple – I ever do only things that would let me be proud of what I’ve done. Perhaps everyone does so. So I decided to go into a little bit more details here because for me the ethics means that I am ready to (and I did a few times) say NO to my boss or my customer if I don’t believe I could be proud about the results.
So reasons why I refuse to my boss, or my customer doing some tasks or even participating some projects is because I would never be:
Working extra hours or doing brainless simple tasks on a permanent basis (because this would damage my ability to do good job)
On the other hand I’m fine with:
More details on one of the ethically tricky aspect - hiding bugs from my stakeholders I’ve blogged about it already .
I wanted to write this down for years. Special thanks to Martijn de Vrieze for this blog post that provoked/reminded me to do so
P.S. An illustration
I almost declined participating one project when I realized that the only acceptance criteria for test documentation that customer have put is accordance to IEEE standard! But after a short consideration I accepted because it was my first (and hopefully the only) experience with test documentation according to IEEE – I wanted to better understand the standard to be able to criticize it better and maybe even suggest a better standard or decide for myself that no standard is reasonable at all.
Add a Comment