The Wall<\/h4>\n<\/p>\n
The metaphorical \u201cwall\u201d between programming and testing is often quite high (as in programmers write code, then throw it over the wall to testers; who, in turn, throw the bugs back over the wall to developers, who make fixes and start the wall-chucking process over again). Lloyd was hired to catch stuff thrown to him over the wall, and I think it\u2019s a fair argument to say it would have been more efficient for developers to run those tests as part of a check-in suite (assuming, of course, they had such a thing). <\/p>\n
To be completely transparent, a wall on my team still exists \u2013 it\u2019s just a much shorter wall. There are still expectations of programmers and testers that fit into the typical roles, but collaboration and code throwing don\u2019t occur often. <\/p>\n
Infection<\/h4>\n<\/p>\n
Elisabeth Hendrickson speaks often of being \u201ctest-infected\u201d to describe programmers who \u201cget\u201d testing (I believe the term was coined by Erich Gamma). I for one, can\u2019t think of a good reason for a programmer to not have some test ideas in their head when they write code. <\/p>\n
Similarly, I think that testers can benefit from being a bit \u201ccode-infected\u201d. Before the self-preserving screams of oppression begin, let me note that I said testers \u201ccan<\/i> benefit\u201d from some code knowledge. I\u2019m not talking about language expertise \u2013 a basic understanding of programming logic and some ideas on how computer programs may<\/i> improve testing is usually plenty. It\u2019s not necessary<\/em> to know anything about programming to be a tester \u2013 I\u2019m just saying it can help. <\/p>\n Beyond the disclaimer, it\u2019s worth elaborating on the last two paragraphs here. I have had testers tell me that knowledge of code will adversely affect the \u201ctester mindset\u201d \u2013 that by knowing how to code, the tester will somehow utilize less of their critical thinking or problem solving skills. While I suspect this to be a false assumption, I have no proof of whether this is true or not. But I will hypothesize that if this is true (that code-infection adversely affects testing skill), then it\u2019s just as likely that test-infection adversely effects programming ability. When I look at it this way, the answer clears up a bit. Take a moment to think about the best programmer you know. I\u2019m fortunate enough to work with some really incredible (and some famous) programmers. Every single one of them is test-infected<\/i>. Yes \u2013 I have no hard data, and zero empirical research, so I could be high as a kite on this, but I\u2019d be curious to hear if anyone knows a great programmer who doesn\u2019t have the ability to think at least a little bit like a tester. <\/p>\n So \u2013 let\u2019s suppose for a few minutes that code-infection is beneficial for testers. Not even necessarily equally<\/i> beneficial \u2013 just helpful. Is there such a thing as too<\/i> infected<\/i>? An old colleague of mine, John, once said, <\/p>\n \u201cI\u2019m not the best tester on the team, and I\u2019m not the best programmer. But, of the programmers on the team, I\u2019m the best tester, and of the testers, I\u2019m the best programmer\u201d. <\/p>\n<\/blockquote>\n Which role<\/i> should John be in? On your team, would he be a programmer, or a tester? Is it a clear cut decision, does it depend, or does it even matter? Is John a test-infected developer, or a code-infected tester? Does it matter? <\/p>\n I think the answer to the above questions are either \u201cIt depends\u201d, or \u201cIt doesn\u2019t matter\u201d, so let me ask a different question. Do you want a team full of John\u2019s? Maybe you do, or maybe you don\u2019t (or maybe it depends), so let me rephrase yet again in the form of a quick thought experiment. <\/p>\n You are forming a nine-person team to make a super cool software application. You get to build a dream team to put it together. On a scale from 1-9, where a 1 is a tester with zero knowledge of programming, a 9 is a developer who can\u2019t even pronounce \u201cunit test\u201d, and a programmer \/ tester like John is a 5 – which employees do you hire (note that all of these people get paid the same, work the same hours, get along with each other, etc.). <\/p>\nCode Infected<\/h4>\n<\/p>\n
\n
An experiment<\/h4>\n<\/p>\n
![\"clip_image002\"](\"http:\/\/angryweasel.com\/blog\/wp-content\/uploads\/2013\/05\/clip_image002.png\" "\\"clip_image002\\"")
<\/a> <\/p>\n