So I'm abit confused, apparently there are discussions in the Testing World as to whether or not it's a good idea for testers to review code.
It's something touched briefly on a few blogs I read recently: http://blogs.msdn.com/imtesty/archive/2008/03/11/do-testers-do-code-reviews.aspx#comments
and http://www.goldb.org/goldblog/
I'm sure the discussion is on a load of forums and blogs everywhere but those are the two I read most recently.
What I don't understand is why anybody would question whether or not it is a good idea for testers to review code. Fixing an error before it makes it to a build seems like a wicked idea! Imagine that! Fixing a problem before it's a problem! You could be known as a psychic software tester. I! Tony Bruce am the worlds first Psychic Software Tester! Call 1800 Magic Testing now!
Well, the first apart from the all the men and women testers who already have the ability or skillset to read and review code.
And I guess that's what and where it comes down to, testers with the skillset to be able to review, not just read code.
I aim to be able to review code but how useful is it going to be if I just learn to read code? I maybe able to spot one or two things but for it to be a useful practice will I first need to have experience with development?
Anybody been there? Done that? Can you shed some light? How have your experiences been?
|