http://blogs.msdn.com/b/steverowe/archive/2007/04/26/teaching-your-team-to-program.aspxThe world of testing is becoming a lot more technical than it once was. While there is still a need for strong exploratory testing, the need for test automation is increasing dramatically. Test automation requires programming at some level. Good testen-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.msdn.com/b/steverowe/archive/2007/04/26/teaching-your-team-to-program.aspx#2335007Mon, 30 Apr 2007 08:19:56 GMT91d46819-8472-40ad-a661-2c78acb4018c:2335007SteveRowe<p>Thanks for that insight Stuart. &nbsp;That confirms what I would have thought to be the case.</p> <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=2335007" width="1" height="1">http://blogs.msdn.com/b/steverowe/archive/2007/04/26/teaching-your-team-to-program.aspx#2333464Mon, 30 Apr 2007 05:18:03 GMT91d46819-8472-40ad-a661-2c78acb4018c:2333464Stuart Moncrieff<p>As someone who occasionally runs training courses for Mercury in their functional test automation tools (WinRunner, QuickTest Pro), there is a very sharp divide between who have previous programming experience, and those who don't. </p> <p>But there is also a divide between those who have an *aptitude* for programming and those who don't. I have seen senior programmers (COBOL etc) who could not understand a simple for loop, while Business Analysts with no programming experience picked it up like a duck learning to swim.</p> <p>Cheers,</p> <p>Stuart.</p> <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=2333464" width="1" height="1">